VERIFIED FIXED in B2G C3 (12dec-1jan)
Fabrice - Any ideas on what's going on here?
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
(CC'ing slithering devs MattN & jaws, in case they have any insights or have hit this themselves)
We both have this too and I started filing this bug but got distracted by another. I don't have any insights into this other than the fact that we do use AppCache and appcache_path in the app manifest so the game is available offline. We aren't a packaged app though.
We have however updated the app cache recently (within the past week or two) which might have gotten it into this state.
(In reply to Jared Wein [:jaws] from comment #4) > We have however updated the app cache recently (within the past week or two) > which might have gotten it into this state. Actually, the last change to it was October 28th.
Fabrice says there's a fix for this in a different bug. He'll follow up with details later (had to run).
Assignee: nobody → fabrice
Setting priority based on triage discussions. Feel free to decrease priority if you disagree.
Priority: -- → P1
I tested with the latest nightly, and that seems to be fixed (we landed several fixes to the update and download error reporting in other bugs). Can QA verify?
Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.
Target Milestone: --- → B2G C3 (12dec-1jan)
No QA yet, but speculatively closing
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(In reply to JP Rosevear [:jpr] from comment #10) > No QA yet, but speculatively closing Yeah, makes sense. I'll look in a little bit, but I *think* this is fixed for the same reasons Fabrice said in comment 8.
I haven't seen this bug on the latest builds nor anything that looks like the error seen in the logs. Marking as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.