I can confirm this same issue is also occurring on my device. I am using visionOS Developer Beta 2.5, and can reproduce this issue by using Apple's Sample Code Building local experiences with room tracking. If Apple could confirm that this is either; A bug in the ARKit World Anchor persistence or expected behaviour, that ARKit World Anchors must persist at least one anchor that would be very helpful for us!

I can confirm I also have this issue on VisionOS 2.5. Using the sample code https://developer.apple.com/documentation/visionos/building_local_experiences_with_room_tracking you can replicate the issue. I have also submitted this to Feedback Assistant.

After multiple reboots, the issue has resolved itself and the attached code now works as expected with no build changes. When present the issue was present for several hours across multiple reboots before resolving. I will update again here if it reoccurs!

Reverting to Beta 3 also does not work with this sample.

Reverting to visionOS 26 Beta 2, the sample works as expected!

I am still getting this issue on the full release of VisionOS 26. On rare occasions, the issue does not occur, but closing the app and relaunching the app returns the issue.

To resolve the issue, the only solution I have found is to Restore OS 26 image using the Developer Strap and Configurator. Image from https://developer.apple.com/download/os/

@Vision Pro Engineer After updating to the latest OS (non-Beta) the issue returned. Deleting all ‘Widget’ in my space resolved the issue. That may be why restoring OS previously worked, as that would have also reset any widgets in my device. I have updated my Feedback Assistance post with this information as well. (FB18362829) thank you to @jkdufair for this suggestion.

Same issue here, but while using Navigation Stack and navigating to a child path. Did you ever find a workaround?

@Vision Pro Engineer I have submitted a Feedback Post with a code sample for this issue. FB22536529. Please note, this Feedback Post is one of many variations of the problem, using an If/Else not NavigationStack, where tapping the screen allows the camera feed to appear. However, in other cases the camera never appears. I will create additional Feedback Posts for those other cases, once I can isolate the code into repeatable sections.

@Vision Pro Engineer I have submitted a second Feedback Post with an example using NavigationStack, where the camera feed never appears, even after tapping the screen FB22537390. Next I will submit additional RealityView bugs relating to the camera not turning off, and FloorAnchor not working as expected. I will mention them here but also create a new Form post for them as they are fundamentally different issues.