Closed Bug 831464 Opened 11 years ago Closed 11 years ago

Cannot finish downloading a large packaged app update from 17 KB --> 20 MB - app gets stuck at 0.00 KB with notification never disappearing

Categories

(Core Graveyard :: DOM: Apps, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 830294

People

(Reporter: jsmith, Unassigned)

Details

Attachments

(1 obsolete file)

Build: B2G 18 1/16/2013
Device: Unagi

Reference URL - http://mozqa.com/webapi-permissions-tests/large_packaged_update/

Steps:

1. Install the packaged app with state1.zip at the reference URL
2. Update the packaged app on the server to state2.zip
3. Check for updates (manual or automatic)
4. Update should be found - apply update for that app
5. Wait for a while

Expected:

The download should eventually finish - we should get an updated app.

Actual:

The download never finishes - we're getting 0.00 KB downloading spinning forever. What's weird here is that the webapps.json file says that it isn't downloading after a long period of time:

  "{404e3053-890d-40a0-a570-d3f16acb3658}": {
    "name": "Test WebAPI Permissions",
    "csp": "",
    "installOrigin": "http://mozqa.com",
    "origin": "app://{404e3053-890d-40a0-a570-d3f16acb3658}",
    "receipts": [],
    "installTime": 1358365150197,
    "manifestURL": "http://mozqa.com/webapi-permissions-tests/large_packaged_upd
ate/large_packaged_update.manifest",
    "appStatus": 1,
    "removable": true,
    "id": "{404e3053-890d-40a0-a570-d3f16acb3658}",
    "localId": 1024,
    "basePath": "/data/local/webapps",
    "progress": 20957079,
    "installState": "installed",
    "downloadAvailable": true,
    "downloading": false,
    "readyToApplyDownload": false,
    "downloadSize": 20000000,
    "lastUpdateCheck": 1358365150197,
    "etag": "\"2584e3-178-4d36cf5772ec0\"",
    "packageEtag": "\"2584e4-4365-4d2ef56325b00\"",
    "installerAppId": 1002,
    "installerIsBrowser": true,
    "lastCheckedUpdate": 1358365192997,
    "retryingDownload": false
  }

I tried launching the app - it still launches to the old content. So something might be getting stuck.

I'm guessing this is a different bug than the hosted app equivalent. If that ends up being wrong, feel free to dupe.
blocking-b2g: --- → tef?
Attached file Packaged App v1.0 (obsolete) —
Attachment #702993 - Attachment is obsolete: true
It's almost as if we actually did download the app entirely, but we failed when we tried to apply the update to the packaged app over the existing app.
It looks like the download succeeded (the size looks right, and downloadAvailable is true), but the update was not applied, so we didn't switch to the new package.

That could be a gaia issue, but we need debugging traces to confirm.
Just to clarify btw - I did test this over a good network.

I tested an exact test case where I successfully installed a packaged app on the same network that was 20 MB. So it isn't a weak network issue.
Jason, could you put the source for your app somewhere? so that I can test myself tomorrow. thanks
(In reply to Julien Wajsberg [:julienw] from comment #5)
> Jason, could you put the source for your app somewhere? so that I can test
> myself tomorrow. thanks

http://mozqa.com/webapi-permissions-tests/large_packaged_update/ is where I'm hosting the contents.

Use state1.zip for the first app you install. Then, do an update to state2.zip.
With the patch from bug 830294, I can't reproduce this bug.

I'll dupe on that bug. When that patch lands, I'll retest to see if I still reproduce the issue. If I do, I'll reopen.
Status: NEW → RESOLVED
blocking-b2g: tef? → ---
Closed: 11 years ago
Resolution: --- → DUPLICATE
No longer blocks: b2g-app-updates
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: