Description
Describe the problem
Arduino IDE now has an auto update capability (#797).
After downloading an update, the user is offered two options:
From #797 (comment)
when a newer version is downloaded, the user can restart the application to apply the new changes, or just close the window; in the last case, the changes will be applied at the next start-up
🐛 In contradiction to the described behavior, after you select Not now and then close the Arduino IDE, the postponed update is installed immediately.
To reproduce
-
In order to force an update offer, download an outdated nightly build, using the variant that supports auto-update for your OS.
Latest outdated URLs at the time of writing are here:These download URLs can be derived from that of the current nightly by decrementing the date component.
-
Install the downloaded application as usual
-
Start the installed Arduino IDE.
-
Open the "Command Palette".
(Ctrl+Shift+P or Command+Shift+P by default) -
Run the "Preferences: Open Settings (UI)" command.
-
Change the "Arduino › Ide: Update Channel" (
arduino.ide.updateChannel
) setting to "nightly". -
Select File > Quit from the Arduino IDE menus.
-
Start the installed Arduino IDE.
-
Wait for the IDE to finish loading.
-
Click the Download button on the "Update Available" dialog.
-
Wait for the download to finish.
-
Click the Not now button on the "Arduino IDE ___ has been downloaded." dialog.
-
Select File > Quit from the Arduino IDE menus.
-
Watch the Arduino IDE installation folder.
🐛 The IDE is updated immediately after exit, not on the next start-up.
The installation takes some time and there is no feedback to the user that an operation is in progress, so they might try to open the IDE again or shut down their machine during the installation.
Expected behavior
Postponed update behavior matches described behavior: update occurs on the next start-up.
Arduino IDE version
Original report
2.0.0-rc4-snapshot-354b74c
Last verified with
Operating system
- Windows
Operating system version
- Windows 10
- Windows 11
Issue checklist
- I searched for previous reports in the issue tracker
- I verified the problem still occurs when using the latest nightly build
- My report contains all necessary details