Always happens here :-/

Interesting. My previous test did all the things you mentioned, but the captureHighResolutionFrame call that failed was made immediately after calling session.run. It works when moved to a tap handler. Thanks

I'm seeing the same behavior and haven't found a solution

Re: @sducouedic's question, configuration changes aren't immediate. Add this delegate method to see that the sceneDepth semantic is enabled. public func captureSession(_ session: RoomCaptureSession, didAdd room: CapturedRoom) { if (session.arSession.configuration?.frameSemantics.contains(.sceneDepth)) != nil { print("Scene depth is supported") } }

Cole from Scandy wrote a nice blog article about this a number of years ago. I don't think his mesh was textured though, so the method described may not yield the results you're looking for. https://www.scandy.co/blog/how-to-export-simple-3d-objects-as-usdz-on-ios

Same here when running against physical devices. I filed feedback. We can't be the only ones experiencing this. macOS 15.4 (24E248) Xcode 16.3 iOS 18.4, iPadOS 18.4

Ok. One user with the issue took their device to an Apple Store where no hardware issues were found. The user followed their recommendation to do a complete restore, after which the user reports that scanning began working again.