Hi, We successfully migrated to the new AppIcon from Icon Composer. Everything works great on simulator and on real devices. We also released a manually generated build that works great. However when we build the same project from Xcode Cloud we get the following error: None of the input catalogs contained a matching stickers icon set, app icon set, or icon stack named "AppIcon" The previous line seems to indicate that no icon is passed: /Applications/Xcode.app/Contents/Developer/usr/bin/actool /Volumes/workspace/repository/Mail/Assets.xcassets --compile /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_output/thinned --output-format human-readable-text --notices --warnings --export-dependency-info /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_dependencies_thinned --output-partial-info-plist /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_generated_info.plist_thinned --app-icon AppIcon --accent-color AccentColor --compress-pngs --enable-on-demand-resources YES --development-region en --target-device iphone --target-device ipad --minimum-deployment-target 15.0 --platform iphoneos However when I archive locally, the icon seems correctly referenced: /Applications/Xcode.app/Contents/Developer/usr/bin/actool /Users/<my name>/Developer/ios/infomaniak/apps/ios-kMail/Mail/Resources/AppIcon.icon /Users/<my name>/Developer/ios/infomaniak/apps/ios-kMail/Mail/Resources/Assets.xcassets --compile /Users/<my name>/Library/Developer/Xcode/DerivedData/Mail-fbgflwyftafvlmezepjlymckizhg/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_output/thinned --output-format human-readable-text --notices --warnings --export-dependency-info /Users/<my name>/Library/Developer/Xcode/DerivedData/Mail-fbgflwyftafvlmezepjlymckizhg/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_dependencies_thinned --output-partial-info-plist /Users/<my name>/Library/Developer/Xcode/DerivedData/Mail-fbgflwyftafvlmezepjlymckizhg/Build/Intermediates.noindex/ArchiveIntermediates/Infomaniak\ Mail/IntermediateBuildFilesPath/Mail.build/Release-iphoneos/Infomaniak\ Mail.build/assetcatalog_generated_info.plist_thinned --app-icon AppIcon --accent-color AccentColor --compress-pngs --enable-on-demand-resources YES --development-region en --target-device iphone --target-device ipad --minimum-deployment-target 15.0 --platform iphoneos Has anyone encountered a similar issue ?

My project build failed in Xcode Cloud(works well in my local Mac), and the error shows: Preparing build for App Store Connect failed The error message is not clear enough to help us find the solution to fix it. Can anyone help with it?

I have a workflow where I want to specifically run some tests in the iOS 18 simulator. All while using Xcode 26 on Xcode Cloud. In my Xcode Cloud workflow I can set the iOS version, but just iOS 16, 17 and 26, but no 18? I'm very confused here Not sure which is the right channel anyway to request support to Xcode Cloud too

Hi everyone, After opting out of Xcode Cloud, I tried to set it up again for my product. However, I’m getting the following message when attempting to reconnect to my source control provider: "Connecting Xcode Cloud with your source control provider was incomplete. Products cannot be configured to use Xcode Cloud while your team’s opt-out request is being processed." It’s been 7 days since I opted out, and I still haven’t been able to re-enable Xcode Cloud. I’ve tried reconnecting both GitHub and Bitbucket, but the same message appears in both cases. I’d like to know: How long does the opt-out (deregistration) process usually take to complete? Is there any way to check the current status or expedite the reactivation process? Team Type: Organization Region: Japan Any insights or similar experiences would be greatly appreciated. Thank you in advance!

When running an Xcode Cloud workflow pinned to Xcode 26.1, macOS 26.1 and using a Test Destination for iPhone 15 Pro and iOS 26.1, the following error appears in the xcodebuild-build-for-testing.log: 2025-11-13T19:08:31.855137440Z xcodebuild: error: Unable to find a destination matching the provided destination specifier: 2025-11-13T19:08:31.855318998Z { platform:iOS Simulator, id:704F84C8-025F-4F70-B2D9-FF19B7DC098F } 2025-11-13T19:08:31.855362640Z 2025-11-13T19:08:31.855370957Z Ineligible destinations for the "Inbound" scheme: 2025-11-13T19:08:31.855381964Z { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device, error:iOS 26.1 is not installed. Please download and install the platform from Xcode > Settings > Components. } This can be fixed if ci_pre_xcodebuild.sh is updated with the following: # Get Xcode major version # `xcodebuild -version` returns something like: # Xcode 26.0.1 # Build version 17A400 XCODE_VERSION=$(xcodebuild -version | head -n 1 | awk '{print $2}' | cut -d. -f1) if [ "$XCODE_VERSION" -ge 26 ]; then if xcodebuild -downloadPlatform iOS >/dev/null 2>&1; then echo "iOS platform is installed" else echo "iOS platform is not installed. Failing the build." exit 1 fi fi Changing the workflow to use "Latest Release" of Xcode (26.1), macOS (26.1) and the Latest Test Destination iOS (26.1) version provided also does not work.

