723365 - Already in-progress app-update is not shown in notification bar after Fennec restarts after force quit

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect, P3)

Description

[Ed Morley [:emorley]]

Galaxy S2, Android 2.3.4, Fennec native 12.0a1 2012-01-30

1) Cold start Nightly
2) Hardware menu button -> More -> Settings -> About Nightly
3) Press "Check for updates"
4) Agree to start download on update notification in android notification bar
5) When update download gets stuck at X% and can't be cancelled, force quit Nightly using task manager
6) Repeat steps 1-3

Expected results:
At step #6, "Looking for updates..." -> "Update Available" -> Tap and then notification shows in android notification bar & able to start download again.

Actual results:
At step #6, "Looking for updates..." -> "Update Available" -> tapping button does nothing, no notification shows up in android notification bar & button caption returns to "Check for updates" after a few seconds. Restarting phone does not help.

Comment 1

[Ed Morley [:emorley]]

Attachment: Logcat output

Filtered with |grep -i 'gecko'| but have the full log locally.

Comment 2

[Ed Morley [:emorley]]

Hmmm... after trying half a dozen times, it's now offering to install the update without asking to download, which makes me think that it was actually downloading all the time, but was just not showing the notification.

I unfortunately don't have a copy of org.mozilla.fennec/files/Download/ from before it offered to install the update, but after comment 0's step #6, org.mozilla.fennec/files/Download/updates/0/update.status stated 'downloading', the apk in that folder was a few MB short of what I would have expected, and the update.version file was not present.

Comment 3

[Ed Morley [:emorley]]

Please don't close bugs without also commenting.

The reason I left this open, was that the behaviour in comment 0 and comment 2 is still not correct. The update should be re-shown in the notification bar if it is indeed still in progress, since:
a) There is otherwise now no way to cancel the download (eg: now roaming and need to save data)
b) The user thinks update is broken

Updating summary to reflect comment 2 finding (presuming my interpretation is correct).

Comment 4

[Ed Morley [:emorley]]

Mass-closing old bugs I filed that have not had recent activity/no longer affect me.