Have you looked into this alternate Apple method of handling gestures on 3d objects?

Maybe this can assist you, did you try adding : @Environment(\.scenePhase) private var scenePhase And then listening for changes, for example .onChange(of: scenePhase) { _, newPhase in if newPhase == .background || newPhase == .inactive { //do something, or check for `active` } }

Can also look at this article https://developer.apple.com/documentation/realitykit/transforming-realitykit-entities-with-gestures.

I have been using an M1 mbp 256 gb w 16gb of ram since it came out in 2020 for professional development. I develop iOS and visionOS apps, and this laptop still has good performance! But, every time Apple releases an Xcode beta, or when I am limited to a prior version of Xcode (when I need more thean 1 Xcode version on disk), I do have to do some disk cleanup, which I find tedious. For studies, I would recommend a MacBook that would also allow you to do professional development after you have graduated, and will still last you several more years! As mentioned above, the M2 air is a great choice, and would recommend at least 512 GB as well to avoid the chore of clearing up some disk space. Whatever you choose though, get at least 16 gb of ram! Dreaming of that M3 max :P

Add the following modifier on a view where appropriate in your code: .persistentSystemOverlays(.hidden) I actually resolved bug yesterday where the close and home button were missing! I found this modifier, commented it, and the missing controls appeared again.

We are having the same issue as described above on the iOS 17.2 simulator w Xcode 15.1 Beta 2. Here is our output: [plugin] AddInstanceForFactory: No factory registered for id <CFUUID 0x6000002e0d00> F8BB1C28-BAE8-11D6-9C31-00039315CD46 [aqme] AQMEIO.cpp:198 timed out after 15.000s (0 0); suspension count=0 (IOSuspensions: ) [aqme] MEDeviceStreamClient.cpp:467 AQME Default-InputOutput: client stopping after failed start: CA_UISoundClientBase@0x103b6bee0; running count now 0 CA_UISoundClient.cpp:293 CA_UISoundClientBase::StartPlaying: AddRunningClient failed (status = -66681). -[AVAssetTrack loadValuesAsynchronouslyForKeys:completionHandler:] invoked with unrecognized keys ("currentVideoTrack.preferredTransform"). [aqme] AQMEIO.cpp:198 timed out after 15.000s (0 0); suspension count=0 (IOSuspensions: ) [aqme] MEDeviceStreamClient.cpp:467 AQME Default-InputOutput: client stopping after failed start: <AudioQueueObject@0x1050fd600; Unknown FigPlayer; [2240]; play>; running count now 0 Warning: -[UITextInteractionAssistant selectionView] now returns nil with redesigned_text_cursor=on. [VisualTranslation] Visual isTranslatable: NO; reason: observation failure: noObservations [com.apple.VisionKit.RemoveBackground] Request to remove background on an unsupported device. Error Domain=com.apple.VisionKit.RemoveBackground Code=-8 "(null)" [com.apple.VisionKit.RemoveBackground] Error generating mask only remove background image for analysis: <VKCImageAnalysisResult: 0x103c4c230> - Error Domain=com.apple.VisionKit.RemoveBackground Code=-8 "(null)" [MADService] Client XPC connection invalidated

A bit more info from the article: The problem is that Swift doesn't allow you to place more than ten elements within a SwiftUI container, may it be a VStack , HStack , Group , Button or whatever. This is made aiming reusability and readability across your code. If you have too many elements in a single View , it may become hard to read and solve some UI bug. So Apple highly encourages you to take some of your inner views and keep them inside another container, or maybe a new custom View .

Resolution: use Group as reported by a medium article entitled Getting an "Extra Argument in Call" SwiftUI Error? Here’s How to Resolve This Bug. Quoting the article: "Containers in SwiftUI are like boxes with a limited content size, but each box is magical and counts just as a single unit, pretty cool, right? It means that no matter the internal content, each view can be placed inside another counting as only one, so each View can hold 10 direct subviews no matter what they are. Thinking about that, Group is a SwiftUI view that is made for holding some other views inside. "

Also facing same issue, message is "The iOS 13.3 simulator runtime is not supported on macOS 13.2.1."