Post

Replies

Boosts

Views

Activity

Reply to Xcode 16 used in CI gets littered with empty user accounts
For clarity, I fixed the problem, with the following command : defaults write com.apple.dt.Xcode DVTDeveloperAccountManagerAppleIDLists -dict 'IDE.Identifiers.Prod' '({ "identifier" = "DEADBEEF-8599-416C-8362-E12AE4D7424F"; } )' "IDE.Prod" '({ "username" = "<apple_id>"; } )' instead of deleting the whole DVTDeveloperAccountManagerAppleIDLists. We have just updated to Xcode 16.1 so I don't know yet if it fixes the issue.
Oct ’24
Reply to Correct settings to setup Xcode/xcodebuild in a CI using automatically managed signing ? (Xcode 16)
To get back on this, adding the keyID/issuerID/keyFilePath triplet to our xcodebuild commands helps, however the problem remains that even with -allowProvisioningUpdates added to all commands, exporting a built archive fails with a "no profile found for bundle xxxx" error. The only way I've found to fix this to manually open the project in Xcode on the CI machine, go to the "Signing and capabilities" tab, let the spinner run until Xcode shows it has managed things, and only then the CI pipeline will work. It seems to me this is what the -allowProvisioningUpdates is for, but it doesn't seem to work.
Topic: Code Signing SubTopic: General Tags:
Oct ’24
Reply to Failed to build module 'CustomSDK'; SDK not supported by compiler due to Swift version mismatch on Xcode 16 Beta 6
I'm having a similar issue, with internal xcframeworks packaged in Cocoapods : Failed to build module 'Common'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)', while this compiler is 'Apple Swift version 6.0 effective-5.10 (swiftlang-6.0.0.9.10 clang-1600.0.26.2)'). Please select a toolchain which matches the SDK. The problem, is that the xcframeworks were built using Xcode 16.0, with BUILD_LIBRARY_FOR_DISTRIBUTION set to YES, but and I'm getting this error on Xcode 16.0 in an app that I'm trying to build using those xcframeworks. Update : I don't reproduce the problem when using the xcframeworks directly instead of through cocoapods, so I guess that's where the problem lies.
Topic: Programming Languages SubTopic: Swift Tags:
Sep ’24
Reply to Displaying multiple immersive movies in spheres in an immersive environment
I found how to do it : instead of a sphere, you need to add a SkySphere to your immersive environment in Reality Composer Pro, and set its material to be the immersive movie.
Topic: Spatial Computing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to OSLogStore can't access an app's extensions?
I have the same question (trying to fetch logs made by an app extension from the main app). Have you found a solution for this ?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Apr ’25
Reply to Running local package's tests in main app's test plan
Did you ever found a solution for this ? I'm running into the main problem and the Xcode (v16.10) doesn't even see the test target of the local package in the test plan.
Replies
Boosts
Views
Activity
Nov ’24
Reply to Xcode 16 used in CI gets littered with empty user accounts
For clarity, I fixed the problem, with the following command : defaults write com.apple.dt.Xcode DVTDeveloperAccountManagerAppleIDLists -dict 'IDE.Identifiers.Prod' '({ "identifier" = "DEADBEEF-8599-416C-8362-E12AE4D7424F"; } )' "IDE.Prod" '({ "username" = "<apple_id>"; } )' instead of deleting the whole DVTDeveloperAccountManagerAppleIDLists. We have just updated to Xcode 16.1 so I don't know yet if it fixes the issue.
Replies
Boosts
Views
Activity
Oct ’24
Reply to Xcode 16 cloud signing failure in CI while other app with same configuration works correctly
Add: I've cleared all the empty accounts, it doesn't fix the issue.
Replies
Boosts
Views
Activity
Oct ’24
Reply to Correct settings to setup Xcode/xcodebuild in a CI using automatically managed signing ? (Xcode 16)
To get back on this, adding the keyID/issuerID/keyFilePath triplet to our xcodebuild commands helps, however the problem remains that even with -allowProvisioningUpdates added to all commands, exporting a built archive fails with a "no profile found for bundle xxxx" error. The only way I've found to fix this to manually open the project in Xcode on the CI machine, go to the "Signing and capabilities" tab, let the spinner run until Xcode shows it has managed things, and only then the CI pipeline will work. It seems to me this is what the -allowProvisioningUpdates is for, but it doesn't seem to work.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’24
Reply to Xcode 16 warning about missing symbols of static framework
I'm seeing this as well on a project using multiple home-built dynamically linked xcframeworks, but they are packaged as a zip file in a single cocoapod. I think cocoapod is the culprit here.
Replies
Boosts
Views
Activity
Oct ’24
Reply to Failed to build module 'CustomSDK'; SDK not supported by compiler due to Swift version mismatch on Xcode 16 Beta 6
I'm having a similar issue, with internal xcframeworks packaged in Cocoapods : Failed to build module 'Common'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)', while this compiler is 'Apple Swift version 6.0 effective-5.10 (swiftlang-6.0.0.9.10 clang-1600.0.26.2)'). Please select a toolchain which matches the SDK. The problem, is that the xcframeworks were built using Xcode 16.0, with BUILD_LIBRARY_FOR_DISTRIBUTION set to YES, but and I'm getting this error on Xcode 16.0 in an app that I'm trying to build using those xcframeworks. Update : I don't reproduce the problem when using the xcframeworks directly instead of through cocoapods, so I guess that's where the problem lies.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Sep ’24
Reply to iOS 17.0 beta 5 (21A5303d) simulator fails to install
Same here, with Xcode 15, and about 80GB free. This is rather annoying.
Replies
Boosts
Views
Activity
Sep ’23
Reply to failed to prepare device for deployment
I had the same issue with Xcode 14, and a device running iOS 15.7. Two different macs (running the same config), tried rebooting both and the device, nothing worked. What fixed the issue was installing Xcode 13.4.1 and preparing the device with it.
Replies
Boosts
Views
Activity
Sep ’22