Closed Bug 978089 Opened 11 years ago Closed 11 years ago

Installing an app with origin on the manifest fails to fire the ondownloadsuccess/applied events

Categories

(Core Graveyard :: DOM: Apps, defect)

Product:
Core Graveyard
Component:
DOM: Apps
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:1.4+, firefox28 wontfix, firefox29 wontfix, firefox30 fixed, b2g-v1.4 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla30
Project Flags:
blocking-b2g 1.4+
Tracking Flags:
Tracking Status
firefox28 --- wontfix
firefox29 --- wontfix
firefox30 --- fixed
b2g-v1.4 --- fixed

People

(Reporter: amac, Assigned: ferjm)

References

Details

(Keywords: regression) 

STR: 

Install an app that has a 

origin:

field on the manifest.

Expected:

The icon updates at the end of the installation and changes from the rocket to the real icon

Actual: 

The installation seems to hang and never finish. Rebooting the phone shows the correct app icon and status.

Cause: 

When the origin field is processed, a RemoveApp is sent to the child processes, followed up with a AddApp. The RemoveApp event handler removes the references to the DOM objects. And thus when any further event arrives for that app (like the downloadsuccess) it won't be processed since we don't know anymore which DOM APP objects exist.

STR: Any ondownloadsuccess/ondownloadapplied
Blocks: 880043
I'm guessing this is a regression from bug 903291.
blocking-b2g: --- → 1.4+
Keywords: regression
Blocks: 903291
Antonio - bug 903291 is backed out on b2g-inbound. I think that's what was causing this regression.

Can you still reproduce with bug 903291 backed out?
Flags: needinfo?(amac)
Confirmed, backing out 903291 fixed this also.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(amac)
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.