In my case the architectures were custom which lead to that error. When I used $(ARCHS_STANDARD) in BuildSettings -> Architectures the error went away.Thanks for pointing me to that direction

Same here... also lybron's answer did not help in my case

I think the problem is with the device. Can't run the app on my daily driver but runs fine on a second device.

This crash happed to my app in production only built with Xcode 13.2.1 -.-

Call tag.connect before tag.readNDEF. I had the same problem and I fixed it with that...

I could get it to work on a real device by running the extension. Then Xcode says: Waiting to attach. Then bring up the add new widget UI on your device and search for your widget there. Stop when you see your previews and select in Xcode -> Debug -> Attach to process -> Your Process should be in Likely Targets. Click that and you should be able to debug.

Yes they are saved in the Images folder created by CaptureFolderManager in the sample app. From there you can built a export functionality.

The issue persists in Xcode Version 15.0 beta 6 (15A5219j) and iOS 17 beta 5. The whole Object Capture experience got worse. Everything feels very laggy.

You can use this to compile the code only for real devices. You need to put the if statement around the whole ObjectCapture code. #if arch(arm64) || arch(x86_64) // Code that should not be compiled for simulator devices #endif

I would be. You can send me a message via nfc.cool

@lastsong @yutay @Nate1244 did you find a solution?

The issue got resolved in iOS 17 beta 6

I can not even upload a screenshot of my stacktrace here. Image upload seems to be broken here.

I am facing the same issue. My journey of debugging is here: https://twitter.com/n1c0_muc/status/1712425064203751677

Relax, it takes a while. I guess at the moment of my comment it should be available worldwide. ;)