817819 - App updates run erratically, then fail

Status: RESOLVED DUPLICATE of bug 812931

(Firefox OS Graveyard :: Gaia::System, defect)

Description

[John Hammink]

# Environment
Unagi
Nightly build 12/2/2012
Unagi BuildID= 20121202070809
Gecko - b7a71a10d566babce419b4fde0f6be602bc540eb
Gaia  - f48b93eafbeb3f93c9575b8bca733113ee611a52

There is erratic behavior and failure of app  updates (in this case, marketplace).

After flashing 12/2/ build:
1.  Notification comes with 3 updates (dev marketplace, staging marketplace and marketplace)
appears.
2.  I Selected only "marketplace" and unchecked other two.
3. Hit the button to download.

Actual:  Download appears to work  - at first - but then screen returns to notification (with three updates).  
Update is not installed.

adb logcat gives this output before the update fails:
12-03 13:04:47.681: DEBUG/memalloc(109): /dev/pmem: Freeing buffer base:0x4c134000 size:40960 offset:2310144 fd:165
12-03 13:04:47.681: DEBUG/memalloc(109): /dev/pmem: Freeing buffer base:0x4c1ec000 size:40960 offset:3063808 fd:197
12-03 13:04:47.751: DEBUG/memalloc(109): /dev/pmem: Freeing buffer base:0x4c13e000 size:8192 offset:2351104 fd:207
12-03 13:04:47.761: DEBUG/memalloc(109): /dev/pmem: Freeing buffer base:0x4c1fc000 size:8192 offset:3129344 fd:212
12-03 13:04:48.291: DEBUG/memalloc(109): /dev/pmem: Freeing buffer base:0x4c1fe000 size:16384 offset:3137536 fd:170
12-03 13:04:48.301: DEBUG/memalloc(109): /dev/pmem: Freeing buffer base:0x4c1f6000 size:16384 offset:3104768 fd:202

Comment 1

[Marcia Knous [:marcia]]

I see the same issue using the build on 20121128 on my nightly testing unagi device.

Comment 2

[John Hammink]

And I see the issue when trying to upgrade from 11/30 - 12/3.   Will also try 12/2 - 12/3

Comment 3

[John Hammink]

As it turns out, I was not prompted for app updates when updating 11/30 - 12/3.   So, cannot test that path.

Comment 4

[Tony Chung [:tchung]]

hey guys, you'll need to check logcat and grep on "aus:svc"

Look for something like: 

12-03 17:37:26.867: I/Gecko(2522): *** AUS:SVC Checker: checkForUpdates, force: true
12-03 17:37:26.867: E/GeckoConsole(2522): AUS:SVC Checker: checkForUpdates, force: true
12-03 17:37:26.897: I/Gecko(2522): *** AUS:SVC Checker:getUpdateURL - update URL: http://update.boot2gecko.org/nightly/update.xml?force=1
12-03 17:37:26.897: E/GeckoConsole(2522): AUS:SVC Checker:getUpdateURL - update URL: http://update.boot2gecko.org/nightly/update.xml?force=1
12-03 17:37:26.897: I/Gecko(2522): *** AUS:SVC Checker:checkForUpdates - sending request to: http://update.boot2gecko.org/nightly/update.xml?force=1
12-03 17:37:26.897: E/GeckoConsole(2522): AUS:SVC Checker:checkForUpdates - sending request to: http://update.boot2gecko.org/nightly/update.xml?force=1
12-03 17:37:27.598: I/Gecko(2522): *** AUS:SVC Checker:onProgress - 604/604
12-03 17:37:27.608: E/GeckoConsole(2522): AUS:SVC Checker:onProgress - 604/604
12-03 17:37:27.608: I/Gecko(2522): *** AUS:SVC Checker:onLoad - request completed downloading document
12-03 17:37:27.618: E/GeckoConsole(2522): AUS:SVC Checker:onLoad - request completed downloading document
12-03 17:37:27.648: I/Gecko(2522): *** AUS:SVC Checker:getUpdateURL - update URL: http://update.boot2gecko.org/nightly/update.xml?force=1
12-03 17:37:27.648: E/GeckoConsole(2522): AUS:SVC Checker:getUpdateURL - update URL: http://update.boot2gecko.org/nightly/update.xml?force=1
12-03 17:37:27.658: I/Gecko(2522): *** AUS:SVC Checker:onLoad - number of updates available: 1


If you dont see an update being served from the update.boot2gecko.org/nightly/update.xml channel, then you have a legitimate issue.   we can debug more if you can confirm there's nothing found.