NRF_ERROR_INTERNAL while bonding?

[Gordon]

Hi,

After finding that Windows doesn't like HID devices if they can't be bonded to, I've been attempting to add peer_manager and bonding into my application.

However, having added it I'm getting loads of problems. I can connect normally, but:

Bonding (using nRF Connect) appears to work, but immediately after disconnecting, I get NRF_ERROR_NOT_FOUND from pm_whitelist_set in the BLE_GAP_EVT_DISCONNECTED handler (and the device resets).

Even after removing all the whitelist code (which I'm not too worried about), when attempting to bond I get NRF_ERROR_INTERNAL which comes via the PM_EVT_ERROR_UNEXPECTED handler (and the device also resets)

Any thoughts what could be the issue here? The internal error sounds a bit worrying.

The code that changed in order to add the peer manager without whitelist :

github.com/.../c969f3c52cb39cd0a66df6da4e22d61241486071...BLE_peer_manager_no_whitelist

Same code, but with the whitelist:

github.com/.../c969f3c52cb39cd0a66df6da4e22d61241486071...BLE_peer_manager

Is there anything obvious I've missed here? It kind of seemed like I'd got everything, but it's hard to tell from just looking through the HID example.

[Gordon]

I was getting NRF_ERROR_INTERNAL occasionally before as well - I was just also getting the pm_whitelist_set error every time I disconnected after bonding... So I think there are two problems. Realistically the NRF_ERROR_INTERNAL is the one I care about, since I don't need whitelisting at the moment.