I am working on nRF52840 DK with nRF5_SDK_15.2.0_9412b96 and I used the example ble_app_rscs_c with absolutely no changes. I first erased the flash and then burned the Softdevice and app to erase any bonding. I used LightBlue on my iPhone to advertise 0x1814 (BLE_UUID_RUNNING_SPEED_AND_CADENCE). The first time I received the pairing request on iPhone. Every time I restart the DK, I receive the following error several times (4 to 5 times):
<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Encryption, error: 4352
<info> peer_manager_handler: Connection secured: role: Central, conn_handle: 0, procedure: Encryption.
Although it finally works, these failures cause a long delay. I have also seen this problem reported for BLE peripheral examples but their solution (un-pairing from iPhone) does not work for me. I need to keep the devices paired.
I was wondering how I can fix this.
I have a similar issue, I'm using the ble_app_multirole_lesc example for nRF5_SDK_15.2.0_9412b96.I have erased 2 dev kits and placed the example on both.
When they try to connect I end up with this error:
<info> app: CENTRAL: Already connected to this device as PERIPHERAL (handle: 0), disconnecting.<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Encryption, error: 4352<warning> peer_manager_handler: Disconnecting conn_handle 0.<info> app: CENTRAL: Disconnected, handle: 0, reason: 0x16
And the other one:
<info> app: PERIPHERAL: Already connected to this device as CENTRAL (handle: 1), disconnecting.<info> app: PERIPHERAL: Disconnected, handle 1, reason 0x13.
I'm not able to have a connection and receive heart rate data. Any clue what can go wrong ?
I managed to reproduce the issue and have reported this internally. I will update this case when we find the cause of this issue.
I don't have any update on this matter for now, but in your case have you tried testing with other iphones to see if it makes any difference? I do manage to reproduce it but it isn't often like you see it. Also, it is working despite the error message, the security will retry until it succeed.
May I ask the root cause of this issue (if you have found it)?
The issue haven't been found yet.
This issue is also occurring for me but using an Android (Samsung Note 9).