Hi! I stumbled across this topic when I tried to keep the UWB session running after Bluetooth disconnection. @carlos.silva, are you sure that the iOS Nearby Interaction framework allows the NI session to run after the associated Bluetooth peer disconnects?
I modified the default behavior of my iOS app to stop calling the invalidate() function on my NI session. However, it seems the NI framework invalidates the session with the NI didInvalidate callback and the following error:
NIError.Code.accessoryPeerDeviceUnavailable | Apple Developer Documentation (NI error)
I want to highlight here that I am using the new iOS 16+ API for passing NI Accessory configuration, which also requires Bluetooth peer identifier as a second parameter:
init(accessoryData:bluetoothPeerIdentifier:) | Apple Developer Documentation (NI Accessory Configuration constructor with Bluetooth peer identifier)
Is there any way to work around this automatic invalidation on the iOS side?