By default, disabled the BLE Encrpyption requirement for provisioning characteristic.
With this flag enabled, when remote attempts to read and if the ACL link is not encrypted,
ESP device will return Insufficient Authentication. It is remote device responsibility to go
for link encryption which may result in pairing.
Some devices do not proceed for any pairing and just show failure pop-up. Also, user needs
to remove bonding on remote phone manually and then try again. This is causing bad user experience.
End user can enable it as per their use case.
If the user copies the BLE example to their own project without understanding the need to enable the BT stack or BTDM BLE settings in the SDK then their build will probably fail at this line due to linker errors.
Closes https://github.com/espressif/esp-idf/pull/6652
Closes IDFGH-4854
If users may try to use this (excellent) example code in their own projects, without understanding the need to enable the BT stack and BTDM settings in the SDK. If they do that then their builds will fail with linker errors but they may not understand why.
the binary size check in example test was removed long time ago. Now we
have updated ttfw_idf to raise exception when performance standard is
not found. These fake performance check will be regarded as error.
Remove them now.
Config options have been set such that BLE transport will be the default for ESP32
and SoftAP will be the default for ESP-S2.
CMakeLists.txt for all provisioning examples applicable for ESP32-S2 have also been updated
as these now work fine on ESP32-S2
Signed-off-by: Piyush Shah <piyush@espressif.com>
