nrf52832 bonding to apple iphone

[Rickon]

Hi Friend,

I use nrf252832 MCU and SDK 15.3, 

I would like to Implement below function, 

1:Device bond phone A without password first , the phone A popups a bonding dialog box;

2: Disconnect phone A and  bond phone B,  the phone B popups a bonding dialog box;

Now it is right;

3:Then I connect phone A back, I want phone A to popup a bonding dialog box again;

If phone A is android phone ,it is ok, but if the phone A is a apple iPhone, it does not popup a bonding dialog box again and pair fail.

How can I bond the iPhone A back? 

The MAC address adding 1 seems make it work,but it is not a good methed.

Thanks!

[Mttrinh]

Hi,

Is there a reason that you want to bond again when you already have bonded the first time?

Do you mean to erase bonding data before connecting to phone A again?

[Mttrinh]

Hi,

Which SDK are you using? Are you using peer manager?

How are you storing your bonding data?

[Rickon]

I need phone popup a dialog box ,no matter what app I use, example:lightblue.

[Mttrinh]

Like I said, if your attributes require encryption, the peer device will initiate bonding when trying to access those attributes.  So the dialog box should pop up whenever you use a bluetooth app to connect to the device.

I suggest you have a look at the keyboard example on how the Peer manager is implemented.

[Rickon]

"if your attributes require encryption"

How could I set the attributes?

[Rickon]

I capture the data using Ellisys Bluetooth Analyzer and attached the data.

Type filter "*deskbike*".

When the device bond back to iPhone A, the device send "LLCP Rejected(PIN or Key Missing)".

How can I send this to iPhone A? 

Which api can I call and where I call it?

Thank you!!!!!

deskbike.rar

[Mttrinh]

Hi,

I have edited one of the earlier replies regarding allow_repairing, it will only work where the phone have lost/erased the bonding information while the nRF device still have it.

I'm not sure how the device you mentioned was able to bond back without "Forget your device". Are you sure that when testing with that device, that the bonding information was erased from nRF device while kept on phone? And not the other way around?

I suggest you allow more bonds instead of erasing the bonding information of the previous phone when bonding with a new phone. This should solve the issue.