You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.
Currently, if the user starts the updater a second time, and reboots are required, it will happily run through the whole "checking for updates" process again before letting the user know that they have to reboot. Instead, we should immediately alert the user that a reboot is required to apply available updates.
The screen for successful updates that require a reboot currently looks like this:
[====100%====] All updates complete!
A reboot is required for security updates to be applied.
Please click the Reboot button to continue.
[Reboot]
I think if the user launches the updater again now without having rebooted, it should immediately show a screen similar to the above, with two differences:
omit the progress bar
instead of "All updates complete", say something like "One more step" or omit the text (can kick this around a bit on this issue).
The text was updated successfully, but these errors were encountered:
Tracking as stretch goal since it's an annoying waste of the user's time in a secondary path. The "happy path" is that the user immediately requests a reboot.
Currently, if the user starts the updater a second time, and reboots are required, it will happily run through the whole "checking for updates" process again before letting the user know that they have to reboot. Instead, we should immediately alert the user that a reboot is required to apply available updates.
The screen for successful updates that require a reboot currently looks like this:
I think if the user launches the updater again now without having rebooted, it should immediately show a screen similar to the above, with two differences:
The text was updated successfully, but these errors were encountered: