var peerIdentifier = peripheral!.identifier     do {       configuration = try NINearbyAccessoryConfiguration(accessoryData: accessoryData, bluetoothPeerIdentifier: peerIdentifier)     }catch{       return     }     cacheToken(configuration!.accessoryDiscoveryToken, accessoryName: devicename)     nisession?.run(configuration!) I configured the source as above, how do I receive Apple Shareable Configuration Data sessionFailed : Error Domain=com.apple.NearbyInteraction Code=-5887 "NIERROR_SESSION_FAILED_DESCRIPTION" UserInfo={NSLocalizedRecoverySuggestion=NIERROR_SESSION_FAILED_RECOVERY_SUGGESTION, NSLocalizedDescription=NIERROR_SESSION_FAILED_DESCRIPTION, NSLocalizedFailureReason=This session object is invalidated. Dispose of it and create a new one instead.}

Hey Folks, I am a bit stuck on creating UWB session between two iPhones in background mode of the application. The UWB works fine on foreground mode of the application but it doesn't work in background. I get error of invalid configuration and while searching on stackoverflow I get the answer that the discovery tokens are invalid. Can anyone please guide me if someone has done it in background mode. Getting this error: Error: Error Domain=com.apple.NearbyInteraction Code=-5888 “NIERROR_INVALID_CONFIGURATION_DESCRIPTION” UserInfo={NSLocalizedRecoverySuggestion=NIERROR_INVALID_CONFIGURATION_RECOVERY_SUGGESTION, NSLocalizedDescription=NIERROR_INVALID_CONFIGURATION_DESCRIPTION, NSLocalizedFailureReason=NIERROR_INVALID_CONFIGURATION_FAILURE_REASON}

Anyone here who implemented apple nearby interactions I'm continously getting this error and unable to resolve this. I'm getting accessoryData from BLE device chractristics and bluetooth identifier of connected BLE device. let config = try NINearbyAccessoryConfiguration(accessoryData: accessoryData,                                                             bluetoothPeerIdentifier: peerIdentifier) Error: Error Domain=com.apple.NearbyInteraction Code=-5888 "NIERROR_INVALID_CONFIGURATION_DESCRIPTION" UserInfo={NSLocalizedRecoverySuggestion=NIERROR_INVALID_CONFIGURATION_RECOVERY_SUGGESTION, NSLocalizedDescription=NIERROR_INVALID_CONFIGURATION_DESCRIPTION, NSLocalizedFailureReason=NIERROR_INVALID_CONFIGURATION_FAILURE_REASON}

In my app, I have configured BackGround Session like the following code. var peerIdentifier = peripheral!.identifier do { configuration = try NINearbyAccessoryConfiguration(accessoryData: accessoryData, bluetoothPeerIdentifier: peerIdentifier) (configuration!.accessoryDiscoveryToken.description) : (devicename) : (peerIdentifier)") }catch{ return } cacheToken(configuration!.accessoryDiscoveryToken, accessoryName: devicename) nisession?.run(configuration!) However, the Delegate setting does not receive a response whether it is an error func session(_ session: NISession, didUpdate nearObjects: [NINearbyObject]) Is there a way to receive NINearbyObject in the background? If not, is there a way to get a sample code on how to measure the background distance? When using 'nisession.delegate = self ' in background UserInfo={NSLocalizedRecoverySuggestion=NIERROR_SESSION_FAILED_RECOVERY_SUGGESTION, NSLocalizedDescription=NIERROR_SESSION_FAILED_DESCRIPTION, NSLocalizedFailureReason=This session object is invalidated. Dispose of it and create a new one instead.}

Hi all, Recently I updated my app, which is using NearbyInteraction framework and was working great in iOS 15.x, to use new NearbyInteraction APIs introduced in iOS16. The main reason I want to test new APIs is to enable background sessions as explained in WWDC2022-10008. Actually background session is working ok with my third-party accessory, I can bring the app to the background and then back to the foreground and the Nearby Session does not get invalidated. However, I noticed that now using latest API the direction I receive is always null. I am using this API to create the session: "init(accessoryData:bluetoothPeerIdentifier:)" The ranging starts, but distance is nil in didUpdate delegate callback: "func session(_ session: NISession, didUpdate nearbyObjects: [NINearbyObject])" This same code was working before, I would get the direction out of myObject.direction. I tested setting isCameraAssistanceEnabled to true, even tried adding ARSession as in WWDC just in case, but direction and estimated horizontal and vertical angles are always nil. Is there anything I am missing? Any hint how to get this fixed? Regards.

Hello, We are a company working on Ultra Wideband solutions and, hence, using Apple's NearbyInteraction framework to establish UWB Ranging sessions with our UWB-enabled third-party accessory. This week we were excited about the new background UWB Ranging session possibility, which opens new use cases. The wwdc2022 10008 video that provides the technical details for this feature indicates that the third-party accessory is responsible to expose the Nearby Interaction GATT Server. We don't manage to get full details about what needs to be implemented to by compliant with Apple's framework. The URL below indicates that full BLE details should be explained in the "Nearby Interaction Accessory Protocol Specification" but we don't see any info there. https://developer.apple.com/documentation/nearbyinteraction/ninearbyaccessoryconfiguration https://developer.apple.com/nearby-interaction/specification/ Can someone indicate us where the find full details for this background Nearby Interaction feature? Thanks in advance. Regards.