I still had the issue in iOS 18 beta 8. In case someone is using several navigationDestinations on a view. In my case it helped to change the order of these. Not sure why but it worked.

I am facing the same issue. Did you find a solution so far? @yqiang

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

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

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

The issue got resolved in iOS 17 beta 6

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

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

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

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.

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

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.

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

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

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