I’m packaging a Safari Web Extension using the web-based Safari Web Extension Packager in App Store Connect. The ZIP uploads successfully, the manifest is accepted, and the Packager automatically creates the related Extension identifier. However, every build fails during export with: Exporting for App Store Distribution failed. Please download the logs artifact for more information. It also shows: Exporting for Development Distribution failed. Please download the logs artifact for more information. There is no Logs, Artifacts, or Download button on the build or issue page. To isolate the problem, I tested: Manifest V2 and Manifest V3 A minimal extension containing only HTML and icons No JavaScript, permissions, host permissions, APIs, or external dependencies A completely new App Store Connect app A new explicit Bundle ID A name-matched extension ZIP Multiple version and build numbers Every test produced exactly the same export errors. The App Store Connect agreement is active, and the Account Holder has access to cloud-managed distribution certificates. Because even a clean minimal extension and a newly created app fail identically, this appears to happen during cloud signing, provisioning, or archive export—not while parsing the extension. Questions: How can I download the logs artifact requested by the error when the Packager interface does not provide it? Can Apple confirm whether the web-based Packager currently has an export or automatic-signing issue? Is there any required certificate, provisioning profile, App ID configuration, or account permission that the Packager does not create automatically?

For the last 2 months I have been submitting the first iOS builds of my app “Zema Kirar”. However Appstore connect wrongly rejects it claiming it was built bu a BETA version of xcode and / or MacOS. My Dev Environment I am Running macOS Tahoe 26.6.2, and Xcode 26.6 (Build 17F113). Both are the ”current” latest public (GM) versions required by apple. Steps to reproduce: Xcode cloud build/ and transporter upload completes > I select the build > click save > click on Submit. Appstore connect shows error: Unable to add for Review. The items below are required to start the review process: New apps and app updates must be built with the latest public (GM) versions of Xcode, and the iOS, macOS, watchOS, and tvOS SDK. Apps built with the beta versions aren’t allowed.

I'm angry — Apple’s support has been awful. I’ve been trying to get help from Apple for two weeks. Their replies feel canned and automated (they even sign with a first name only), and they only provide basic information that doesn’t address the problem. You put in a response and then a week later, some canned response comes back from someone with a single name (Lisenga) I’m now faced with two unacceptable options: stop supporting Apple Safari users or delete my account and start over. Both options punish my users. For a multi-billion-dollar company, Apple’s support is shockingly limited. I ran this issue past ChatGPT Codex, and it confirmed that this is something only Apple can fix. Recent Apple Developer Forum posts describe Xcode Cloud / App Store Connect requests returning null responses because backend team permissions were broken. One post even referenced a case where Apple confirmed the only remedy was an internal fix on their side. To be clear: I am NOT using Xcode. I’ll say it again in case it was missed: I am not using Xcode. Here’s what happens: In App Store Connect, when I click the Xcode Cloud link it prompts me to “upload archive file.” When I upload, I immediately get “Failed to Fetch.” This happens in Safari, Chrome, and Firefox, in normal and private windows. It happens on a different computer 400 miles away as well. My suspicion is this: if a build is created before agreeing to the developer agreements, and the agreements are answered afterward, the system goes out of sync and breaks — a problem that only Apple can resolve. How do you actually talk to a real human at Apple??