I'm using Xcode Cloud to build for internal TestFlight testing. But it stuck in Archive. No warning or error. Unable to complete the workflow. What could be causing this? I have absolutely no idea what to do now.

【溦N51888M】腾龙公司直属会员怎么开户【罔纸 211239.com 】输入官惘到浏览器打开联系24小时在线业务人员办理上下，打开公司官网. 二、点击主页右上角注册按钮. 三、填写账号信息. 四、输入手机号，验证码，密码. 五、勾选用户协议，完成注册协议，完成注册. 注意：若出现账号已存在」提示，需重新设置唯一账号名称

Hello, My project is GitLab and to access it we need VPN. How to connect Xcode Cloud to that repo if VPN is required for read it? Any solution to this? Any help is appreciated

Hi, Since Xcode 26.2 beta 1, till now (I thought RC or actual release will solve this issue) I have problems exporting archive to appstore via Xcode Cloud (locally everything works and using Xcode 26.2 I was able to submit app to AppStore). Build is archived successfully but during export I get an error Exporting for App Store Distribution failed. Please download the logs artifact for more information. In xcodebuild-export-archive.log I see multiple attempts & errors like this 2025-12-13T08:29:34.040644840Z 2025-12-13 00:29:33.900 xcodebuild[10889:58988] DVTServices: Sending request 9A4173F4-CD87-4A76-95FC-501B4D11EF22 to <http://172.16.55.70:8089/services/v1/capabilities> for session DVTFoundation.DVTServicesSessionProxy. 2025-12-13T08:29:34.040647258Z Method: POST 2025-12-13T08:29:34.040648780Z 2025-12-13T08:29:34.040650230Z Headers: 2025-12-13T08:29:34.040651730Z { 2025-12-13T08:29:34.040653539Z Accept = "application/vnd.api+json"; 2025-12-13T08:29:34.040655403Z "Accept-Encoding" = "gzip, deflate"; 2025-12-13T08:29:34.040673847Z "Content-Length" = 124; 2025-12-13T08:29:34.040675883Z "Content-Type" = "application/vnd.api+json"; 2025-12-13T08:29:34.040677903Z "User-Agent" = Xcode; 2025-12-13T08:29:34.040681998Z "X-HTTP-Method-Override" = GET; 2025-12-13T08:29:34.040684468Z "X-Xcode-Version" = "26.2 (17C52)"; 2025-12-13T08:29:34.040686326Z } 2025-12-13T08:29:34.040688028Z 2025-12-13T08:29:34.040689711Z Payload: 2025-12-13T08:29:34.040692163Z {"urlEncodedQueryParams":"teamId=8CKLLLC9UE&filter%5BreferenceType%5D=bundle&filter%5BincludeRequestable%5D=true&limit=200"} 2025-12-13T08:29:34.308538247Z 2025-12-13 00:29:34.208 xcodebuild[10889:58988] DVTServices: Received response for 9A4173F4-CD87-4A76-95FC-501B4D11EF22 @ <http://172.16.55.70:8089/services/v1/capabilities>. Code = 0 2025-12-13T08:29:34.308555026Z 2025-12-13 00:29:34.208 xcodebuild[10889:58988] DVTServices: Response payload: { 2025-12-13T08:29:34.308557639Z "errors" : [ { 2025-12-13T08:29:34.308569919Z "id" : "0316154c-332b-4f9d-a90a-5770d4f8dc1a", 2025-12-13T08:29:34.308573588Z "status" : "400", 2025-12-13T08:29:34.308575871Z "code" : "PARAMETER_ERROR.INVALID", 2025-12-13T08:29:34.308578343Z "title" : "A parameter has an invalid value", 2025-12-13T08:29:34.308581767Z "detail" : "A parameter 'filter[includeRequestable]' has an invalid value : ''includeRequestable' is not a valid field name.'", 2025-12-13T08:29:34.308584989Z "source" : { 2025-12-13T08:29:34.308587270Z "parameter" : "filter[includeRequestable]" 2025-12-13T08:29:34.308589531Z } 2025-12-13T08:29:34.308591437Z } ] 2025-12-13T08:29:34.308593381Z } 2025-12-13T08:29:34.308595389Z 2025-12-13T08:29:34.308597297Z 2025-12-13T08:29:34.308600188Z 2025-12-13 00:29:34.208 xcodebuild[10889:58988] DVTServices: Could not fetch capabilities from network due to error: error = 'A parameter has an invalid value' When I use Xcode 26.1.1 to export the same commit, eveything works and workflow sends build to AppStoreConnect, any ideas what might cause this issue? Unfortunately I need to use Xcode 26.2 if I want to use tabViewBottomAccessory(isEnabled:content:) bcs even though this api is available since iOS 26.1, it's not available in Xcode 26.1

