Re: Bonding completed notification
Re: Bonding completed notification
- Subject: Re: Bonding completed notification
- From: Martijn The <email@hidden>
- Date: Wed, 23 Sep 2015 15:07:14 +0200
FWIW, how we're dealing with these shortcomings:
1. We're using a notifiable characteristic which value tells the app A) whether the link is encrypted (so iOS/master must have valid LTK) and B) whether the device itself has a bonding for the other device. This way the app can know when iOS has a bonding (it was able to encrypt the link, which will always happen automatically by iOS/master at the start of the connection) and also whether our device has a bonding. When there's a "half pairing" situation, we unfortunately have to instruct the user to go to iOS Settings / Bluetooth and "Forget" from there, since there is no (public) API to remove pairings...
2. We're using a GATT operation to let our app tell our device (slave/peripheral) it's time to pair -- our device will then send the "Slave Security Request". This only seems to work if the app is foregrounded *and* connected to the app (through CoreBluetooth). We didn't like the implicit pairing, because we want fine control when the pairing happens so the app can decide when it is appropriate from a UX point of view to bring up the pairing.
Hope it helps.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden