Lost configurations and nagging

Is there easy way to prevent Arduino 2.x to continously to ask to update boards and libraries?
I mean the new versions too often, just do not work. For example new ESP32 3.3.0 with LVGL does not compile but wit ESP32 3.2.1 is just fine.
And, when new board library version is changed the settings in Tools menu, like flash size and PSRAM option are cleared. I do not get why this happens because those parameters are project HW specific and not library version specific parameters. The behaviour is not logical.

The best way of course would be to have capability to freeze project configuration including library versions.

Hi @mos99.

  1. Press the Ctrl+Shift+P keyboard shortcut (Command+Shift+P for macOS users) to open the "Command Palette".
    A menu will appear on the editor toolbar:
  2. Select the "Preferences: Open Settings (UI)" command from the menu.
    ⓘ You can scroll down through the list of commands to find it or type the name in the field.
    A "Settings" tab will open in the Arduino IDE main panel.
  3. Type arduino.checkForUpdates in the "Search Settings" field of the "Settings" tab.
  4. Uncheck the box under the "Arduino: Check For Updates" setting.
  5. Close the Preferences tab by clicking its X icon.

If you disable the automatic update check, make sure to periodically do a manual check for newer versions of Arduino IDE and any installed boards platforms and libraries you do wish to keep up to date.

You can check for new versions of Arduino IDE by selecting Help > Check for Arduino IDE Updates from the Arduino IDE menus.

You can check for new versions of boards platforms and libraries by the following procedure:

  1. Press the Ctrl+Shift+P keyboard shortcut (Command+Shift+P for macOS users) to open the "Command Palette".
  2. Select the "Arduino: Update Indexes" command from the menu.
    A notification will appear at the bottom right corner of the Arduino IDE window to indicate the progress of downloading the index files.
  3. Wait for the index file downloads to finish.
  4. Select Tools > Board > Boards Manager... from the Arduino IDE menus to open the "Boards Manager" view in the left side panel.
  5. Select "Updatable" from the "Type" menu in the Boards Manager view.
    A list of installed boards platforms for which updates are available will be listed.
  6. Click the "UPDATE" button on the entry for any platform you wish to update.
  7. Select Tools > Manage Libraries... from the Arduino IDE menus to open the "Library Manager" view in the left side panel.
  8. Select "Updatable" from the "Type" menu in the Library Manager view.
    A list of installed libraries for which updates are available will be listed.
  9. Click the "UPDATE" button on the entry for any library you wish to update.

The correct term is "platform":

https://arduino.github.io/arduino-cli/latest/platform-specification/

In cases where that term alone might be ambiguous, I like to use the more descriptive "Arduino boards platform".

This happens because the developers of the platform you updated changed the machine identifiers for those "custom board options" in their board definitions.

Arduino IDE does remember the configuration of the board, but it remembers it using the identifiers from the board definition at the time you selected them. There is no way for the IDE to translate to the new identifiers if the platform developer pulls the rug out from under it by changing them.

Unfortunately I have seen that it is common for 3rd party platform developers to not understand or accept that the custom board option identifiers are part of their platform's API. These developers will make breaking changes to the identifiers without even documenting the change, even though they would not consider doing the same for the programming API of their core and libraries.

The Arduino IDE developers are tracking this request here:

If you have a GitHub account, you can subscribe to that thread to get notifications of any new developments related to this subject:


:red_exclamation_mark: Please only comment on the GitHub issue thread if you have new technical information that will assist with the resolution. General discussion and support requests are always welcome here on the Arduino Forum.