Log shows: Run command: 'xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/d3c9c43f-e24e-4ad9-882d-d0179ab3149b.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist '-DVTPortalRequest.Endpoint=http://172.16.182.66:8089' -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3' Command exited with non-zero exit-code: 70

I'm using Xcode Cloud for release builds and unit tests, and it works fine. Recently, I added some XCUITests, but to run it the way I need I started to use this mock server. Basically, the idea is you define before each test what responses you want to get for specific requests. It works like a charm locally. But if I want to run it in Xcode Cloud, it looks like the server has failed to launch. The mock server is a separately launched binary file. I think this is because this permission I get when launch it locally. So, my question is how to allow this kind of permission in Xcode Cloud to make my UITests works correctly? You can find a detailed instruction how server is launched on a github page I provided.

I am setting up a new app and am having problems with Xcode Cloud. From Xcode if I click on the "Cloud" button under the Report Navigator I get a spinner for a long time then get the message "Could not load Xcode Cloud data". I also visited the "Xcode Cloud" tab under my app in App Store Connect and I get a spinner and nothing loads. This is a recent account and I'm setting up Xcode Cloud for the first time. Below is what I've tried and I'm out of ideas on how to get this working. In Xcode, I signed out and back in as the Account Holder Closed Xcode and reopened This occurred yesterday and today and have not seen a problem under the Apple System Status page On the latest Xcode 16.2 Checked the Signing & Capabilities tab in Xcode and my team a bundle Id is correct and it's happy with signing. At this time on my machine I am using the distribution profile.

There seems to be a problem to a specific Apple Developer Account regarding Xcode Cloud Distribution (Signing). The Xcode Cloud Error Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “XcodeCloudTest.app/XcodeCloudTest” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. Investigation Apple Developer Forums This issue seems to be known: https://developer.apple.com/forums/thread/746210 Debugging by ourselves We setup an example Xcode project from a default iOS Xcode app template to rule out any project issues. This example project failed with the same error as stated above. In the next step we tried the same example project with a different Apple Developer Account and it successfully distributed the example App through Xcode Cloud. Conclusion It seems like there is no setup issue on developer-side, because our example project works out-of-the-box on a different Apple Developer Account. Our only hope is that Apple will have a look on our Developer Account. Maybe there is some internal setting.

Since today, all our team members cannot download artifacts from Xcode Cloud builds. We get a JSON response that contains: {"message":"You are not authorized to access this team’s resources."} System Status doesn't show any issues at the time. Is there an action we can follow to restore proper access? Thank you in advance.

I've noticed that when using the Test action in an Xcode Cloud workflow, the xcodebuild command includes COMPILER_INDEX_STORE_ENABLE=NO while performing build-for-testing. This disables the index store, which is required by tools like Periphery to analyze unused code. Without indexing, Periphery triggers a fresh build internally, resulting in a significant increase in CI build time. Is there any way to enable indexing (COMPILER_INDEX_STORE_ENABLE=YES) on Xcode Cloud? Or alternatively, is there a recommended workaround to generate and access the index store? Any help is appreciated.

We started seeing an access issue today when attempting to go to the Xcode Cloud tab in App Store Connect. When you navigate to https://appstoreconnect.apple.com/teams/:teamId/apps/:appId/ci we're seeing the following message: The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I am the account holder so it shouldn't be a permissions issue. Is there an ongoing outage or problem in Xcode Cloud? And, if so, where can I monitor this accurately?

