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 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 already did this.

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".

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.

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