@glow it sounds like a bad bug. The sample code from 14.0 is breaking in 15.4. Apple DTS told us there is no workaround. That's… not a good sign.
It's possible the next version of Xcode builds and compiles to retcon a fix on 15.4.x. It's either an official fix from a new SDK, an unofficial fix in the form of discovering some kind of hacky private API to fix 15.4.x, or engineers just have to permanently gate their users from ARGeoTrackingConfiguration on 15.4.x.
vanvoorden
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
@glow you were able to build from Xcode 13.3.1 to 15.5b2 and the issue is fixed?
Do we know when the issue first started happening? Is this a 15.4.x bug?
Does anyone have the diff to get that Apple sample code project working correctly on 15.4.x?
Is there any workaround in code other than just gating users on 15.4.x from ever using ARGeoTrackingConfiguration?
https://developer.apple.com/documentation/arkit/content_anchors/tracking_geographic_locations_in_ar
I'm seeing the same error from trying to build and run the Apple sample project. Building from Xcode 13.3.1 (13E500a) to iPhone 12 Pro Max running iOS 15.4.1 (19E258).