This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

I am having issues connecting with iOS13 with my production app based on react native and also issues with nRFconnect not connecting

My production app(sill in development technically but pre-production stable) is having issues with our SDK14.2 BLE UART application. When the generic version from examples is loaded it works.....any reasons why this would happen??? Please note the app is built within react native and has no issues other than what I have described.

Parents
  • It appears as though the "fix" was to add a handler which wasn't in the SDK for the PHY?? Does any of this make some sense? I am actually not directly involved with the project these days but I originally designed this. I can get more specifics as I am curious myself now why iOS would care???

  • Thanks for updating the ticket. The iPhone was probably requesting an update to the 2Mbit PHY but ignored by the nRF. There are certain events such as PHY update requests that the application must respond to in order to let the Softdevice respond back (Softdevice does not know what PHY the app prefers). No response is sent if the app ignores the Softdevice event, which will lead to procedure timeout->linkloss. 

    There is a message sequence chart in the Softdevice API documentation that illustrates this exchange: Peripheral PHY Update 

Reply
  • Thanks for updating the ticket. The iPhone was probably requesting an update to the 2Mbit PHY but ignored by the nRF. There are certain events such as PHY update requests that the application must respond to in order to let the Softdevice respond back (Softdevice does not know what PHY the app prefers). No response is sent if the app ignores the Softdevice event, which will lead to procedure timeout->linkloss. 

    There is a message sequence chart in the Softdevice API documentation that illustrates this exchange: Peripheral PHY Update 

Children
No Data
Related