May I ask where I can find this document: the UWB Interoperability Specification, Developer Preview, Release 1? This document is a comment I saw in Qorvo's project. I need to understand the specific meaning of the data sent to the iPhone by embedded devices in the Nearby Interaction Access Protocol. I am developing an application based on Qorvo's dwm3000, so I need to understand this aspect. Thank you for any response!

How to create and handle multiple sessions using Nearby Interaction? It was briefly mentioned in the WWDC20 video titled "Meet Nearby Interaction" but I cannot find the implementation anywhere online. Can someone share sample code or point me towards the location where I can find the solution to this problem? Thanks.

Hi all I am going to develop a software for third party-UWB chipset communication with U1. From the document, third party chipset have to send the UWBConfigData to U1, but I have no idea how to fill in Manufacturer ID and UWB chipset model ID . anyone can help? Terence

when i check NIpeekaboo before update iOS to latest, it worked well. but if i push app after update iPhone12 to iOS 14.2.1 and Xcode to 12.2, it stops on "discovering peer". air-drop is working but NIpeekaboo is not working. how can i test NIpeekaboo?

Hello everyone, I have encountered an error when trying to enable BLE background mode of the third-party NI example application. I have done that by replacing the configuration = try NINearbyAccessoryConfiguration(data: configData) with configuration = try NINearbyAccessoryConfiguration(accessoryData: configData, bluetoothPeerIdentifier: peerIdentifier) I have additionally expanded the List.plist with Required background modes: App communicates using CoreBluetooth Or rather, central-bluetooth When starting the session, iPhone 12+ Pro Max (iOS 16+) device immediately calls invalidateSession with the error invalidSession. configData is identical for both cases, and implementation on peripheral device has not been changed. Important thing to note here is that for the non-background mode, third-party accessory and iPhone device are able to range just fine. Do you have any recommendations or advice how we can try to solve this, or what might be an issue? Thank you in advance, Aleksa and OBLO Living development team.

Hi All I can run the nearby interaction even the apps is in background, while there is a distance information in the accessory side, the apps invoke delegate function "didRemove nearbyObject" with timeout periodically. is there any way to disable the timeout when it is running in background? Or anything I did wrong so that the session keep timeout while there is distance measurement in accessory side, please anyone help. Thanks in advance

The requirement to have an active Bluetooth connection for UWB readings confuses me. Bluetooth is so slow in connecting. Mostly. when I walk passed my accessory, I have already passed my UWB accessory range effect (switch on an led) without getting a UWB reading. I have no problem to pair the accessory to my phone. But please give us UWB background readings without connecting via Bluetooth. Thank you, Robin

Hi all! I was hoping that in WWDC23 sessions, there would be an announcement on a new API for ultra wide-band and AirTags, in order to have access on developing apps with interaction between iPhones and AirTags using the UWB technology. But, I cannot see anything related to this topic. Do you think there will be any good news this year ?

Hello everyone! We are a small team developing third-party accessories using NXP and Qorvo chips. Two of our teammates have bought the new iPhone 14 and it seems that we have no azimuth no more regarding UWB sessions. We have tested on the Qorvo NearbyInteraction app from the App Store. By debugging on our own application, it seems we never have a valid direction vector. Is anyone experiencing the same issue ? Did Apple made an iPhone 14 less efficient than the iPhone 13 on UWB ? Regards, Alexandre

I am working on the background mode of nearby interaction, from the WWDC 2022 video, my Apps have to do pairing, connect with third party device's BLE Afterward, I have to implement a method called triggerPairing ( peripheral: peripheral, encryptedCharacteristics: CBCharacteristics), to trigger pairing process. The document mention that Apps should NOT discover the nearby interaction GATT service, but the encrypted characteristic is belonged to this service. how can I pass the parameters into the triggerPairing function if the Apps does not discover the service? what parameter should I pass into the function? Does anyone help?