@baderer I confirm we got the issue on our Mac mini intel, but it did not happened on our Mac Studio.
The fix I mentioned previously with generic platform did work for us.
I don't think this is related to the "EOL" of intel chips, maybe just a bug with Xcode 15.4 and x86 🤷♂️.
Post
Replies
Boosts
Views
Activity
I got a similar issue on our CI (Mac mini) during iOS build stage and after checking logs I discovered this trace:
Details: (null) deviceType from XXXXXXXX-XXXXXXXXXXXXXXXX was NULL when -platform called. Object: <DTDKMobileDeviceToken: 0x7fe75d2ec4a0> Method: -platform Thread: <NSThread: 0x600002fee380>{number = 2, name = (null)} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. Segmentation fault: 11
The build was failing randomly probably due to the fact that xcodebuild was somehow unavailable to detect or communicate with our iPhone 15 Plus (connected to the Mac mini).
I fixed this issue replacing this original destination parameter:
xcodebuild xxxxxx -destination "platform=iOS"
using the Generic Platform:
xcodebuild xxxxxx -destination "generic/platform=iOS"
Hope it will help some developers struggling with segmentation fault 11 💥.