Closed
Bug 823189
Opened 12 years ago
Closed 12 years ago
Installing a signed packaged app, updating it on the server, doing a manual sync, and completing the update - app fails to launch
Categories
(Firefox OS Graveyard :: General, defect, P2)
Tracking
(blocking-basecamp:+)
People
(Reporter: jsmith, Assigned: gwagner)
Details
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.
Reporter | ||
Updated•12 years ago
|
Blocks: b2g-app-updates, market-packaged-apps
blocking-basecamp: --- → ?
Reporter | ||
Comment 1•12 years ago
|
||
I'm going to dig into this one a bit more to try to get more information.
Keywords: qawanted
QA Contact: jsmith
Reporter | ||
Comment 2•12 years ago
|
||
I was able to reproduce this with a different signed packaged privileged app. So this is 100% reproducible.
Keywords: qawanted
Comment 3•12 years ago
|
||
Not blocking but tracking. Workaround would be to delete the app then reload it from Marketplace.
blocking-basecamp: ? → -
tracking-b2g18:
--- → +
Reporter | ||
Comment 4•12 years ago
|
||
(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.
Comment 5•12 years ago
|
||
Based on the fact that this could result in data loss for the user. Blocking.
blocking-basecamp: ? → +
Priority: -- → P2
Target Milestone: --- → B2G C3 (12dec-1jan)
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(dietrich)
Comment 6•12 years ago
|
||
dietrich - who is this assigned to?
Reporter | ||
Comment 7•12 years ago
|
||
(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?
Flags: needinfo?(etienne)
Comment 8•12 years ago
|
||
(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?
Flags: needinfo?(etienne)
Reporter | ||
Comment 9•12 years ago
|
||
(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?
Component: Gaia::System → General
Flags: needinfo?(fabrice)
Updated•12 years ago
|
Assignee: nobody → fabrice
Gregor: Is this something you could have a look at?
Also cc'ing Fernando who has been looking at this code before.
Comment 11•12 years ago
|
||
I'm writing tests for this over in bug 826058.
Reporter | ||
Comment 13•12 years ago
|
||
(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.
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(fabrice)
Updated•12 years ago
|
Target Milestone: B2G C3 (12dec-1jan) → B2G C4 (2jan on)
Assignee | ||
Comment 14•12 years ago
|
||
(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?
Reporter | ||
Comment 15•12 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Updated•12 years ago
|
No longer blocks: market-packaged-apps
Reporter | ||
Updated•12 years ago
|
No longer blocks: b2g-app-updates
You need to log in
before you can comment on or make changes to this bug.
Description
•