After further investigation, I’ve isolated the problem to the use of ARView in a presented view controller along with a UIViewControllerAnimatedTransitioning custom dismiss animation (of the presented ARView view controller) that occurs immediately before the call to scrollToItem(at:at:animated:) in the view controller revealed when the presented ARView view controller is dismissed. Given this new information, I have resubmitted this issue as FB14718433.

I posted two possible workarounds below: https://developer.apple.com/forums/thread/761068?answerId=798573022#798573022

Thank you for responding. I've submitted this feedback: FB14615051

Thank you, this is extremely helpful to know. I had incorrectly assumed that Previews used RealityKit.

For visionOS 2, I'd like to test the notification that appears above the view. I can take your word for it that the displayed notification is simple and straightforward, but because on visionOS 1 the failure cases were complex, I am understandably still wary of this feature, and ideally I'd like to be able to test it and see it for myself. Thanks for responding, though. I'll just assume it works. (2/2)

For visionOS 1, I'd like to test each case, in which the user denies full immersive space permission, or presents the Safari page that provides more information about surroundings awareness, or accepts the full immersive space permissions. On visionOS 1, handling each of these cases correctly and providing appropriate fallback behavior was critical, or otherwise the user experience would be bad. There's no longer a way to test these cases now that I have visionOS 2 installed on the device. (1/2)

Thank you so much for answering quickly! This is truly awesome. I've wanted this feature for so long. It will make creating and maintaining complex shader graphs much more pleasant. I had read through all the documentation under Help > Reality Composer Pro Help but didn't see any mention of comments or groups. I think I may have experimentally right-clicked while searching for the feature, but I must not have associated the name "group" with "comment". It all makes sense now, though.

Thank you for responding to this question. Unfortunately, Product > Clear All Issues only removes the issues temporarily. They often return the next time the project is built. This has been an issue in Xcode since 2019. See https://superuser.com/questions/1405099/how-can-i-clear-faulty-error-messages-in-xcode FB13088245

(continuing previous comment) So, while I certainly understand your perspective, if would be helpful if Apple would provide broad strokes numbers as a starting point. The current situation is that each visionOS developer has to build their own experiments to determine this information.

Thank you for providing this advice. However, imagine the case of a third party app developer who hires a modeler to create assets for their app. When the modeler asks "How many triangles should this model be? How large should the texture map be?", how would you answer them? The third party developer can't tell the modeler, "I encourage you to think about performance and quality as an iterative optimization cycle." I assume the modeler wants real numbers.

For Apple Vision Pro, the USB-C developer strap can now be purchased via this page: https://developer.apple.com/visionos/resources/

Thank you.

Or you can add a feature to your app to call exit(0).

Also, instead of killing the app from the Terminal which requires tricks like ps -e | grep MyAppName.app to find the process ID, you could use ⌘Q via the simulator's passthrough mode.

Thank you for posting this. : - )