Closed
Bug 1011832
Opened 10 years ago
Closed 10 years ago
Loading my app on Android displays a blank white screen
Categories
(Firefox for Android Graveyard :: Web Apps (PWAs), defect, P1)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: block.jon, Unassigned)
References
()
Details
(Whiteboard: [WebRuntime])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140506152807 Steps to reproduce: Created an open web app and installed it via android. Actual results: Upon loading the web app, it just shows a blank white full screen. Expected results: It should display the app interface as it does in plain web browsers. See here: http://app.youcards.co/
Just to clarify, the problem only manifests when I install my open web app into the home screen of my android and I try to load it as an android stand alone app.
Updated•10 years ago
|
Component: General → Web Apps
OS: Mac OS X → Android
QA Contact: aaron.train
Hardware: x86 → ARM
Comment 2•10 years ago
|
||
Which version of Firefox are you testing on? Can you try out Nightly (http://nightly.mozilla.org) and report back if that works for you? This sounds a tiny bit like bug 889744 or bug 1003962.
Comment 3•10 years ago
|
||
I'm unable to reproduce the problem with the latest Nightly build of Fennec. I loaded the app's URL in Fennec, and an "Install App" button appeared briefly, but which it was quickly replaced by a "Choose photo" button with a "Start here" image. Nevertheless, I managed to tap the "Install App" button before it disappeared after reloading the page a few times and went through the installation process, after which I was able to tap the YouCards icon in the All Apps screen and start the app.
Updated•10 years ago
|
Severity: normal → major
Priority: -- → P1
Whiteboard: [WebRuntime]
Comment 4•10 years ago
|
||
I have this problem too. To fix it, I must to uninstall Firefox 30 or Firefox 31 beta from my tablet and start the app. A popup shows and permit to install Firefox beta by the Play Store. After the install, I press the button back, and the app starts correcty. If I restart the app (after kill it by the " long press " home button), I have a white screen after the splash screen…
Comment 5•10 years ago
|
||
(In reply to jonathanmm from comment #4) > I have this problem too. To fix it, I must to uninstall Firefox 30 or > Firefox 31 beta from my tablet and start the app. A popup shows and permit > to install Firefox beta by the Play Store. After the install, I press the > button back, and the app starts correcty. Are you seeing this problem with the app at appcards.co or with another app? > If I restart the app (after kill it by the " long press " home button), I > have a white screen after the splash screen… What happens if you restart your device and then launch the app?
Comment 6•10 years ago
|
||
(In reply to Myk Melez [:myk] [@mykmelez] from comment #5) > (In reply to jonathanmm from comment #4) > > I have this problem too. To fix it, I must to uninstall Firefox 30 or > > Firefox 31 beta from my tablet and start the app. A popup shows and permit > > to install Firefox beta by the Play Store. After the install, I press the > > button back, and the app starts correcty. > > Are you seeing this problem with the app at appcards.co or with another app? An another app. I don't find the app at appcards.co > > > > If I restart the app (after kill it by the " long press " home button), I > > have a white screen after the splash screen… > > What happens if you restart your device and then launch the app? It's work, I don't have the blank screen
Comment 7•10 years ago
|
||
(In reply to jonathanmm from comment #6) > (In reply to Myk Melez [:myk] [@mykmelez] from comment #5) > > Are you seeing this problem with the app at appcards.co or with another app? > > An another app. I don't find the app at appcards.co > > > What happens if you restart your device and then launch the app? > > It's work, I don't have the blank screen Hmm, that sounds like a different problem with similar symptoms. With which app(s) are you experiencing the problem?
Comment 8•10 years ago
|
||
(In reply to Myk Melez [:myk] [@mykmelez] from comment #7) > (In reply to jonathanmm from comment #6) > > (In reply to Myk Melez [:myk] [@mykmelez] from comment #5) > > > Are you seeing this problem with the app at appcards.co or with another app? > > > > An another app. I don't find the app at appcards.co > > > > > What happens if you restart your device and then launch the app? > > > > It's work, I don't have the blank screen > > Hmm, that sounds like a different problem with similar symptoms. With which > app(s) are you experiencing the problem? It's a private app, and I can't share an url or source. But, I watched, when the server (Tomcat) have a charge > 1, to get a page can make more than 20 sec on Chrome or Firefox on the tablet. I think the blank screen as a link this it. The private app use AppCache, with an " appcache_path " in the manifest, so I think for the first run, it's blank because the server is very slow, but, for the next run, when the page is in the cache, it's fast and the blank screen don't visible. (And yes, my english is bad, sorry ^^')
Comment 9•10 years ago
|
||
(In reply to jonathanmm from comment #8) > It's a private app, and I can't share an url or source. But, I watched, when > the server (Tomcat) have a charge > 1, to get a page can make more than 20 > sec on Chrome or Firefox on the tablet. I think the blank screen as a link > this it. The private app use AppCache, with an " appcache_path " in the > manifest, so I think for the first run, it's blank because the server is > very slow, but, for the next run, when the page is in the cache, it's fast > and the blank screen don't visible. Hmm, that would make sense, since the Android runtime actually ignores the appcache_path property. I filed bug 1048327 on honoring that property. See also related bug 925087. In the meantime, I'm going to close this bug, as it sounds like a different issue, but we don't have the information from the original reporter that we would need to debug it. Nevertheless, please reopen the bug if you can reproduce the original issue and provide additional information!
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•