Hi Apple DTS and community, My developer account's app has been granted the Default Mail App managed capability (com.apple.developer.mail-client). The capability works for Development and App Store Connect distribution, but it is not enabled for Ad Hoc distribution. This prevents us from using our Xcode Cloud “Archive & TestFlight” workflow: The archive succeeds. Development and App Store Connect exports succeed. Xcode Cloud then automatically attempts an Ad Hoc export. The Ad Hoc export fails, causing the entire archive action to fail and the TestFlight post-action to be skipped. The export log reports: Entitlement com.apple.developer.mail-client not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file. We have reproduced this in two consecutive Xcode Cloud runs. We also confirmed that: The App ID has the Default Mail App capability enabled. The entitlement is present and correctly spelled in the app’s entitlements file. The App ID’s provisioning support lists Development and App Store Connect, but not Ad Hoc. Our Xcode Cloud workflow does not expose an option to disable the automatically attempted Ad Hoc export. This appears to match these previous reports: https://developer.apple.com/forums/thread/774506 — a DTS engineer enabled Ad Hoc support for the entitlement, after which the developer confirmed the issue was resolved. https://developer.apple.com/forums/thread/800072 — DTS confirmed that the Ad Hoc distribution option must be enabled for the Default Mail App managed capability. We also opened an Apple Developer Support case (102945477410). Developer Support directed us to the forums and indicated that this issue would need to be handled by DTS engineers. I can provide our Team ID, Developer Support case number, Xcode Cloud run identifiers, and any other account details privately if needed. Thank you!

I use Xcode Cloud with my Github repo to automatically trigger workloads any time I create a new PR or make changes to the PR. This has been working for a few years now but this week it stopped working from one day to the next with no explanation. If I trigger the workflow manually via Builds > Start Build > my PR build workflow, and selecting my Pull Request from the list. This means that Xcode Cloud has access to my Github account, it's not an auth issue or anything like that. The only thing that doesnt work is the auto detection of when a PR is created or updated.

所请求的app不可用或者不存在

Hi, I am curious about why don't you provide an arm64 version of homebrew to your developers. To install arm64 homebrew in xcodecloud requires to compile packages from source. After 35 minutes still running ci_scripts/ci_post_clone.sh to install some packages: arm-brew install coreutils arm-brew install bash awk grep cat arm-brew install make arm-brew install gnu-tar gzip bzip2 xz arm-brew install automake autoconf m4 libtool arm-brew install llvm arm-brew install perl perl-build pod2man python3 meson ninja sqlite libtasn1 openssl libiconv gettext Further I need continues integration to build universal binaries and libraries. Maybe run the integration test suite, too. I think xcodecloud should provide arm64 and x86_64 versions of homebrew. Please consider this change.

I was previously able to test my app on Xcode 27 / iOS 27 by setting the Xcode Version to "Latest beta or release". I needed this to test PrivateCloudCompute on my apps in TestFlight. As of a few days ago this stopped working and only shows the stable 26 release, which removes PCC and my ability to test it. Am I doing something wrong? I didnt change any settings, I just noticed PCC wasnt working, checked the workflow and noticed that it no longer shows Xcode 27.

My app has been sitting in Beta App Review for an extended period with no update. I opened a support ticket through the developer contact form and never received a response. I also called Apple Support through the consumer line, but they weren't able to access developer/App Review case details and redirected me back to the same channel that already isn't responding. Has anyone else run into a review request that stalls with no reviewer feedback and no response to a filed ticket? Looking for: Any way to escalate beyond the standard contact form Typical wait times others have seen for a stuck Beta App Review before it's worth re-submitting a new build vs. waiting Whether there's a different queue/contact specifically for TestFlight (as opposed to full App Store review) Appreciate any pointers.

I've been getting intermittent failures on Xcode code compiling my app on multiple platforms because it fails to compile a metal shader. The Metal Toolchain was not installed and could not compile the Metal source files. Download the Metal Toolchain from Xcode > Settings > Components and try again. Sometimes if I re-run it, it works fine. Then I'll run it again, and it will fail. If you tell me to file a feedback, please tell me what information would be useful and actionable, because this is all I have.

Hi, My full build with all dependencies takes approximately 2 hours plus about 1 hour to run integration tests. Sorry 120 minutes build timeout is too short. Is there a way to adjust build timeouts? by Joël

