Post

Replies

Boosts

Views

Activity

Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Similar issue here when starting an ARSession. iOS 26.3.1 on an iPhone 16 Pro. No issues running the same app on an iPhone 12 on iOS 18.6.2 `(Fig) signalled err=-12710 at <>:601 <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:308 <<<< FigCaptureSourceRemote >>>> Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:569) - (err=-17281)`
1d
Reply to Nearby Interaction property supportsDirectionMeasurement returns false and NINearbyObject direction property is nil
Having the same problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. Worth noting that I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far, at least the case of the 16 Pro / U2 / iOS 26 (?): 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Placing both a 16 Pro and a 12 face down on a table with rear cameras covered: 12 continues to show position with a dirSrc of '3D'; 16 Pro tells me to "Move to a brighter area" with a dirSrc of 'none' iPhone 12 seems to start an NI session with hAngle as its dirSrc before resolving to 3D. If anyone has experienced anything differently with NISessions, would love to hear it.
Topic: App & System Services SubTopic: General Tags:
1d
Reply to Direction data not available with U2 chip (iPhone 15 Pro and iPhone 16 Pro) when using Murata SR040/SR150 accessory
Having a similar problem, although I'm not sure if it's related to iOS26 or phones with the U2 chip. I am doing peer to peer rather then peer to object, but figured I'd share my findings. iPhone 16 Pro (U2 chip), iOS 26.3.1: NISession created — capabilities: token: true supportsDirection: false supportsCameraAssistance: true supportsExtendedDistanceMeasurement: true supportsPreciseDistanceMeasurement: true iPhone 12 (U1 chip), iOS 18.6.2: NISession created — capabilities: token: true supportsDirection: true supportsCameraAssistance: true supportsExtendedDistanceMeasurement: false supportsPreciseDistanceMeasurement: true What I've found so far: 16 Pro / U2 / iOS 26 (?) 3D direction vector is never available Camera seems to be required for directional convergence Everything seems to be determined by hAngle Seems to start an NI session with dirSrc as 'none' and then resolves to 'hAngle' after camera convergence is complete 12 / U1 / iOS 18 Seems to start an NI session with 'hAngle' as its dirSrc before resolving to '3D'. FYI, placing both a 16 Pro and a 12 face down on a table with rear cameras covered after both devices have established position and relative distance: 12 continues to show position with a dirSrc of '3D'; 16 Pro tells me to "Move to a brighter area" with a dirSrc of 'none' If anyone has experienced anything differently with NISessions, would love to hear it.
1d