Sure, that's an option. But it means that we now also need to have a switch in the app to determine which OTA to download an apply (on top of maintaining the 2 configs). What happens when we get the next change that requires splitting OTAs. This gets unmanageable quickly. If you've been doing Androi...

I don't think you are thinking this through. Or maybe I' not. Suppose I have have 2 build configs. ConfigA no MD5 in partition tables and not requiring it in boot loader and app ConfigB generating MD5 in partition tables and requiring it in boot loader and app They will each generate partition table...

Just like every other project, we will be be building the application to be sent OTA as well as flashed onto new devices. We could build multiple configurations of the same app, one for OTA, one for new devices, but what would be the point? The new devices would eventually received the OTAs, so they...

Wait. Setting CONFIG_ESP32_COMPATIBLE_PRE_V3_1_BOOTLOADERS=yCONFIG_ESP32_COMPATIBLE_PRE_V3_1_BOOTLOADERS=y auto changed # CONFIG_PARTITION_TABLE_MD5 is not set Ie unset the MD5 generation on the partition table So when I build my partition table has no MD5. Wasn't the whole point of this to roll for...

Brilliant thanks - that was doing my head in.

OK, so where/how dop I configure "App compatible with bootloader and partition table before ESP-IDF v3.1" According to https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/kconfig.html#config-app-compatible-pre-v3-1-bootloaders it should be visible in the BuildType section of Me...

Ah. Thanks. Missed that in the breaking changes.
You might want to highlight the impact of that breaking change.

ESP_igrr

Yes. The devices were built with IDF 3.3 using CMake.
So 3.3 bootloader and 4.4.2 app

Reported here: https://github.com/espressif/esp-idf/issues/9987

That's perfect, thank you.