Randomly failing to discover services and leading to "Device not supported"

[Sourabh]

Hi team,

Describe the bug Running the sample app on Nordic Development Kit "nRF52840-DK" (and also on our firmware board) is randomly failing to discover services leading to connection disconnect with the error message of "Device not supported" I am basically having two but RANDOM issues: Not able to provision as described above. If provisioning is successful, the app is stuck in "Requesting Composition Data" and getting "The bearer is closed". To Reproduce Just cloned IOS-nrf-Mesh-Library from the repo, made the Example compile and run on iPad. Tapping the + button to Provision Device. From the scanned list (2 boards for me), tapping one any board. WorthNoting After going to iPads Bluetooth Settings', turning the bluetooth Off and On makes both the above cases/issues work. But the same problem comes back after resetting / removing the node. Not sure if it anyone else have faced this problem but surely happening a lot for me. Expected behavior The sample app should be able to Provision and load Composition Data successfully every time for the Nordic Dev Kit board at least. Platform details: Device: iPad 3 OS: iOS 13.3 App Version: 2.2.3 Logs / Screenshots Nordic board 2020-09-09 12:45:10.801432+0530 nRF Mesh[408:92785] [Bearer] Central Manager state changed to .poweredOn 2020-09-09 12:45:11.206446+0530 nRF Mesh[408:92785] [Bearer] Connecting to Dev Board... 2020-09-09 12:45:11.818963+0530 nRF Mesh[408:92785] [Bearer] Connected to Dev Board 2020-09-09 12:45:11.819245+0530 nRF Mesh[408:92785] [Bearer] Discovering services... 2020-09-09 12:45:11.962127+0530 nRF Mesh[408:92785] [Bearer] Device not supported 2020-09-09 12:45:11.962701+0530 nRF Mesh[408:92785] [Bearer] Cancelling connection... 2020-09-09 12:45:11.965448+0530 nRF Mesh[408:92785] [Bearer] Disconnected from Dev Board with error: Device not supported 2020-09-09 12:45:12.411416+0530 nRF Mesh[408:92946] [CoreBluetooth] XPC connection invalid My board 2020-09-09 12:45:22.206242+0530 nRF Mesh[408:92785] [Bearer] Central Manager state changed to .poweredOn 2020-09-09 12:45:22.611192+0530 nRF Mesh[408:92785] [Bearer] Connecting to Ios dev... 2020-09-09 12:45:23.406476+0530 nRF Mesh[408:92785] [Bearer] Connected to Ios dev 2020-09-09 12:45:23.406650+0530 nRF Mesh[408:92785] [Bearer] Discovering services... 2020-09-09 12:45:23.611281+0530 nRF Mesh[408:92785] [Bearer] Device not supported 2020-09-09 12:45:23.611836+0530 nRF Mesh[408:92785] [Bearer] Cancelling connection... 2020-09-09 12:45:23.614616+0530 nRF Mesh[408:92785] [Bearer] Disconnected from Ios dev with error: Device not supported 2020-09-09 12:45:24.059975+0530 nRF Mesh[408:92946] [CoreBluetooth] XPC connection invalid Please suggest what might be going wrong and how to fix this?

[Mttrinh]

Hi,

Which example are you using from the Mesh SDK?

Which Mesh SDK version are you using

[Mttrinh]

I mean which firmware example are you running on your DK?

Sourabh said:

Mesh SDK Version - Latest commit in master.

 Do you referr to this repo? Mesh SDK v4.2?

[Sourabh]

Update: Mesh SDK v4.2 is giving the same problems. Stuck at Requesting Composition Data..

[Sourabh]

We have downloaded the code v4.2.0 from here nrf_SDK_for_Mesh_v4.2.0_src and flashed it on DK. And using the given iOS Mesh Example. 

[Mttrinh]

Hi, 

The "Device not supported" error may also be thrown when the device disconnects before services were discovered. But then retrying should help, I think.

I tried with the latest Mesh SDK and managed to reproduce the issue you are seeing. Stuck at Requesting Composition Data. 

A workaround for the "Stuck at Requesting Composition Data":

After you have provisioned the device -> connect to the device by going into the proxy tab and connect from there -> Then configure the device. The "Requesting Composition Data" should go through now.

[Sourabh]

Thank you. I'll try this and update you.

[Sourabh]

Mttrinh said:

The "Device not supported" error may also be thrown when the device disconnects before services were discovered. But then retrying should help, I think.

Having look at the logs tells us that device gets disconnect after "Device not supported" error. Refer below:

Nordic board

2020-09-09 12:45:10.801432+0530 nRF Mesh[408:92785] [Bearer] Central Manager state changed to .poweredOn
2020-09-09 12:45:11.206446+0530 nRF Mesh[408:92785] [Bearer] Connecting to Dev Board...
2020-09-09 12:45:11.818963+0530 nRF Mesh[408:92785] [Bearer] Connected to Dev Board
2020-09-09 12:45:11.819245+0530 nRF Mesh[408:92785] [Bearer] Discovering services...
2020-09-09 12:45:11.962127+0530 nRF Mesh[408:92785] [Bearer] Device not supported
2020-09-09 12:45:11.962701+0530 nRF Mesh[408:92785] [Bearer] Cancelling connection...
2020-09-09 12:45:11.965448+0530 nRF Mesh[408:92785] [Bearer] Disconnected from Dev Board with error: Device not supported
2020-09-09 12:45:12.411416+0530 nRF Mesh[408:92946] [CoreBluetooth] XPC connection invalid