822329 - Errors break E.me content, even after error states have been resolved.

Status: VERIFIED WORKSFORME

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

Description

[Cody Roesch [:croesch]]

Attachment: Everythingme Error.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0
Build ID: 20121128204232

Steps to reproduce:

You must be on a network!

1. Launch Build 20121217070202 version 18.0
2. Go to Everything.me
3. Go into any category and try to launch an app such as NFL.com
4. Notice that an error message appears saying it's not working properly.
5. Tap Try Again and notice that you are taken to a broken page.
6. Now go back and move NFL.com to your Home page.
7. Try to launch the NFL.com App from your home page and you should see the error again.
8. Tap Try Again and notice the app loads correctly.


Actual results:

Loading the apps from Everything.me is not working currently. However moving the app to the home page is allowing access to the website after retrying the operation.


Expected results:

The user should be able to access these apps from both Everything.me and the Home Screen without ever seeing any errors if they have a connection to the network.

Comment 1

[Mark Hammond [:markh] [:mhammond]]

I can somewhat reproduce this (it doesn't always work after adding it to the home screen) but I suspect it is a dupe of bug 822329 (but as there are no builds with that fix yet, I can't be sure)

Comment 2

[Josh Carpenter [:jcarpenter]]

Am also seeing this in 12/26 buid. Everything is throwing up errors when it should be working. This seems to be caused by a failure to check that a preexisting error state has been cleared. We're seeing several odd behaviours:

 Start with a working connection...
1. Open Twitter from E.me > Social. Loads properly
3. Long press Power button. Turn on Airplane mode. Go back to Twitter.
4. Twitter crashes. Error message appears.
5. Press Home hw button to exit app (per decision made in bug #824672).
6. Turn Airplane Mode Off. Wait for connection to become active again.
7. Open a different E.me app. eg: Pinterest, also from E.me > Social

Expected: Pinterest loads.
Result: as follows....

8. An error message appears. Pinterest is having problems.
9. Press Try again. 
10. Content reloads, but shows Twitter!
11. Switch to Task Manager by long pressing Home button. 
12. The card says "Quora" instead of Twitter!

I think this needs to block release. It's bad enough that we don't gracefully handle errors in E.me (again, per bug #824672). It's even worse that we continue to throw up errors even once a connection has been reestablished.

Build ID: 20121226061418

Comment 3

[Joe Cheng [:jcheng] (please needinfo)]

Triage: BB-. people in triage can load e.me apps fine. QAWANTED to confirm and renom if reproducible

Comment 4

[Josh Carpenter [:jcarpenter]]

Joe, did you guys follow the STR? This is not hard to trigger, in my experience, and effectively breaks E.me. 

Looks like QA confirmed, so I'm renominating.

Comment 5

[Tony Chung [:tchung]]

Tested on 20121230230203 build, and unable to reproduce on nfl.com.  site loads as expected.  however, i believe this is a problem when a page can't load a site, and won't try again, so please look for another reproducible site and latest build to see if it fails.  

renom bb? if it does, thanks.

Comment 6

[Cody Roesch [:croesch]]

This bug is verified as fixed in build 20130103070201