Possibly related: Sometimes, in the iOS 18 simulator only, the ARView appears black and none of my app's geometry is rendered.

Hi, any updates on this issue? I'm concerned that when Xcode 17 is released, the new iOS 19 simulator won't support RealityKit reliably either, and supporting iOS 17 just so the simulator is useful for development will become problematic. Thank you.

I also installed 15.4.1 and Xcode 16.3 appears to work for me. I was able to run an app in the iOS 18.4 and iOS 17.5 simulators. Sorry that's not helpful. Does the simulator actually not load at all, or does your app not launch in the simulator, or does your app launch, but crash? Are you low on disk space? I'm sure you've tried all these, but off the top of my head: Try rebooting Try other simulator iOS versions In Xcode > Settings > Components try deleting the iOS simulator you're using (with right-click > Remove) and then reinstalling that simulator Delete everything in the Derived Data folder and rebuild Are you low on disk space? What have you tried already?

Hi, any updates on this issue? In new development, I just encountered “error 1” again trying to read a corrupt material that had been created for a different reason, and I wasted hours rediscovering the cause and tracking down the source of the problem. If RealityKit could respond with an error that provided any context at all, like the name of the shader graph node or the unrecognized attribute, the fix would have taken minutes instead of hours. I know you’re quite busy but I’d appreciate any response at all regarding the status of this issue. Thank you.

If you've implemented a workaround for this issue, you may want to investigate it again. I think it may have been fixed in iOS 18.5 or perhaps earlier.

(response continued from reply to the apple engineer in the accepted answer to work around the dev forum's 500 character comment limit) fwiw, the page https://developer.apple.com/documentation/realitykit/loading-entities-from-a-file describes .reality files in the context of the Reality Composer app (the old one), not Reality Composer Pro. Until you mentioned it just now, it wasn't clear to me that a RealityKitContent bundle contains a .realty file, as this implementation detail is not exposed in any user-facing way in Reality Composer Pro or Xcode. The page https://developer.apple.com/documentation/visionOS/designing-realitykit-content-with-reality-composer-pro does mention .reality files in two callouts that specifically refer to the their importance for performance reasons, but without deep investigation, this is confusing to a new user. I didn't notice that my project was using .reality files at all until just now when, motivated by your developer forums answer, I happened to look in /Users/drew/Library/Developer/CoreSimulator/Devices/A50E7AE3-EDE3-44BA-878B-E0DBE4A6F834/data/Containers/Bundle/Application/4C2EF75B-AE35-42B0-8A5B-ABE2B74CCE82/Baseball.app/RealityKitContent_RealityKitContent.bundle It would be nice if https://developer.apple.com/documentation/realitykit/loading-entities-from-a-file and the documentation for ModelEntity https://developer.apple.com/documentation/realitykit/modelentity and Entity(named:in:) https://developer.apple.com/documentation/realitykit/entity/init(named:in:) could be updated to make this clearer.

This issue appears to be fixed in Reality Composer Pro 2.0 (476.0.0.508.4), included with Xcode 26.0 beta (17A5241e).

As the engineer above wrote, the answer to this question is in the Xcode 26 release notes: Xcode may crash on launch restoring UI state. (152042209) Workaround: Remove your UserInterfaceState.xcuserstate file from the project/workspace. In macOS Terminal, you can find this file in your Xcode project directory tree with: find . -name '*.xcuserstate' -print and then delete it with rm. I have been assured that this is a cache file and contains no important project state and is safe to remove.

Workaround version that includes import SwiftUI:

FB18241928 includes a minimal sample app demonstrating the issue and detailed repro steps.

I was able to reproduce this bug in 26.0 beta 2 (17A5241o).

I was able to reproduce this bug using Xcode 26.0 beta 3 (17A5276g).

I encountered this same problem, but like @nevyn reported, the Xcode Cloud error referenced my RealityKit assets bundle as a whole, and not a skybox specifically. I discovered that the cause of the error was an ImageBasedLightComponent I had defined in my Reality Composer Pro project. My ImageBasedLightComponent was referencing a PNG file, not an HDR file. I still saw the error even after removing the PNG file reference entirely. I removed the ImageBasedLightComponent and created my ImageBasedLightComponent in code instead. After making that change, I was able to successfully deploy my app using Xcode Cloud, and I no longer saw the "realitytool requires Metal for this operation and it is not available in this build environment" error message.

I was able to reproduce this bug using Xcode 26.0 beta 4 (17A5285i).

I was able to reproduce this bug using Xcode 26.0 beta 5 (17A5295f).