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?

I'm very excited about the new AirTag product and am wondering if there will be any new APIs introduced in iOS 14.5+ to allow developers to build apps around them outside the context of the Find My network? The contexts in which I am most excited about using AirTags are: Gaming Health / Fitness-focused apps Accessibility features Musical and other creative interactions within apps I haven't been able to find any mention of APIs. Thanks in advance for any information that is shared here. Alexander

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

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

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.

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?

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 ?

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 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

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.

My phone all the time always randomly overheats, when i am hiking or taking a walk. i have already reset it multiple times or switch it to air plane mode, but it doesn’t do anything. so i am asking out for help. here is a link to a log file of some regular daily use: https://www.dropbox.com/scl/fi/a8urc24gjfnjqx4drygxe/stalking.txt?rlkey=g1kvxfs3kkxq5qq913xgnflfy&dl=0

Hello, Our team is working on a mobile app that uses Nearby Interaction framework (UWB technology) to get real-time high-accuracy ranging information with our third-party UWB-enabled device. So far everything works fine, background sessions included as explained in wwdc2022/10008 video. We are using Bluetooth LE to exchange the UWB parameters as recommended by Apple. Our next goal is to go for a full hands-free configuration of the UWB session. Let's think of an access control use case where UWB is used to measure the distance between the user and the door (credentials exchanged via Bluetooth). What we want to achieve is to start the UWB session without requiring the user to take the phone out of his wallet and open the access control app. What it works for us today is if the user starts the app, then switches off the screen and puts the phone into his pocket. The app is still running in background, so the Bluetooth Scan keeps working, the Bluetooth session starts, the UWB parameters exchanged and the UWB session started in the background, all good. But what if the user killed the app or never started it after reboot? How can we force the app to start from killed state when the BLE / UWB third-party accessory comes into proximity? iBeacon seems like a promising approach, but according to the forums, in iOS 16 the app will not be restarted from killed state. Is this correct? Any idea / suggestion about how to let the OS start our app when the user approaches the BLE / UWB accessory and the app is in killed state? Thanks in advance for your time. Regards.

Is it possible to start a background nearby interaction session without pairing? It would be nice to have a bunch of background sessions for a bunch of devices and not need them to all be confirmed by the user like in the foreground.

Ranging is working great when I'm removing the BluetoothPeerIdentifier parameter but if I want to do some background ranging, I need to be able to use the removed parameter. Somehow when I'm both AccessoryData and BluetoothPeerIdentifier parameters, I got the NIErrorCodeInvalidConfiguration error code and i can't range anymore. Do you guys have a fix for that? The parameter BluetoothPeerIdentifier is not NULL so it should work properly... Thank you, Marc

Hello all! We are a small team of smart home. We are preparing to develop third-party UWB applications in Apple Watch, but we have not found any instructional materials related to watch UWB. So i would like to ask if there is any way to get such documents, or guys who have done this kind of development.

Scenario: We have a museum where each exhibit has a UWB BLE accessory. A user moves around the museum with their phone application in the background. Once a user enters an exhibit area (Determined by UWB distances) a background task is initiated (audio/notification/widget). The Question: In our current understanding of the protocol, the user must pair to each exhibit anchor beforehand, significantly impairing the user experience and bloating their Bluetooth-paired device list. Is it possible now or potentially in the future to not require pairing for pre-approved devices? Alternatively, pairing to a hub that acts as an intermediary between the phone and accessories also seems like an appropriate compromise.

Inquiry about Apple's "NearbyInteraction" and Related Patent US10486646B2 Hello, I have questions about Apple's publicly disclosed accessory 'NearbyInteraction' and the associated Apple patent US10486646B2. I understand that pairing is required when using "NearbyInteraction" in the background. However, employing pairing with NearbyInteraction might potentially infringe upon the patent US10486646B2. Could you please clarify whether Apple has implemented any of the following measures, or if there is another strategy or policy in place? No patent licensing agreements exist, and sales of products using UWB in the background by third parties are not permitted. When using NearbyInteraction, patent infringement isn't a concern, and systems using NearbyInteraction aren't considered to infringe upon the patent US10486646B2. It's necessary to apply for a patent licensing agreement. I apologize for any inconvenience, and I would be grateful for a response. Also, if there's a need for any application or process, could you please guide me on how to proceed? Thank you for your attention to this matter.

Hi everyone, I am trying on iOS 17.1.1 the Nearby Interaction framework and SceneKit. I am testing it on iPhone 15 Pro Max and iPhone 12 Pro Max. if NISession.deviceCapabilities.supportsDirectionMeasurement { print("Interact using device distance and direction.") } else if NISession.deviceCapabilities.supportsPreciseDistanceMeasurement { print("Interact using distance only.") } iPhone 12 Pro Max is working normally, but supportsDirectionMeasurement property in iPhone 15 Pro Max returns false and i cant use the SceneKit. Is anyone experiencing the same issue? Regards, Shin

Hi, sorry if the sentence is wrong as I am using the translate function. I am looking to create an AR application using Nearby Interaction and ARkit. The devices to be used are iPhone 15pro and apple watch 9. The iPhone implementation will measure the distance to the apple watch while simultaneously using AR to track images. The apple watch implementation will only measure the distance to the iPhone. Is it possible to implement this feature? If you know of any, I would like to know.