Same here. Having an issue with Gitlab (not self-hosted) connection.

Seeing this same issue on my builds... Tried deleting all the Xcode Cloud certificates from the developer portal and restarting the build but still has issues.

This seems to be an issue with Cocoapods and will be resolved in a future version. See: https://github.com/CocoaPods/CocoaPods/issues/12012

For anyone wondering, I was able to debug this further by using ibtool from Xcode 14.3 and fortunately a rather suspect warning caught my attention: Main.storyboard:Aj5-Js-Cpe: warning: Unsupported configuration of constraint attributes. This may produce unexpected results at runtime before Xcode 5.1 [9] Turns out, there is an invalid constraint in my project referencing safe area layout guide's xCenter as both first and second item: Removing this constraint fixed the issue. Looks like this specific invalid constraint wasn't an issue for Xcode 14.3 but Xcode 15 is being more strict and crashing when it comes across this.

You can use the USDZ Tools from here: https://developer.apple.com/augmented-reality/tools/ "Download essential Python-based tools for generating, validating, and inspecting USDZ files. Also includes a converter that creates USDZ from other 3D file formats along with Pixar’s USD library and sample scripts."

I could also build my own color picker component, of course, but much rather use Apple's tried and tested components.

Same here. Filed FB13819647

Same. Filed FB13819647 already. There seems to be like 4-5 other threads of people with same issue too.

The feedback report was marked as Investigation complete - Works as currently designed today so it is safe to assume the bundle ID format will be changed from Xcode 16 forward. I just wish this change was documented and communicated somewhere.

I would also like to mention my report filed August 12th, 2024 regarding the same issue: FB14768097 The issue does not happen on latest 18.1 Betas. I hate to be that guy, but @DTS Engineer , are we sure the patch was applied to the 18.0 train and not removed in the release version?

This bug makes testing on simulators very hard. I had to reset the simulator 10 times just to capture some app screenshots. I hope it's being addressed with Super High priority