NRF52832 SDK 17 NUS LESC with iphone as peripheral. Pairing problem.

[DmitrySol]

Hello!

NRF52832 is used as a central for connecting with phones as peripheral.
NUS service is used. Lesc is used too.

SDK 17
SoftDevice S132 V7.0.1

On android phones pairing dialog is shown. And pairing is finished successfully.

On the IOS pairing dialog doesn't show.

What may be cause?

[Simonr]

Hi

I need some more details in order to get a good look at what is going on here, please answer the following questions. 

• What iOS version(s) are you seeing this issue with?
• What application are you using to set up the iOS (and Android) as a peripheral here?
• Have you tried taking a sniffer trace to see what is going on during the pairing process?

Best regards,

Simon

[DmitrySol]

Simonr said:

What iOS version(s) are you seeing this issue with?

14

Simonr said:

What application are you using to set up the iOS (and Android) as a peripheral here?

It is our application. But It seems that pairing dialog is matter of bluetooth core. not application. Is it true?

Simonr said:

Have you tried taking a sniffer trace to see what is going on during the pairing process?

No. 

BR

Dmitry

[Simonr]

Hi Dmitry

We saw a similar issue in iOS v14.0.0 a few weeks ago, see this thread, where another DevZone user reported seeing this issue specifically in iOS v14.0.0 due to this version requiring distribution keys that the nRF5 SDK does not support. The user reported that both iOS versions v13.0.0 and v14.2 beta2 were both able to connect and pair with his nRF52 central. We're currently looking into this, but has not found a workaround for pairing to work in iOS v14.0.0.

You can check if this is the case for you as well by taking a sniffer trace of the connection and check if the Link and Signature Key in the Initiator Key Distribution which is part of the Bluetooth Security Manager Protocol event.

I will update this ticket on any updates on this case as well.

Best regards,

Simon

[DmitrySol]

Hi Simon

Thanks for fast reply

I'll check what you suggest.

and will be waiting workaround method

or new ios version

BR

Dmitry