Closed
Bug 1036680
Opened 10 years ago
Closed 10 years ago
[B2G][Homescreen]Installing an app while receiving a call will cause there to be no icon on the homescreen
Categories
(Core Graveyard :: DOM: Apps, defect)
Tracking
(blocking-b2g:2.0+, b2g-v1.4 unaffected, b2g-v2.0 affected, b2g-v2.1 unaffected)
RESOLVED
WORKSFORME
blocking-b2g | 2.0+ |
Tracking | Status | |
---|---|---|
b2g-v1.4 | --- | unaffected |
b2g-v2.0 | --- | affected |
b2g-v2.1 | --- | unaffected |
People
(Reporter: dharris, Unassigned)
References
()
Details
(Keywords: smoketest, Whiteboard: [273MB-Flame-Support][2.0-exploratory][systemsfe])
Attachments
(1 file)
(deleted),
text/plain
|
Details |
Description: While the user is installing an app and recieving a phone call at the same time, the app will finish installing, but there will be icon shown on the homescreen Prerequisite: Have wifi enabled Repro Steps: 1) Update a Flame to Build ID: 20140707000200 2) Open Marketplace App> Start downloading any app 3) While the app is downloading and installing, receive a phone call 4) Go to the homescreen Actual: The app will be installed, but there will be no Icon visible on the homescreen Expected: App icons appear on the homescreen when apps are downloaded Flame 2.0 Environmental Variables: Device: Flame 2.0 Build ID: 20140708000322 Gaia: e935f4ff190b76c70d9b2af8856c542a6e4a7546 Gecko: 3f9d7a3a0b7b Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Keywords:Marketplace, Install, Download, Call, Dialer, Receive, Incoming, Inbound, Icon, App, Marketplace Repro frequency: 100% See attached: Logcat, Video - http://youtu.be/ODhXWcRTyCU
Reporter | ||
Comment 1•10 years ago
|
||
This issue only occurs on Flame 2.0 with 273MB memory. This issue will NOT reproduce on Flame 2.1 or Flame 1.4 Flame 2.1 Environmental Variables: Device: Flame Master Build ID: 20140709040203 Gaia: 0f9f11d0a6dadb3ea27160204bbe911c1ad69a6f Gecko: 196d05832e12 Version: 33.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Flame 1.4 Environmental Variables: Device: Flame 1.4 Build ID: 20140709003002 Gaia: b0e9b4bdb39c5eb93a6783a34624ffc84f62b126 Gecko: acf704e54e19 Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 All apps will install and correctly show an icon on the homescreen even when there is an incoming call
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 2•10 years ago
|
||
Adding Smoketest blocker because I was able to reproduce this issue without having a phone call by following these steps. 1. Launch Marketplace 2. Search for and install apps e.g. 'Terra' 'Cut the rope' 'Yummi Squares' 3. Once installed, press the 'Home' button Actual: Installed apps are not displayed on the homescreen. Expected: Installed apps are displayed on the homescreen. Repro rate: 80%
Keywords: smoketest
Comment 3•10 years ago
|
||
This issue needs to be checked on the Flame with 512mb of memory, the Buri and the Open C if deemed necessary. Also, you should specify the memory of each Flame device that was tested.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(dharris)
Reporter | ||
Comment 4•10 years ago
|
||
This issue does NOT occur on Buri 2.1, Open C 2.1, Buri 2.0, Open C 2.0, Buri 1.4, Open C 1.4, or Flame (512mb) Icons will always appear on the homescreen when they are downloaded and installed Buri 2.1 Environmental Variables: Device: Buri Master Build ID: 20140709073020 Gaia: c394b7b4205b6f1a6ca44915fc08650f3ad127ec Gecko: 2d88803a0b9c Version: 33.0a1 (Master) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Open C 2.1 Environmental Variables: Device: Open_C Master Build ID: 20140708040218 Gaia: 740faa5d0060fb218b407cf224330654ddf833a5 Gecko: 465280604ea6 Version: 33.0a1 (Master) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Buri 2.0 Environmental Variables: Device: Buri 2.0 Build ID: 20140709063007 Gaia: 1774027323bb072b4ebdfea9883572bcf2535c87 Gecko: 11b6493a7d8f Version: 32.0a2 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Open C 2.0 Environmental Variables: Device: Open_C 2.0 Build ID: 20140708000322 Gaia: e935f4ff190b76c70d9b2af8856c542a6e4a7546 Gecko: 3f9d7a3a0b7b Version: 32.0a2 (2.0) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Buri 1.4 Environmental Variables: Device: Buri 1.4 Build ID: 20140709003002 Gaia: b0e9b4bdb39c5eb93a6783a34624ffc84f62b126 Gecko: acf704e54e19 Version: 30.0 (1.4) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Open C 1.4 Environmental Variables: Device: Open_C 1.4 Build ID: 20140709000201 Gaia: b0e9b4bdb39c5eb93a6783a34624ffc84f62b126 Gecko: acf704e54e19 Version: 30.0 (1.4) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Flame 2.0 (512mb) Environmental Variables: Device: Flame 2.0 BuildID: 20140708000322 Gaia: e935f4ff190b76c70d9b2af8856c542a6e4a7546 Gecko: 3f9d7a3a0b7b Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 The original test was done with Flame 2.0 (273 mb memory) and is the only device the issue occurs on
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(dharris) → needinfo?(ktucker)
Comment 5•10 years ago
|
||
Please update the appropriate tracking flags.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(dharris)
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 6•10 years ago
|
||
There should never be an instance of an app icon not showing once an app has been downloaded. This is a regression from 1.4 so nominating this 2.0?
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 8•10 years ago
|
||
After the install we see this in the logs which doesn't look so good, but I'm not quite sure what it means either: 07-09 15:53:31.378 3892 3892 E GeckoConsole: [JavaScript Error: "A promise chain failed to handle a rejection. 07-09 15:53:31.378 3892 3892 E GeckoConsole: 07-09 15:53:31.378 3892 3892 E GeckoConsole: Date: Wed Jul 09 2014 15:53:29 GMT-0700 (UTC) 07-09 15:53:31.378 3892 3892 E GeckoConsole: Full Message: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage]" {file: "resource://gre/modules/Webapps.jsm" line: 3644 column: 0 source: "3644"}] We can find that line here: https://github.com/mozilla/gecko-dev/blob/65073f3114a216a57ddb663e377df7795d49170e/dom/apps/src/Webapps.jsm#L3644 There are a few logging messages from the verticalhome app in the logcat, but these mostly look harmless. I think we should look into what this Webapps message means, and if we need to fix it or not. Moving to Core -> Apps.
Component: Gaia::Homescreen → DOM: Apps
Product: Firefox OS → Core
Comment 9•10 years ago
|
||
Once thing that we may want to check is the 1.4 homescreen running on 2.0 gecko code to see if this reproduces to verify if it is a gecko or gaia problem. I will try to reproduce tomorrow.
QA Whiteboard: [QAnalyst-Triage+] → [VH-FL-blocking-][VH-FC-blocking+][QAnalyst-Triage+]
Updated•10 years ago
|
Whiteboard: [273MB-Flame-Support][2.0-exploratory] → [273MB-Flame-Support][2.0-exploratory][systemsfe]
Comment 10•10 years ago
|
||
I am not able to reproduce this issue on 2.0 Flame 273MB Environmental Variables: Device: Flame 2.0 Build ID: 20140710000201 Gaia: 35a9b715e7348ec738ff6c8a59f50190390a06f2 Gecko: 94714370dfc3 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Comment 11•10 years ago
|
||
Did you chat with the reporter & lead about this?
Flags: needinfo?(jschmitt)
Comment 12•10 years ago
|
||
Yes I did. Adding qawanted to verify if it repros.
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking+][QAnalyst-Triage+] → [VH-FL-blocking-][VH-FC-blocking+][QAnalyst-Triage?]
Flags: needinfo?(jschmitt) → needinfo?(pbylenga)
Keywords: qawanted
Updated•10 years ago
|
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking+][QAnalyst-Triage?] → [VH-FL-blocking-][VH-FC-blocking+]
Flags: needinfo?(pbylenga)
Comment 13•10 years ago
|
||
I'm also unable to repro this bug on 2.0 Flame. Tried all the apps in Comment 2 with a total of 10 repro attempts. I tried both the repro steps in comment 0 and comment 2 with no luck. Environmental Variables: Device: Flame 2.0 Build ID: 20140710134018 Gaia: 1bd6e8957ccf310b2f75ba5695b058a2e284df3a Gecko: f0e91a6bfd1b Version: 32.0a2 (2.0) Firmware Version: v122
Comment 14•10 years ago
|
||
Multiple parties report no repro from today's 2.0 build. Closing this as Works-for-me
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking+] → [VH-FL-blocking-][VH-FC-blocking+][QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•