Post

Replies

Boosts

Views

Activity

Reply to Going back to ARKit view in Navigation Stack causes application crash with iPhone 14 Pro
We are also seeing several new ARKit related crashes with similar stack traces, some exclusively on iPhone 14, others on iOS 16 only. I have also filed a few bug reports: "ARSession on run after pause from viewWillDisappear causes crash in AppleCV3D" - 11343731 "TrueDepth stream fails on iPhone 14 Pro after using an ARSession" - 11554045 "Modifying an ARSession that uses 'initialWorldMap' causes a unnecessary relocalization" - 11604874 For your situation, there might be a workaround. I'm guessing you are calling session.run() on viewWillAppear and session.pause() on viewWillDisappear, but keeping the same ARSession around. You can try creating a new ARSession on viewWillAppear rather than reusing the same one ( e.g. self.session = ARSession() )
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’22
Reply to WKWebView clear search highlight
try searching for a random string
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
Boosts
Views
Activity
Dec ’24
Reply to USDZ + ShaderGraphMaterial not working?
Thanks, I will test out using the PBR material as a backup on non visionOS platforms. Can you share if there are any plans to support ShaderGraphMaterial on iOS or Mac? My use case is authoring usdz content on the Vision Pro, and sharing with others on iOS / Mac platforms.
Replies
Boosts
Views
Activity
Mar ’24
Reply to Going back to ARKit view in Navigation Stack causes application crash with iPhone 14 Pro
We are also seeing several new ARKit related crashes with similar stack traces, some exclusively on iPhone 14, others on iOS 16 only. I have also filed a few bug reports: "ARSession on run after pause from viewWillDisappear causes crash in AppleCV3D" - 11343731 "TrueDepth stream fails on iPhone 14 Pro after using an ARSession" - 11554045 "Modifying an ARSession that uses 'initialWorldMap' causes a unnecessary relocalization" - 11604874 For your situation, there might be a workaround. I'm guessing you are calling session.run() on viewWillAppear and session.pause() on viewWillDisappear, but keeping the same ARSession around. You can try creating a new ARSession on viewWillAppear rather than reusing the same one ( e.g. self.session = ARSession() )
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’22