PeerManager error (error: 133)

[takashina hiroki]

I have a question about PeerManager.

SDK: 15.3.0
example: ble_app_multirole_lesc (I changed the source from the sample)
using device: EYSHJNZWZ (nRF52832)
connection device: Android (Bluetooth v5.0)

When trying to connect with LESC security level using PeerManager, the following error occurred.
Please tell me the cause.

<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133
<warning> peer_manager_handler: Disconnecting conn_handle 0.

I know that this error means "BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP".
The connection partner supports pairing.
I confirmed that I could connect many times.
However, this error may occur.
Also, after this error occurs, the same error will occur no matter how many times you try to connect.
This error does not occur after reset.

[RMurias]

I am able to consistently reproduce this issue.

1) Build and run a Bluetooth app, e.g. the HRM example.

2) Set NRF_LOG_BACKEND_RTT_ENABLED = 1 to enable logging

3) Debug->Run

- Pairing from the phone starts for a brief moment and then stops, no indication of a problem.

- Debug log shows the above error.

4) Set NRF_LOG_BACKEND_RTT_ENABLED =  to disable logging

- The problem persists on the nRF-DK

5) Flash the Blinky example (copy the hex file to the JLINK foder)

6) Flash the HRM example, now you can pair again.

SUMMARY: If I enable logging with NRF_LOG_BACKEND_RTT_ENABLED = 1, I cannot pair a phone to the nRF52-DK. Reverting the setting does not fix the issue, I'm forced to flash a different build to the nRF52-DK before I can re-flash and pair.