Over the last 24 hours, App Store Connect has been performing very slowly, sometimes showing Bad Gateway and sometimes only loading tab views without any content. I use the word "flakiness" because it's happening intermittently. It took over an hour for Xcode Cloud builds to be triggered yesterday, and during that time it was not possible to start builds manually because the github refs weren't refreshing. Today I was unable to load the Users & Access > Integrations > Webhooks page. Since, I've logged out and back in, and now I cannot load any of my apps even though my development team correctly shows with my account info in the top right. Is anyone else experiencing these symptoms? I see nothing on the System Status page other than an outage with Apple Podcasts Connect.

Xcode Cloud builds fail at the export archive step. The critical log shows: Account "Session Proxy Provider": Unable to authenticate with App Store Connect Error Domain=DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)" And in DVTITunesSoftwareService.log: App Store Connect response failed with unknown failure; response (null); error (null) error: DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy Environment: Xcode Cloud, iOS app, team type Individual (S43L28SVX2) What I have ruled out: Regenerated all DISTRIBUTION_MANAGED certificates (per thread 744683) — portal API is reachable, certs issued successfully Removed an obsolete App Groups entitlement that was causing a secondary error — that error is now gone All agreements accepted, no pending legal items Failure persists across multiple builds with identical symptoms The developer portal API responds correctly. The failure is isolated to the App Store Connect store configuration endpoint specifically, where the proxy returns response (null) — no HTTP response at all. This appears identical to thread https://developer.apple.com/forums/thread/810658 where Apple confirmed the root cause was a backend API permission issue for the team requiring an Apple-side fix. Support case 102857550486 was opened but redirected to admin support without technical investigation. Has anyone else hit this recently, or can an Apple engineer look at the backend state for this team?

Hello, Our Test Flight internal user limit is stuck at 100/100 users and I couldn't reduce the number and free seats no matter what I tried. What I tried so far: Reduced number of people in Users and Access to 98 (excluding customer support which does not count for internal users anyway) Reduced number of internal testers in the only internal Test Flight group to 38 Testers. Reduced number of all testers for the app to 97 (including external test only users) Made sure that deleted users from Users and Access list have no emails in the internal test group. More importantly, no matter how many users I delete from both Users and Access or only internal tester group, the limit always shows 100/100. I appreciate any help. This feels like a bug. I am unable to contact Apple support, I waited for almost an hour on the phone but nothing. I waited for days for potential caches to clear up, still no luck.

I'm trying to build an Xcode Cloud workflow, but I keep getting this error. At first it just said I had to accept a license agreement, which I did, but it still didn't work after. I had recently added a new branch to the connected GitHub repository and committed to it so that I can have a beta branch separate from the main one. The only error that happens is when archiving. I am using Xcode 27 beta.

I added a workflow and it seemed to work fine so lets add them all ! I added a second workflow and it seems to see the repository but not the branches in the repository. I have googled and even asked AI. Checked and it's installed with all repo access on Github Removing the repo .. adding it back Deleting the workflow and adding it back Adding the workflow from the browser Adding the workflow from XCode Nothing seems to work, but the first one I created works. Is there paid support for Xcode Cloud ? I s there a version control that works better with Xcode Cloud? Any suggestions are appreciated.

Hello App Review Team, My app, SUB PREMIUM TV (Apple ID: 6769972609, Version 1.0), has been in “Waiting for Review” status for several days. I would like to confirm whether there is any issue with my submission or if any additional information is needed from me. Thank you for your time and assistance. Best regards, Babucarr Ngum

my app build is stuck on preprocessing build from one hour

Is there a way for me to set CFBundleVersion before TestFlight and/or Notarization actions occur and have it stick? When I've tried doing this with ci_scripts or Script Phases, the system overwrites CFBundleVersion with the Xcode Cloud build number before publishing to TestFlight or notarizing. We have a rather odd setup where we have two apps which are built from the same source & historically have used identical build numbers. So e.g. App A build 3 is built from the same commit as App B build 3. We have a bunch of tooling & processes which assume this, but it's really tough to achieve on Xcode Cloud because the build numbers for two different projects get out of sync really quickly.

This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.