User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20161001030430 Steps to reproduce: For quite some time this happens both in Firefox Nightly and Thunderbird Daily. Different Windows versions, both 32 and 64 bits; and many client versions, not only the latest. Automatic updates should be disabled; and let's assume there is an update is available. Bring up "About Nightly/Daily" dialog, press "Check for updates" button. Actual results: Quite often text "Nightly/Daily is up to date" would be seen instead of "Update Nightly/Daily to ..." button. Spacebar or Enter could be used to repeat search for updates. 1-3 retries usually were enough to get the "Update ..." button. Expected results: Retries should be avoided. In case of error a button should be available for repeated checks.
John, would you have time to check this on nightly? psn, can you be more specific please about "For quite some time". Are we talking 6 weeks, 6 months, 1 year?
Hard to tell; let's call it a year.
psn do you still see this problem?
Component: Untriaged → General
Flags: needinfo?(johnlgalt) → needinfo?(psn)
Summary: Manual search for updates is unreliable → Manual "Check for updates" for newer application is unreliable, both Firefox and Thunderbird
It kept happening fairly recently. However, only one case since the time of needinfo request, and even that was after "double-tapping" spacebar. That is, spacebar was pressed again after search for updates was already initiated; though I do not know if that interferes with the already running update check.
Small additional testing. Assuming that updates do exist, open About... dialog. Quickly pressing spacebar twice appears to be a sure way for getting "... is up to date" resposnse even if updates are available. But single key press discovers updates. To make it clear: my initial report was based on cases when I paid special attention to use single keypresses. Or even clicked "Check for updates" button using mouse.
You need to log in before you can comment on or make changes to this bug.