Koxx3 opened a new issue, #1456: URL: https://github.com/apache/mynewt-nimble/issues/1456
Hello, I have troubles with Android phones and bonded ESP32 when adding/removing characteristics between 2 firmware releases (incorrect data reads, no answer on some characteristics ...) It seems a common issue, and I found a lot of users with the same troubles. I tried everything on the "client side" (Android cache refresh hack ... since it's not a public API), but it still doesn't work. I found that BLE seems to already include "a flag" to indicate the client it needs to refresh his cache... the "Service Change Indication". It doesn't seems NimBLEServer::serviceChanged() does the same thing (and it's not in the public API). https://github.com/h2zero/NimBLE-Arduino/blob/release/1.4/src/NimBLEServer.cpp#L168 Espressif seems to offer the API on bluedroid : https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/bluetooth/esp_gatts.html#_CPPv444esp_ble_gatts_send_service_change_indication13esp_gatt_if_t13esp_bd_addr_t it seems related to the 0x2A05 characteristic Could it be possible to offer an API for this in NimBLE please ? More info here : https://stackoverflow.com/questions/62155016/bluez-and-service-characteristics-cache-issue-with-android -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
