Closed Bug 608837 Opened 14 years ago Closed 14 years ago

4.0b2 rc 1 does not automatically update to 4.0b2 rc 2

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nhirata, Assigned: lsblakk)

Details

1. download/install 4.0b2 rc1 
2. go to about:config
3. set app.update.enabled to true
4. set app.update.interval to 120
5. set app.update.timer to 12000
6. set app.partner.test to test
7. stop and restart fennec
8. wait for 6 minutes or so or go to about:firefox and click update button

Expected: 
If app.update.auto is false then a notification should appear in the system notifications, if app.update.auto is true then the install notification should appear.

Actual:
no notifications.
As stated in IRC, we only created updates from 4.0b1 build3 -> 4.0b2 build2.
Just noting this as a bug, since we went from having the updates for 4.0b1 build 1 -> 4.0b1 build 2 -> 4.0b1 build 3.

It doesn't make sense in terms of consistency if we also didn't go from 4.0b2 build1 to 4.0b2 build2 as well.
Assignee: nobody → lsblakk
The reason for that was we had no other release builds that would update to anything... 4.0b1 build1 was the first release build that could update to another build, so those were all we could test.

Since we now have a beta release out in the wild (4.0b1 build 3), it makes sense to test updating that build to the next build we may be releasing (4.0b2 build 2)
Ok, noting:
4.0b1 build 1 => 4.0b1 build 3
4.0b1 build 2 => 4.0b1 build 3
4.0b1 build 3 => 4.0b2 build 2

Would it be possible to include the 4.0b2 build 1/2 to 4.0b2 build 3 to verify the update button (located in about:firefox) that was introduced in 4.0b2 if there is a respin?
Try again now, I've set up a link to the update for 4.0b2 build1 to point to build 2
Thanks, Lukas.  It works now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Now that we respun, I need to wait for build 3 to test.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.