Hello! I have a web extension I've written to Google Chrome and Mozilla Firefox. It's made up of simple files. The extension (content.js) A manifest (manifest.json) file which explains the extension The icon (icon.png) Apple has developed App Store Connect / Xcode Cloud specifically for this. I upload those three files as a zip. I move it over to TestFlight for testing and then select Distribution to put it through Apple Review. This is my entire process. I have been doing this for 4+ months and Apple reviewed my application and put it up. I have then gone through 13 subsequent reviews (ALL POSITIVE) and have gone through version upgrades for months, no issue. On the 15th review, they want me to change the name of my application. I have done that in the content.js, the manifest.json, and anywhere that allows me to change it in App Store Connect. There is apparently one more place they want it changed. This is on the App Information / General Information tab, specifically the "BundleID". The tip on that field says: The bundle ID must match the one you used in Xcode. It can't be changed after you upload your first build. Or, I am not understanding what their issue is or what else I can change. I was told by Review team I must use XCODE to change this. I tell them I don't use XCode (they demand now I use Xcode, which seems completely irrelevant here and a red herring The tooltip itself says I can't change it anyway? Has anyone been told after they released their application they have to change their name later on in life?

Good morning all, We have an on-premise instance of Bitbucket (v8.19.25), using a custom port. We'd like to try using Xcode Cloud, compare to our current CI/CD provider. Once I have to select my source control provider to grant access, I select Bitbucket Server. If I try to input the Host Name with, or without a port, I'm receiving this response: { "message": "An error occurred", "details": [ { "message": "An error occurred", "source": "host" } ], "actions": [], "recovery_actions": [ { "dismiss_label": "OK" }, { "feedback_label": "Provide Feedback", "feedback_component": "Xcode Cloud | New Bugs" } ], "should_show_error": true } Which, of course, doesn't help me in the slightest to understand why the connection fails. I do notice that the request to https://appstoreconnect.apple.com/ci/api/teams/<id>/setup-flow/scm-repositories in the web inspector already includes a host and port that I use to clone the repository locally. However, the web-based interface of Bitbucket doesn't include that port. So, if I clone a repo: ssh://<bitbucket-instance>:<port>, but if I look at pull requests: https://`. My colleagues have already determined that there shouldn't be any firewall rules or gateway limits, so Bitbucket should be reachable. No VPN either. How can I continue to fix this?

Xcode Cloud builds are hanging forever at the final step, Prepare Build for App Store Connect. This is a common issue that requires some fix in Cupertino. Reporting this in the afternoon of Jan 13, Pacific Time.

Hello Apple Developer Support Team, I am writing to request assistance with an issue preventing me from distributing my iOS app to the App Store. I am able to successfully build and archive my app in Xcode without errors. However, after archiving, Xcode only shows the option “Distribute Content” instead of “Distribute App”. Because of this, I am unable to upload the app to App Store Connect. App & Account Details • App Bundle Identifier: com.yesbuy.yesbuyapp • Team Name: Fathima Sayed Mohamed • Team ID: Z327MG963D • Xcode Version: 26.2 • macOS Version: macOS 15.6.1 Signing & Certificates • Signing Method: Automatically manage signing (enabled) • Signing Certificate (Release): Apple Distribution: Fathima Sayed Mohamed • Provisioning Profile: Xcode Managed / App Store Distribution • Archive Status: Build succeeded What I’ve Already Verified • The archive is created using Release configuration • Skip Install is set to No for the main app target (Runner) • The app target is selected correctly during Archive • A valid Apple Distribution certificate exists • The app is registered correctly in App Store Connect • App Groups and capabilities are configured correctly • Notification Service Extension is present and signed Despite all of this, Xcode still treats the archive as a Generic Xcode Archive and only allows Distribute Content, not Distribute App. I have attached screenshots showing: 1. Xcode Archives screen (showing “Distribute Content” only) 2. Signing & Capabilities for the app target 3. Certificates and provisioning profiles 4. Team ID and bundle identifier configuration Could you please review this issue and let me know: • Why the archive is not recognized as an App Store–distributable app • Whether there is any account, certificate, or configuration issue on Apple’s side • Any steps I should take to resolve this and successfully upload the app to App Store Connect Thank you very much for your time and support. I look forward to your guidance.

After pushing to a branch which is automatically configured to build and distribute on TestFlight, I found no way to log on and check Xcode cloud builds and nothing being pushed to that branch was building or showing up elsewhere in App Store Connect.

I’m trying to integrate our app with the iXGuard obfuscation tool, which needs to run in the archive post-actions step in Xcode Cloud. The issue is: iXGuard takes a long time to complete and, during its execution, does not generate any console output or logs in the Archive Post-actions step. Problem: When Archive Post-actions runs for a long time without producing log output, Xcode Cloud triggers a timeout and the workflow stops before running the next CI step (e.g., ci_post_xcodebuild.sh). Even though the script continues running in the background, the workflow is aborted due to inactivity in the logs. Workaround Tried: As a workaround, I have ci_post_xcodebuild.sh print the logs generated by archive post-actions. However, this does not help in my case since the timeout occurs before ci_post_xcodebuild.sh even runs. Error: The step invocation hit a user timeout. The xcodebuild archive invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. Question: Is there a recommended way to prevent Xcode Cloud from timing out during long-running steps that do not produce log output? Are there best practices for keeping the workflow alive with periodic logs during Archive Post-actions? Any support or workaround for integrating tools like iXGuard that require significant processing time after the archive step? Thanks in advance for your help!

Hello guys, recently I integrated a third-party library into my code to handle blur effects (Glur). This library leverages Metal's compute capabilities and appears to automatically depend on the Metal toolchain during the build process. When using Xcode Cloud, the archive step consistently fails with a "CompileMetalFile Failed" error. However, when I manually archive the project in Xcode locally, everything works fine without any issues. I’ve confirmed that the macOS and Xcode versions specified in my Xcode Cloud workflow are correct. Reply if you know how to fix it or it will be fixed future, thanks. I'm using Xcode 26.2(17C52) and macOS(15.7.1 (24G231))

Since Dec 18th, my Xcode Cloud builds (for multiple apps) have been failing with this error: Command line name "app-store" is deprecated. Use "app-store-connect" instead. I haven't made any changes to my system, signing, etc, and two separate apps started failing at the same time. No matter what I change on my Workflows (environment, new workflow from scratch, etc), nothing seems to fix it, which leads me to believe this is a bug with Xcode Cloud itself. I've logged FB21456291 already, but just wanted to post here to see if I'm missing something.

Error: Preparing build for App Store Connect failed No error logs in log view. Download the archive and try to submit to App Store: Detailed logs: 2025-12-17 07:26:00 +0000 [MT] Command line name "app-store" is deprecated. Use "app-store-connect" instead. 2025-12-17 07:26:00 +0000 App Store Connect request for store configuration failed for account Session Proxy Provider (Account "Session Proxy Provider": Unable to authenticate with App Store Connect (Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)")) 2025-12-17 07:26:00 +0000 App Store Connect response failed with unknown failure for credential <DVTFoundation.DVTServicesSessionProviderCredential: 0x600002e099c0>; response (null); error (null). 2025-12-17 07:26:00 +0000 App Store Connect request for store configuration for credential <DVTFoundation.DVTServicesSessionProviderCredential: 0x600002e099c0>; configuration: (null); error DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy 2025-12-17 07:26:00 +0000 [MT] Failed to find an account with App Store Connect access for team <IDEProvisioningBasicTeam: 0x6000029c0240; teamID='984L9QX9X5', teamName='(null)'> 2025-12-17 07:26:00 +0000 [MT] Running step: IDEDistributionFetchAppRecordStep with <IDEDistributionContext: 0x7fa62b216680; archive(resolved)="<IDEArchive: 0x600000315ea0>", distributionTask(resolved)="2", distributionDestination(resolved)="1", distributionMethod(resolved)="<IDEDistributionMethodiOSAppStoreDistribution: 0x600002a1f560>", team(resolved)="<IDEProvisioningBasicTeam: 0x6000029c0240; teamID='984L9QX9X5', teamName='(null)'>">

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

Export archive step fails in Xcode Cloud when using Xcode 26.2 (17C48) RC. The same project exports successfully when switching back to Xcode 26.1 in Xcode Cloud workflow settings. The same project exports successfully when using Xcode 26.2 RC locally. Projects without Apple Watch app do not encounter this issue (not so sure about this). From Xcode Cloud UI: Exporting for App Store Distribution failed. Please download the logs artifact for more information. Run command: 'xcodebuild -exportArchive ... Command exited with non-zero exit-code: 70 From xcodebuild-export-archive.log: error: exportArchive Automatic signing cannot update bundle identifier "io.***.***.watchkitapp". error: exportArchive No profiles for 'io.***.***.watchkitapp' were found error: exportArchive Automatic signing cannot update bundle identifier "io.***.***". error: exportArchive No profiles for 'io.***.***' were found ** EXPORT FAILED ** IDEDistribution: App Store Connect request for store configuration failed for account Session Proxy Provider (Account "Session Proxy Provider": Unable to authenticate with App Store Connect (Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)")) DVTServices: Sending request A7605D4E-2892-4B6D-9197-90BD3AB53D67 to <http://172.16.57.4:8089/services/v1/capabilities> Payload: {"urlEncodedQueryParams":"teamId=984L9QX9X5&filter%5BreferenceType%5D=bundle&filter%5BincludeRequestable%5D=true&limit=200"} { "errors": [{ "id": "fb67ecdb-103b-4446-a2db-618fd6bd99e7", "status": "400", "code": "PARAMETER_ERROR.INVALID", "title": "A parameter has an invalid value", "detail": "A parameter 'filter[includeRequestable]' has an invalid value : ''includeRequestable' is not a valid field name.'", "source": { "parameter": "filter[includeRequestable]" } }] } DVTServices: Could not fetch capabilities from network due to error: error = 'A parameter has an invalid value' Workaround Switching Xcode Cloud workflow to use Xcode 26.1 works around the issue. Using Xcode 26.2 RC locally works around the issue.

Hello, My app (App ID: 1616628950) is already published on the App Store, but recently we’ve been unable to install the TestFlight build for testing. The TestFlight build shows the green “Testing” status, but whenever we try to install it, we get this message: “Could not install / The requested application is not available or does not exist.” The TestFlight version is the same as the one currently live on the App Store, and the App Store version installs without any issue. I wanted to share this here in case someone from the team could check whether the TestFlight build might be stuck or misconfigured on the backend. Thank you very much for your time and help!

I can create an ipa file with vs using the wildcard bundle identifier but this is rejected by apple when I upload with the Transporter app saying invalid identifier and no distribution profile/certificate. When I create a new distribution profile with the correct XC identifier and distribution certificate and try to archive with visual studio publish says the bundle id is not a match for the distribution profile with iOS? This is a net 10 net maui project and my first build attempt

Hi everyone, I’m unable to enable Xcode Cloud for any app on my account. At the final step of the Xcode workflow setup (“Confirm App on App Store Connect”), pressing Complete always returns: “ could not be added to Xcode Cloud. Authentication credentials are invalid.” This affects both existing apps and completely new test apps with fresh bundle IDs. What I’ve verified • I am Account Holder and Admin. • All agreements are accepted. • App creation, bundle ID registration, and certificate management work normally. • I’ve removed/re-added my Apple ID in Xcode and cleared all Xcode-* tokens from Keychain. • Test apps in clean Git repos reproduce the same error. Support I have already opened Case ID 102769512657 with Apple Developer Support, but I’m posting here in case others have seen this issue or know of additional steps to confirm the provisioning state.

After a break using AWS Macs for CI we are willing to give Xcode cloud another go. Unfortunately we are unable to complete the "Grant Access to your Source Code" step. We tried multiple accounts including maintainer, owner and admin. We tried from multiple Macs and versions of macOS. "Connecting Xcode Cloud with your source control provider was incomplete. 503 Service Unavailable. Please ensure that your repository is available and accepting connections."

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

During testing, we encountered an issue where when entering the game and starting audio playback, if I force-kill the app directly (by swiping up the app in the app switcher, rather than switching to the background first before killing it), a system crash prompt dialog appears after the app is killed. We conducted numerous tests to troubleshoot the problem and found that this issue only occurs with our own TestFlight account. When we uploaded our app to another TestFlight account for testing, we were unable to reproduce this problem.

Hello, We are experiencing a persistent issue where macOS builds in Xcode Cloud consistently hang at the Archive stage. The build itself completes successfully, but no artifacts appear, and it seems the build gets stuck during artifact upload. These builds remain in this state for several days (currently 3 days and counting) not failing, but never finishing. We opened a support ticket (102756662562), but we have not received any response yet. We rely on Xcode Cloud for our entire CI/CD pipeline, and at the moment our workflow is completely blocked because of this issue. Has anyone encountered something similar or found a workaround? Thank you.

We want to replace our CI/CD pipelines in Azure DevOps with Xcode Cloud and are currently facing a critical hurdle. For some time now, we’ve observed that the PoC pipelines in Xcode Cloud are having major issues cloning our repositories stored on our Bitbucket Server. More and more pipeline runs are timing out because Xcode Cloud cannot receive the data. Today I spoke with our network team to check whether we might have an issue on our side affecting access to the repository, but we couldn’t find any problems. Cloning the repository to an external machine only takes 30 seconds, so the host’s bandwidth doesn’t seem to be the problem. However, our network specialists did discover one message: Significance: Request abnormal event: high total time Connection abnormal event: client has a slow receive rate If this is the bottleneck in the system, we may ultimately have to stay with Azure DevOps and Fastlane in order to continue providing our product teams with reliable builds. I look forward to your feedback and thank you in advance. Maik

Hello, While setting up Xcode Cloud using Bitbucket, I encountered an issue with Source Control and providing access to the repository. The problem most likely stems from the fact that Bitbucket has updated its policy, and the use of app passwords is no longer available (at least for new ones). However, in Xcode → Settings → Source Control, the login flow still requires an app password, which makes it impossible to authenticate using the new API tokens. Attempting to authenticate via SSH also does not resolve the issue. After connecting to GitHub, I also tried to connect through the web version, but I'm getting the same message: "Bitbucket Cloud installation was incomplete." I received this same message when I first tried to connect through Xcode. This problem does not occur when connecting to GitHub. I would appreciate receiving feedback from the Apple team on this issue. System Info: Xcode: 16.2 (latest from App Store) macOS: Sequoia 15.1