Thank you, Greg. I appreciate your help.

Thanks, Greg. I was aware of those techniques and they are indeed quite helpful. However, the issue is really that they are only helpful when I want to filter out the RealityKit and PHASE logging a single time. In practice, I have to enable the filters 1000+ times each year. After the first 250 times, the novelty wears off, and I wonder if it's truly necessary for PHASE to tell me what that it's doing in CmConvolutionRenderer 30 times each second, for example.

I'm now encountering this same problem, after having successfully used Xcode Cloud in the past.

Thank you.

Thank you.

By “higher”, iDepth means “taller”, meaning the navigation bar takes up more screen real estate in iOS 26 than in iOS 18, which is not ideal.

Hurray that worked, thank you! 😀

Thank you! ❤️

Thank you.

Thank you for responding, I understand now. Please see my full reply in the comment below at https://developer.apple.com/forums/thread/785415?answerId=841201022#841201022

… 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.

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.

It would be wonderful if Xcode could make this issue clear to developers whenever a new version of Xcode is installed, when it prompts the user to install new components. I was unaware that Xcode was silently hoarding disk space, reported by System Settings > General > Storage only broadly as "System Data", with no other clues. I spent hours investigating why my disk was nearly full, and then eventually used Xcode > Settings > Components to recover 350 GB (!) of disk space I wasn't using.

Thanks for checking if there was a way to disable this behavior. I checked too and didn't see anything. Unfortunately, I believe that this issue would not be addressed if I submitted it as feedback. My memory is that this bug was introduced at least 3 years ago. My understanding is that as a rule, the Xcode team doesn't prioritize fixing bugs that aren't characterized as regressions relative to the previous Xcode release.

I've also created this new post about the issue: https://developer.apple.com/forums/thread/771281