NRF52832 device not visible on iphone XR

Hi all, I have an odd issue with an iphone XR. The NRF Connect for Mobile application can see adverts from the device when scanning, but the device does not appear in the bluetooth menu on the phone, nor is it discovered by my flutter application. On an iphone 7, or an iphone 12 pro, the device is detected correctly.

Has any one else noticed issues specific to the iphone XR? If so, I can go into details of OS version etc (the iphone XR was upgraded to the latest OS release, but that did not improve things.

Regards,

Mike

  • Hi,

    I will look into it and get back to you.

    Regards,

    Swathy

  • Hi Mike,

    Sorry for the delayed response. 

    The NRF Connect for Mobile application can see adverts from the device when scanning

    Does this mean that the device is detected in the nRF Connect for iOS.? Kindly confirm whether you could find the device in nRF Connect for iOS.

    Regards,

    Swathy

  • Correct. It can see it, and can connect to it. Yet the device does not appear in the iOS Bluetooth display, and cannot been seen by my custom application (which has been written in Flutter.) Operation on Android, or iPhone 7, or iPhone 12 is correct. It's very specific to the iphone XR, oddly. 

  • Hi Mike,

    I asked around a bit about this issue. Usually when devices doesn't appear on the Bluetooth menu, it is either because the device is bonded with another device, or because it doesn't contain a service that the phone finds "useful" such as headphones and keyboards. So if the device is not advertising with a familiar UUID, then the phone will hide it from the bluetooth settings display.

    Not sure about the custom application, but this might either be a problem with iPhone XR or because the device is bonded with another iPhone. Since the device appears on other iPhones, then perhaps the device is bonded. Could you try to delete the bonding data using the nrfjprog --eraseall and refresh the application.

    Regards,

    Swathy

  • Hi Swathy,

    thanks, both of those comments are very useful and I would suggest valuable to other developers with similar issues.

    It's odd that an earlier version iPhone is ok, and a later version iPhone is ok, but (IMHO)  is not unusual that Apple make slightly odd Bluetooth handling decisions. 

    Thank you - I don't think I can ask for more at this point. For now it's back to me to do more debugging, and, sadly, obtain an Apple device to test.

Related