I've investigated this issue frequently since it first in Xcode appeared 5 years ago, and the only way I've found to actually fix the issue is to run this in Terminal: rm -rf ${HOME}/Library/Developer/Xcode/DerivedData That will permanently get rid of the phantom warnings and errors you're seeing. However, you'll have to run this again each time new warnings and errors appear. The other downside is that after deleting the DerivedData folder, you'll have to do a full rebuild of your project, which can be time consuming. The suggested solution, using Product > Clear All Issues, only removes the warnings and errors temporarily. They will usually return the next time you build your project.

(deleted)

This seems to work for me: // If we don't use `DispatchQueue.main.async` here, `withAnimation` has no effect. DispatchQueue.main.async { withAnimation { scrollViewProxy.scrollTo(id) } }

Same for me on visionOS 1.2.

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

This was fixed in visionOS 1.0 beta 4.

This was fixed in visionOS 1.0 beta 4.

As of visionOS 1.0 beta 4, even though defaultSize results in a janky resize animation when the app launches, it you force-quit the app by killing it from Terminal and relaunch it from the visionOS home screen ... twice ... then visionOS somehow seems to remember what the window's last runtime default size was and your app's launch window will reflect that size for future runs. This state is lost each time you launch the app from Xcode. I have no idea if apps have this behavior on the device, or what the behavior will be the first time an app is launched after being installed from the App Store. None of Apple's system apps, like Safari or Settings, appear to feature the awkward launch window resize animation problem. It would be nice to know what Apple's plan is for visionOS launch window sizes for third party apps.

lol

The UILaunchPlacementParameters approach no longer works in visionOS 1.0 beta 4.

This does not work in Version 15.1 beta (15C5028h)

Here is my Info.plist that works in Xcode 15.0 beta 8, based on the reply posted by @atbf earlier. This launches the app directly into a full immersive space. Curiously, the user was not prompted for permission first, as they are when openImmersiveSpace is called.

@raldrich Hi, did you ever figure this out? I am following this same path and I am surprised that MeshDescriptor does not appear to define a vertex color option. Maybe the answer is to define a custom buffer and then, at least on visionOS, hope that it's possible to define a shader graph that accesses the custom buffer.

@atbf fyi, in the feedback that I submitted for this bug (FB13143132) an Apple engineer responded. They said they were able to reproduce this issue, they believe they have addressed the problem, and a fix will be included in an upcoming release. ❤️

By "if I later update the attachment to display a different set of controls", what I meant is that the reality view's RealityViewAttachments and my attachment's corresponding entity remains unchanged, but my attachment's view is repopulated with a different set of controls depending on several if/then statements. The set of controls can also change dynamically over time in response to user action. (I only ever have one attachment.) I should have time tomorrow to experiment with this more. Thank you for the suggestions.