Any operation related to Xcode Cloud (e.g., viewing the dashboard, creating a workflow) fails immediately across all Xcode projects, including brand-new empty projects. The error is consistent and always appears as: API Invalid status code: 401. Domain: XcodeCloudCombineAPI.XCCResponseError Code: 1 System Information: macOS Version 15.6.1 (Build 24G90) "details" : "Error alert: API Invalid status code: 401.: XCCResponseError(responseErrorType: XcodeCloudCombineAPI.XCCResponseError.XCCResponseErrorType.invalidStatusCode(XcodeCloudCombineAPI.LegacyHttpStatus.unauthorized), requestUrl: Optional(https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/\/apps\/find?bundle_id=), traceId: Optional(\"2ab09bea8da9ef39\"), retryAfterSecsStr: nil, response: Optional(<NSHTTPURLResponse: 0x600000c6a800> { URL: https:\/\/appstoreconnect.apple.com\/ci\/api\/teams\/\/apps\/find?bundle_id=} { Status Code: 401, Headers {\n \"Content-Length\" = (\n 0\n );\n Date = (\n \"Fri, 05 Sep 2025 10:04:07 GMT\"\n );\n Server = (\n nginx\n );\n \"Set-Cookie\" = (\n \"dqsid=; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Path=\/; Secure; HTTPOnly\",\n \"dqsid=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE3NTcwNjY2NDQsImp0aSI6IlNQZ1FxVXd1UFF1UjI1X2wtZ2ZjN2cifQ.uoE9MRTx-TCY03Sw1qgMBcWrPVA8adtKd-nOZVwllS4; Max-Age=1800; Expires=Fri, 05 Sep 2025 10:34:04 GMT; Path=\/; Secure; HTTPOnly\"\n );\n \"Strict-Transport-Security\" = (\n \"max-age=31536000; includeSubDomains; preload\"\n );\n \"x-apple-jingle-correlation-key\" = (\n ZNGYRW2NJQJKAYDKU5FGCY6VVE\n );\n \"x-b3-traceid\" = (\n 2ab09bea8da9ef39\n );\n \"x-cache-status\" = (\n BYPASS\n );\n \"x-content-security-policy\" = (\n \"script-src 'self' *.apple.com\"\n );\n \"x-content-type-options\" = (\n nosniff\n );\n \"x-daiquiri-instance\" = (\n \"daiquiri:15751001:mr36p00it-hyhk07174801:7987:25RELEASE91:daiquiri-amp-dsce-asc-int-002-mr\",\n \"daiquiri:18493001:mr85p00it-hyhk03154801:7987:25RELEASE91:daiquiri-amp-all-shared-ext-001-mr\"\n );\n \"x-frame-options\" = (\n SAMEORIGIN\n );\n \"x-via\" = (\n \"2.0 PS-WUH-01zra68 [BYPASS]\"\n );\n \"x-ws-request-id\" = (\n \"68bab594_PS-WUH-01zra68_27159-54435\"\n );\n \"x-xss-protection\" = (\n \"1; mode=block\"\n );\n} }))\nError Description: Optional(\"API Invalid status code: 401.\")\nRecovery Suggestion: nil\nHelp Anchor: nil",

Xcode 26 RC is not available on Xcode Cloud. This is a serious blocker affecting developers trying to be on App Store on day 1 of the OS 26 release. Is there an estimate when this can be in place?

We have had 2 Builds so far stuck archiving. Both indicate in their logs that Build Archive took a normal amount of time (9m and 19m) but the step Archive - iOS never finished. One of them ran for more than 6 days until we noticed and canceled it. The other one ran for 18 hours, and also had to be canceled manually. They were in two different projects, with no significant changes. The first build ran on Xcode 16.4 (16F6) and macOS Sequoia 15.6 (24G84), which we had had no issues like this with until just now, and the second ran on Xcode 26 (17A324) and macOS Tahoe 26 (25A354). We tested our app on the newest Xcode version and had no issues. Submitted report using feedback assistant: FB20279737.

Hi, our builds with a Test action in Xcode Cloud are failing because of an internal Xcode Cloud crash. We see the "red cloud with an X" icon, that indicates that it's an Xcode Cloud issue, and the message says "The Test - iOS action could not complete due to an error. The error may not occur on rebuild." but this has been happening for a while now, and for repeated builds. In the artifacts there is a crash log apparently related to the "ibtoold" process, has anybody had this issue before? Thanks