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?

[Sourabh]

Yes, have been turning bluetooth off/on very often but most of the times when we are stuck in "Requesting Composition Data" loop.

Yes, we also tried different devices. We are testing on 1 iPad and 2 different iPhones.

[Aleksander Nowakowski]

Using nRF Connect for iOS, what services do you see on the device instead of mesh proxy service? 

[Sourabh]

My apologies for the late reply. We got stuck in something else and had to shift gears for the same. Now, I'm back on the task and can give inputs quickly.

Interestingly, we see Mesh Proxy Service for the device using nRF Connect iOS app quite often. We are upgrading our firmware again to the latest available version. i'll let you know the updates.

[Sourabh]

Update - with the example of nRF-Mesh-iOS (latest master) app, and using Mesh SDK v4.2, the issue of stucking of requesting composition data is not there anymore.

Thank you Mttrinh and Aleksander Nowakowski for your help and support. It really helped and guided me to the resolution.

Cheers!