NimBLE: Error while removing IRK
- Dominant language
- C
- Stars
- 893
- Forks
- 512
- Avg merge
- 13d 31m
- Merged PRs (30d)
- 7
Description
Checklist
Checked the issue tracker for similar issues to ensure this is not a duplicate
Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
Tested with the latest version to ensure the issue hasn't been fixed
**How often does this bug occurs?**
often
**Expected behavior**
I expected to see BLE pairing working fine after an esp32 factory reset
**Actual behavior (suspected bug) :**
After an esp32 factory reset, some devices fail to connect over BLE again (does not always happen). I get an error saying NimBLE: Error while removing IRK and I could not find a way to get it to work again.
**Error logs or terminal output**
I (5864) NimBLE: GATT procedure initiated: notify;
I (5874) NimBLE: att_handle=20
I (12714) NimBLE: GAP procedure initiated: terminate connection; conn_handle=0 hci_reason=19
E (12724) NimBLE: Error while removing IRK
I (12944) ble: disconnect, reason=534
W (12944) ble: client disconnected, connection id=0 [MAC ADDRESS]
I (12974) NimBLE: GAP procedure initiated: advertise;
I (12974) NimBLE: disc_mode=2
I (12984) NimBLE: adv_channel_map=0 own_addr_type=0 adv_filter_policy=0 adv_itvl_min=0 adv_itvl_max=0
I (12994) NimBLE:
**Steps to reproduce the behavior:**
Perform a factory reset on esp32, Bonds are deleted using the ble_store_clear() function.
Attempt to connect over BLE again.
Get the above error
**Project release version**
Shipped with ESP-IDF 5.2.2
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with ESP-IDF 5.2.2: perform a factory reset, call ble_store_clear(), and reconnect over BLE. Trace the bond and IRK removal path around the reported “Error while removing IRK” message and compare it with the disconnect logs. Done means BLE pairing works reliably after the reset without the IRK-removal error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100