User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090118 Minefield/3.2a1pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090118 Minefield/3.2a1pre I had Minefield 20090116035550 installed. Just an hour or so ago, I went to download the newest nightly, which would have been 20090118033414. However, apparently (i'm guessing the auto downloader) grabbed 20090117033728 first. I had to install that build before downloading and installing 20090118. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Actual Results: I had to download each nightly individually. Expected Results: The downloader should have bypassed any older nightlies and gone to the most recent build.

You're talking about the built-in app updater ?

Can you please provide a url to a nightly along with steps to reproduce? Thanks

Also moving over to app update. If this is in fact the installer then this bug should be filed under a component more suitable toward the downloading of the installer (e.g. mirrors, download mgr., whatever).

I would guess this is the same as bug 431779 - basically you want nightly updates to prompt you and then d/l at full speed in the foreground, not trickle d/l in the background.

Like I said, I had build 20090116035550 (win32) installed on my machine. I didn't install 20090117... first when it originally came out. I booted up my computer today (Sunday, the 18th) and the "Help, check for updates" menu came back with 20090117. I downloaded that, and THEN was able to download the 20090118 build. In other words: One day I installed "Build A" The next day, I did nothing. This is when "Build B" came out. On the third day, I tried to install "Build C", but it downloaded "Build B" first. Upon installation of "Build B", was I able to download and install "Build C." It does seem like this one could be similar to bug 431779, as posted in comment #4, but someone with more technical know-how than I would have to be the one to say so.

Do you know what your local time was when you got offered build b ?

I'd make a rough guess that it was approximately 5:30 to 6:00 PM US ET. Usually the first thing I do when I get Minefield fully started is check for updates for extensions and builds. It should have offered me the most current build right away, regardless of if I missed any, correct? If I was away for a week and missed multiple builds, i'd hate to have to download nightlies for 25 minutes.

Indeed, you should always get the latest build, but if you have the update preferences on their default values then Firefox can start downloading an update in the background. Then you go Check for Updates then brings the d/l into the foreground without checking with the update server again.

Yesterday, approx 2:25 PM ET, I downloaded a nightly build for the same day as the one listed below (just an earlier hourly.) There was a yellow notification bar which I hadn't previously seen before so I immediately checked for any newer hourlies. At 2:29 PM ET yesterday, I downloaded the nightly listed below. I did have nightlies from 20090216 and 20090217 installed before. Once again, it seems like the downloader isn't grabbing the newest build, but it seems to be very random as to when this bug occurs. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090218 Minefield/3.2a1pre (.NET CLR 3.5.30729) ID:20090218033257

This does seem the same as bug 353804 so duping