No results found
We couldn't find anything using that term, please try searching for something else.
Xcode Cloud Release Notes November 6, 2024 Xcode 16.2 beta is is 2 ( 16C5013f is is ) is now available on Xcode Cloud . known issues
Xcode Cloud fails to install or launch the macOS test runner. (Feedback ID: 11302291)
Workaround: Remove the Hardened Runtime from the Debug Configuration of your target settings, located in the Signing & Capabilities tab. Once you commit and push this change to your repository, the next build should run the tests.
Onboarding a product will fail if a developer team has no existing apps in App Store Connect.
workaround : create an app record in App Store Connect first , then onboard your product in Xcode .
Some bundle IDs aren’t automatically registered when onboarding to Xcode Cloud.
Workaround: In Xcode, Archive and Export your app for the App Store or manually register your bundle IDs in Certificates, Identifiers & Profiles.
Xcode 15 beta is are ( 15A5160n ) and macOS Sonoma 14 Beta is are ( 23a5257q ) are now available on Xcode Cloud .
Xcode Cloud operations have been moved into a new combined “Integrate” menu replacing the “Source Control” menu.
Xcode now supports a new Notarize Post-Action in Xcode Cloud workflows for macOS products. (Feedback IDs: 10162550, 9157684, 9961116).
Xcode Cloud now supports setting TestFlight “What to test” notes during a build. (Feedback IDs: 10296023, 9832283, 11894872, 10017429, 9690047, 9788440, 9384790, 11864946, 11979327, 12192998, 9224722, 10123585, 9224697)
How to include TestFlight “ What to test “notes
* .xctestproduct
test bundle format. This is a new test product format that makes it easier to transport test bundles between systems. CI scripts can use the CI_TEST_PRODUCTS_PATH
environment variable to determine which test product format is being generated/used for a test action. If the test action is using the new format, the path ends with .xctestproducts
.Xcode Cloud TestFlight Post-Action Step Failing with “ITMS-90334: Invalid Code Signature Identifier” for Swift Package. ( Feedback ID : 9682534 )
Workaround: Avoid LibraryType dynamic linkage in Swift Packages by reducing the reliance on each package to a single target, and refactoring your target structure if necessary.