iOS and pairing/bonding issue

RE: iOS and pairing/bonding issue

AntonHellbe — Thu, 12 Sep 2019 09:23:22 GMT

This was a caching issue. Resolved it after resolving and error in the SDK (Notifications was dropped when there was an ongoing MTU exchange).

see here: devzone.nordicsemi.com/.../service-changed-characteristic-not-enabled-on-ios

RE: iOS and pairing/bonding issue

Mttrinh — Wed, 21 Aug 2019 13:49:21 GMT

iOS does not expose neither of Generic Access and Generic Attribute services.

nRF Connect for iOS just prints them, as they are mandatory for all devices, but there are no characteristics in any of them, as we don’t know what’s inside.To verify if the device has SC characteristic you have to use either nRF Connect for Android or PC.

RE: iOS and pairing/bonding issue

AntonHellbe — Mon, 19 Aug 2019 14:46:37 GMT

Updated it, (UI wise the new one is much more confusing...)

Now I can see the Generic Attribute, but not the Service Changed characteristic which should be located with the Generic Attribute Service.

RE: iOS and pairing/bonding issue

Mttrinh — Mon, 19 Aug 2019 14:39:18 GMT

The latest version is 2.0.

RE: iOS and pairing/bonding issue

AntonHellbe — Mon, 19 Aug 2019 14:37:12 GMT

nRF connect on iOS does not display the two services (Generic Attribute and Generic Access) that the Softdevice adds to the attribute table. When my colleague does a service discovery using the iOS bluetooth API they dont show up either.

From what it looks like in App store I'm using the latest nRF connect.

RE: iOS and pairing/bonding issue

Mttrinh — Mon, 19 Aug 2019 14:33:51 GMT

Hi,

Does this happen in your own app or nRF Connect on iOS? Did you try the new version of nRF Connect on iOS?

RE: iOS and pairing/bonding issue

AntonHellbe — Mon, 19 Aug 2019 14:21:46 GMT

Hi again,

It seems like the Service Changed Characteristic is not shown on iOS. I can clearly see it on my Android phone when using nRF connect. However on my iPhone 6s, running iOS12.4 its not visible, and my colleague cannot see it aswell when he discovers the services programmatically. How do you handle Generic Attribute (0x1801) on iOS?

Connecting on iOS gives error 8 (NRF_ERROR_INVALID_STATE), since notifications are disabled, however it's not possible to activate notifications since Generic Attribute is not visible.

RE: iOS and pairing/bonding issue

AntonHellbe — Fri, 16 Aug 2019 14:17:00 GMT

Hi,

I suspect that it might have something to do with caching as we are sometimes changing the GATT attribute table. I have enabled Service Changed Characteristic and now I notify each time a bonded device connects that the attribute table has changed.

I have sent it to my colleague who will test it out. Hopefully it will help :).

Br,
Anton

RE: iOS and pairing/bonding issue

Mttrinh — Fri, 16 Aug 2019 13:04:48 GMT

Hi,

We haven't seen this issue before. Could you try turning the bluetooth on your phone off/on? To see if it might be an chaching issue.

Have you tried testing with other firmwares on the same DK? Does it happen on the latest stable release iOS12.4?

Could also try it with nRF Connect and other iPhones as well?