Closed
Bug 721649
Opened 12 years ago
Closed 12 years ago
Tapping update notification doesn't start update
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: nthomas, Unassigned)
Details
Steps to reproduce: 1, Install & start the native m-c nightly from the 20th (or later) 2, Load about:nightly (eg by opening the Settings and tapping 'About Nightly') 3, Tap the 'Check for Updates' button 4, Tap on the 'Download & Install...' notification in the lower right At this point there should be a dialog to confirm you want to update, but that doesn't appear in the broken build. Nothing appears to happen at all except for the notification getting dismissed. I'm testing on a Galaxy Tab 10.1 running Samsung's Android 3.2. It breaks somewhere between http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=58e933465c36&tochange=5c2bc94d359c which is between these two builds: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2012-01-19-03-11-05-mozilla-central-android/fennec-12.0a1.multi.android-arm.apk http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2012-01-20-03-11-25-mozilla-central-android/fennec-12.0a1.multi.android-arm.apk The XUL m-c nightly of the 20th doesn't have this problem, so that seems to exclude toolkit/mozapps/update/ (although there are several changes there), leaving http://pastebin.mozilla.org/1464027
Comment 1•12 years ago
|
||
Same on my Galaxy S2 phone. I've noticed this for past week or so and have to download nightly builds manually to update.
Reporter | ||
Comment 2•12 years ago
|
||
Updating from the nightly of the 26th worked for me, haven't had a change to look at the changelog yet.
Comment 3•12 years ago
|
||
Yes, looks like it's working for me again now too.
Comment 4•12 years ago
|
||
Thanks for the updates, please re-open if it happens again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•