Device: Unagi Build: B2G 18 12/19/2012 Steps: 1. Submit the version 1.0 of this privileged app to marketplace-dev.allizom.org 2. Get a reviewer to approve the app and push it out publicly 3. Install the privileged app to your device 4. Upload a new version of the privileged app (v1.1 zip file attached) in the manage status & versions area 5. Get a reviewer to approve the app and push it out publicly 6. Go to settings --> device info --> check for updates (check now) 7. When the update notification appears, approve the update 8. Launch the updated app Expected: The app content should load. Actual: The app content fails to load. Note - see bug 823150 for the actual files involved.

I'm going to dig into this one a bit more to try to get more information.

I was able to reproduce this with a different signed packaged privileged app. So this is 100% reproducible.

Not blocking but tracking. Workaround would be to delete the app then reload it from Marketplace.

(In reply to David Scravaglieri [:scravag] from comment #3) > Not blocking but tracking. Workaround would be to delete the app then reload > it from Marketplace. That basically destroys the whole point of the feature. And that's not an acceptable work-around. If you want to contest taking this out of scope, then that requires a much larger discussion. But I don't think that's an option for this feature set. Back into triage it goes. This definitely is a P1 blocker.

Based on the fact that this could result in data loss for the user. Blocking.

dietrich - who is this assigned to?

(In reply to Caitlin Galimidi from comment #6) > dietrich - who is this assigned to? Nobody at the moment. But I'd recommend seeing if we get help from Etienne first. Etienne - Can you take a look at this? Any ideas?

(In reply to Jason Smith [:jsmith] from comment #7) > (In reply to Caitlin Galimidi from comment #6) > > dietrich - who is this assigned to? > > Nobody at the moment. But I'd recommend seeing if we get help from Etienne > first. Etienne - Can you take a look at this? Any ideas? Mmmh... app failing to launch does sound like a platform issue at first. Jason do you have the setup to make a custom build with the debug function uncommented in dom/apps/src/Webapp.jsm?

(In reply to Etienne Segonzac (:etienne) from comment #8) > (In reply to Jason Smith [:jsmith] from comment #7) > > (In reply to Caitlin Galimidi from comment #6) > > > dietrich - who is this assigned to? > > > > Nobody at the moment. But I'd recommend seeing if we get help from Etienne > > first. Etienne - Can you take a look at this? Any ideas? > > Mmmh... app failing to launch does sound like a platform issue at first. > Jason do you have the setup to make a custom build with the debug function > uncommented in dom/apps/src/Webapp.jsm? At the moment, no. Since it's platform, let's try Fabrice next. Fabrice - Any ideas?

Gregor: Is this something you could have a look at? Also cc'ing Fernando who has been looking at this code before.

I'm writing tests for this over in bug 826058.

I see what I can do.

(In reply to Gregor Wagner [:gwagner] from comment #12) > I see what I can do. Let me know if you need admin access to marketplace dev to test this out.

(In reply to Jason Smith [:jsmith] from comment #13) > (In reply to Gregor Wagner [:gwagner] from comment #12) > > I see what I can do. > > Let me know if you need admin access to marketplace dev to test this out. Yes this would be great. Is there also some documentation for it?

Looks like something may have fixed this. I'm able to launch the app....although the app wasn't really ever updated. I'll update bug 826940 with new data based on what i've found.