Both was working in my tests, but i just performed 7-8 Scans since Beta 6 and in Beta 5 I found out, killing all Apps in AppSwitcher and restarting the devices should allow some scans (This really seams to be a memory issue). Hearing that in Beta 6 it still crashes sometimes is really bad..

Actually for me the scan is working again since iOS 17 Beta 5 and Xcode 6. Just got 2 times bad access in memory but now i got 5 successful scans in a row (after cleaning the build folder) EDIT: Although it worked 5 times in a row now it crashes again in the reconstruction process :(

Thanks guys! I got it to work with #if targetEnvironment(simulator) #endif

@mayur_tanna Why should we need the @Observable macro? I have the AppDataModel as ObservableObject and everything works for my on the scanning side. I just now get more and more crashes when it comes to reconstruction.

I have the same issue, but - at least in my case - it has nothing to do with the amount of pictures. It did also crash one time with just 10 images. Does someone know something about this issue?

Yes, actually its not that hard to fix. The object capture session is not an observed object anymore, but the AppDataModel (which the ObjectCaptureSession is in) is an environment object. Just remove the @ObservableObject ObjectCaptureSession anywhere and use the @Environment AppDataModel and access it from there. You also have to rewrite the feedback and state sink in the AppDataModel because they are also not published anymore. Use the "ObjectCaptureSession.feedbackUpdates / ObjectCaptureSession.stateUpdates" for that. Hope i could help, this took me a day to figure out yesterday.

Hello Dirk, thanks for your answer! The problem is, that is dont only need the billModel in the PDFManger but also everywhere else in the App because it contains the list with all entries from the DB. The PDFManager Class is no DataModel but a helper class that collects informations and provides functions for creating a pdf out of the collected informations.

I am also very interested in this! Is there a solution yet?