I am getting this since Sequoia whenever I start certain Docker containers. This is pretty annoying. Is there a way to work around this?

Update: I now assume that the reason why I only saw this on app start before is that we drop some initial content here, as a tutorial. I believe that the root cause is that dropping world anchors leads to a crash. This is also consistent with the error message. We place our anchors directly in front of the user, in "thin air". Everything worked fine until iOS 17, but now the app is completely broken with iOS 18.

Hey, Thanks for the feedback. However, this does not seem to be a Unity issue. The app worked just fine for years like that. It's also not unusual to delay AR initialisation. Besides, I just noticed today that the problem is much worse. The app crashes as soon as it spawns new AR content. I guess it's related to dropping a world anchor. To me, it looks like a degression in iOS 18. Our app is completely unusable this way. If you want to, you can try it yourself. It's called "Marbleverse".

I already did this.

I noticed that the release notes of visionOS 2.0 mention QR codes briefly: https://developer.apple.com/documentation/visionos-release-notes/visionos-2-release-notes QR Codes of version 25 and 40 can be difficult to detect. (125919605) Does that mean that QR codes are supported now, or does this mean that there is an issue detecting QR codes as image tracking images?

I actually need the QR codes to trigger the download of images used for image tracking. So this won't help me here. I cannot bake images into the app in my use-case.

I am facing a similar problem, but want to exclude RealityKitContent that is part of a larger Swift package: https://developer.apple.com/forums/thread/756003 What is the best approach here?

Well. I get the feeling that this is the standard answer here :-) Anyway, thanks for taking your time to respond. I just filed it as FB13799026 and also FB13799035 (for general access to the camera).

How is your answer related to the Apple Vision Pro? This device is not even giving you access to the cameras.

Thanks!

This approach worked in my case, although I hadn't used a State variable in the child. The original object came from an Observable, though, which was handed over from the parent to the child as a variable. This triggered no re-render on the child. After I copied the Observable variable to a Binding and handed it over like this, it worked fine. But I still don't understand why.

I had the same problem, but was already using a POD in the child. The data came into the parent view via an Observable object, though. The only solution was to copy the Observable to a Bindable in the parent and hand this bindable over to the child. Then it worked. Which is strange.

Awesome, thanks for the confirmation. I was hoping it worked this way.

This works. But what about non-preregistered images, like arbitrary QR Codes?