I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 Command exited with non-zero exit-code: 70 The same pattern repeats for ad-hoc and app-store distribution exports. What I've verified: The build itself compiles successfully (all modules compile, command executed successfully) No code changes were made that would affect signing The workflow is configured with automatic signing managed by Xcode Cloud Post-action is set to TestFlight External Testing Additional constraint — Remote Mac: I'm building on a Remote Mac, which adds complexity to code signing and keychain access. The Remote Mac environment has known limitations with certificate and provisioning profile management compared to a local Mac. This may be a contributing factor to the export failures. This appears to be an issue with how Xcode Cloud is handling the Apple Distribution and Apple Development signing certificates during the export phase, not a build compilation issue. Has anyone encountered this recently, or is there a known issue with Xcode Cloud's managed signing on Remote Mac environments? Any guidance on resolving exit code 70 during the export step would be greatly appreciated.

Hello, I am posting here because my Apple Developer Program membership is currently stuck in a state that I cannot resolve through the available self-service options, and I have not received a response to my compliance reply or Developer Support case. Timeline: • January 6, 2026 — I purchased my Apple Developer Program membership for a one-year term and received an Apple invoice. • September 22, 2026 — Apple Developer Relations notified me that my membership had been suspended pending a compliance review concerning possible digital-asset activities. • September 23, 2026 — I replied to Apple Developer Relations and provided the requested written confirmation that I do not provide digital-asset or cryptocurrency financial services. I also stated that I am enrolled as an individual and do not operate a registered company or other business entity. I have received no further response or request for additional documentation. My account is now in a contradictory state: • App Store Connect reports “Developer Program Membership Expired” and states that my apps have been removed from the App Store. • My membership was purchased on January 6, 2026 for a one-year term, so it should still be within its paid membership period. • developer.apple.com/account shows “Join the Apple Developer Program.” • If I attempt to enroll, Apple displays: “Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership.” Therefore, I cannot access my existing paid membership, restore Developer Program access, or enroll again. I contacted Apple Developer Support regarding this issue. Developer Support Case ID: 102975269103 The case remains unresolved, and phone support for this case currently shows: “Phone support is currently unavailable. Due to high call volumes, phone support is temporarily unavailable.” I am ready to provide immediately, through an appropriate secure Apple verification channel: • government-issued identification; • proof of address; • my Apple Developer Program purchase invoice; • information about my applications and their functionality; or • any other documentation required to complete the compliance review. I am not asking for a workaround or a new enrollment. I need the existing paid membership and compliance case to be reviewed by the appropriate Apple Developer Program Membership / Compliance team. Could an Apple Developer Relations representative or forum moderator please help route or escalate Case 102975269103 to the appropriate team, or advise whether there is any additional verification or documentation currently required from me? My applications have already been removed from the App Store while this remains unresolved, so the issue is actively affecting distribution. Thank you.

I am seeing Xcode Cloud reuse and reassign a single ciProduct when onboarding multiple iOS app targets from one Xcode project. Each target has its own bundle ID, PBXNativeTarget, product reference, and shared scheme. Environment: Xcode 26.6 (17F113) macOS Tahoe 26.5.2 GitHub repository connected to Xcode Cloud Project: pilot-ios/Airtap.xcodeproj Targets / shared schemes: PocketPilot.ai DEV1 — ai.airtap.dev1 PocketPilot.ai DEV2 — ai.airtap.dev2 PocketPilot.ai DEV3 — ai.airtap.dev3 PocketPilot.ai DEV4 — ai.airtap.dev4 PocketPilot.ai QA1 — ai.airtap.qa1 PocketPilot.ai QA3 — ai.airtap.qa3 Every entry above is a separate PBXNativeTarget with a distinct productReference. Each shared scheme is stored under Airtap.xcodeproj/xcshareddata/xcschemes and builds its corresponding target. QA1 and QA3 were onboarded earlier and received independent Xcode Cloud products as expected. Reproduction: In Xcode, open Xcode Cloud Reports and choose Create Workflow. Select target PocketPilot.ai DEV1 and create an archive workflow using scheme PocketPilot.ai DEV1. DEV1 appears under the correct App Store Connect app. Create another workflow for target PocketPilot.ai DEV2 using scheme PocketPilot.ai DEV2. DEV1 disappears as a separate Xcode Cloud product. Both the DEV1 and DEV2 workflows now appear under the DEV2 App Store Connect app. The App Store Connect API confirms this is not only an Xcode UI or cache issue: Before DEV2 onboarding, ciProduct F048BF00-CECF-4926-84DB-D3474CB030A9 was related to bundle ID ai.airtap.dev1. After DEV2 onboarding, that same ciProduct ID became related to bundle ID ai.airtap.dev2. The product now contains both workflows: PocketPilot DEV1 Archive / scheme PocketPilot.ai DEV1 PocketPilot DEV2 Archive / scheme PocketPilot.ai DEV2 No build was started, and both workflows are currently disabled. Expected behavior: Because every target has a different bundle ID, Xcode should create a separate Xcode Cloud product for each target, as described in the Xcode Cloud onboarding documentation. Actual behavior: The newest onboarding changes the existing ciProduct-to-App Store Connect app relationship instead of creating a new ciProduct. This moves all earlier workflows to the newest app. The public App Store Connect API cannot repair this because it supports reading and deleting ciProducts, but not creating one; ciWorkflows can only be created under an existing ciProduct. I also encountered an Xcode crash while adding another product. The crash stack included XcodeCloudNavigableItemCoordinator.removeNavigableItem(for:) and IDENavigableItemCoordinator, which may be related to the product reassignment. I can provide the crash report in Feedback Assistant if needed. A recent forum thread reports the same high-level symptom: previously created workflows migrate to the newest app. In our case, the API relationship change above makes the backend reassignment directly observable. Is this a current Xcode Cloud onboarding/backend regression? Is there a supported workaround, or can Apple Support create or restore separate ciProducts for these bundle IDs?

Hello, I’m trying to create an iOS TestFlight build for an Expo/EAS app on Windows. The project is configured with: Expo SDK 57 EAS CLI 24.1.0 iOS bundle ID: com.i3radleyy.flooriq Apple Developer Program: active individual membership Apple Team ID: R7GLN64JYP The Bundle ID is registered in Apple Developer The app record exists in App Store Connect I am the Account Holder The Expo configuration command succeeds and reports the correct bundle ID. EAS project initialisation also succeeds. However, when running the production build, Apple authentication fails after the Apple ID and password are accepted: Authentication with Apple Developer Portal failed! Failed to set up credentials. iTunes service key is empty Error: build command failed. I have also tried: EAS_NO_VCS=1 EXPO_NO_KEYCHAIN=1 Git is not being used, and the project is being built from the correct app directory. The Apple Developer account and App Store Connect pages are accessible in the browser, and the Bundle ID is registered. Is this a known EAS/Apple authentication issue on Windows? Is there a recommended way to provide the Apple signing credentials or use an App Store Connect API key so that EAS can create the iOS distribution certificate and provisioning profile? Thank you.

My individual enrollment in the Apple Developer Program is being denied, and nobody can tell me why. Both the website and the Apple Developer app refuse the enrollment. I contacted Developer Support and got the same template twice: "For one or more reasons, your enrollment couldn't be completed. We can't continue with your enrollment at this time." No reason. No hint of what to fix. When I asked for specifics, the support agents themselves seemed not to know what the problem is. I genuinely don't understand what is wrong. I'm an individual developer with finished projects waiting for release. I need this account to work, and I need a real answer, not a template. I'm ready to verify my identity with any document Apple needs - passport, ID, proof of address, anything. Could someone from Apple Developer Support with access to the actual account status please look at case 102915311314 and tell me either what to fix, or that the block is permanent so I can stop wasting time?

My developer account identity has a red 'x' next to it like other users have stated. It looked as though a tech helped them correct it. I have been requesting support via email for over 10 days on this and am still waiting for assistance. When I sign into App Store Connect, I can see both of my apps I have registered. My apple developer account at the top tells me I need to enroll in a program and can click to enroll but then will tell me I cannot enroll. I can see myself as the account holder and admin in the user identities. I also have the developer certificate in my keychain.

Apple M2 MacBook Pro 2022 (24GB/1TB) macOS 27.0 Xcode 27.0 Xcode hangs every time I try to open any xib file. Didn't face this issue in previous versions. I have attached some initial part of the report here, I have reported the problem via xcode too. Xcode hang.txt

I am a developer from Pakistan, and I have been facing an issue with my Apple Developer Program enrollment for the past few days. I submitted my enrollment, and after some time it was approved. I then received the option to complete the payment. However, I have been unable to complete the payment. I have tried my Payoneer card as well as cards from several local banks in Pakistan, but I receive the same error every time: “Payment Authorization failed on card ****. Please verify your information and try again, or try another payment method.” Unfortunately, none of the other available payment methods are working either. I would appreciate it if anyone help me,

what can i do?

The live Device Hub window shows my app's colors differently from a physical iPhone. The pixel values themselves are correct: a screenshot taken in Device Hub has the same colors as the device. Only the live window looks different — [e.g. more washed out / more saturated]. It happens in every project I've tried, including ones that use only plain sRGB colors and sRGB image assets, so it doesn't look app-specific. Setup Xcode 27.0 (27A266a) MacBook Pro, Apple M4 Max Built-in Liquid Retina XDR display (default "Color LCD" profile) and an external BenQ PD2705UA Simulated devices: iPhone 13 mini (iOS 26.1) and iPhone 14 (iOS 26.5) What I've ruled out Same result on both the built-in display and the external monitor True Tone and Night Shift are off on the Mac The simulated device is in light mode, with Increase Contrast, Invert Colors and Grayscale off The Device Hub screenshot matches the physical iPhone, so the rendered pixels are correct Questions Is the Device Hub window color-managed for the Mac's display, or is this expected behavior? Is there a setting to make the live window show accurate colors?

I am using Coding Intelligence, powered by Claude, in the first production release of Xcode 27.0 (in MacOS 26.7). Initially it was working ok. But after less than a day, it now crashes every time it needs to ask for permission for any shell command. And each time I restart things, it burns through a ton of tokens. ☹️ Any suggestions? (I'll file a bug report right now…)

Hello, I'm requesting a status update on our Apple Developer Program Organization enrollment. Enrollment ID: 7A7WRTQW97 Organization: SWISS KEY TRADING AG (Switzerland, Commercial Register No. CHE-455.888.722) Enrolled as: Organization Applicant role: IT Responsible, enrolling on behalf of the company We initially received a document verification rejection citing (1) a photo ID mismatch and (2) an employment verification letter missing official letterhead and signature. We have since resubmitted corrected documentation addressing both points. The enrollment has been showing "Your enrollment is being processed" since 08.07.26. Could someone let us know if any further information is needed, or confirm expected next steps ? Thanks in advance and have a great day !

My Apps — 2weeks with no review or response It has now been approximately 14 days since my latest submission, and I still have not received any review result, message, or request for additional information. I completely understand that App Review may take time, especially when an app has previously received rejections and requires additional review. However, in my case, I have already responded to the concerns raised in the previous reviews, clarified the misunderstood features, and made further changes to the app before submitting the latest build. The situation is becoming difficult to understand because the app was initially rejected for one set of concerns, then after clarification it was rejected under spam, and after addressing those concerns and submitting a redesigned/rebuilt version, the latest submission has now remained without any response for about a week. Could someone from the Apple Developer Relations/App Review team please advise on what I should do next? I am not asking for the app to bypass the review process. I simply want to know whether: The submission is still actively waiting for review Additional information is required from me There is an issue with my App Store account or submission I should take any further action before submitting another build This is a new organization account, and I want to make sure I am following Apple's guidelines correctly rather than repeatedly submitting builds without understanding what is expected. If anyone from Apple can take a look at the case or advise on the appropriate escalation path, I would really appreciate it. App ID / Case details can be provided privately if re quired. Thank you.

My Apple Developer Program enrollment as an Individual has been declined. I have already contacted Apple Developer Support and also spoke with support by phone. I was informed only that the enrollment was declined, but no reason was provided and I was not given any way to correct the issue or retry the enrollment. I am not asking Apple to bypass any eligibility or identity-verification requirements. I am requesting: A manual review of my Apple Developer Program eligibility. Confirmation whether my Apple Account has an enrollment or identity-verification restriction. If possible, removal/reset of the declined enrollment state so that I can complete identity verification again. An alternative identity-verification method if the previous verification could not be completed successfully. Guidance on any documentation Apple requires from me. I am fully prepared to provide my Saudi government-issued identification, passport, proof of address, payment information, or any other required documentation through an official secure Apple channel. Support Case ID: 20000132221925 Country/Region: Saudi Arabia I would appreciate it if Apple Developer Support could review or escalate this case to the appropriate Enrollment team.

My Apple Developer Program enrollment has been stuck at: “Your enrollment is being processed.” Enrollment ID: WCW6K8M5M3 It has now been in this state for several weeks. I have contacted Apple Developer Support multiple times but have not received a substantive response. The Developer Support Contact Us page does not currently provide a “Request a Call” option for my account/region, so I have no way to speak to anyone. There is no outstanding action shown in my Developer account, and I am ready to provide any identity, organization, D-U-N-S, signing-authority or other verification documents required. Could Apple Developer Program Support please escalate the enrollment for manual review or advise whether anything is outstanding?

Good afternoon! How can I solve the problem with payment? I have placed orders to pay for my developer account, but the payments have not been confirmed.

Client error - operationID: onboardTarget, operationInput: Input(path: XcodeCloudAPI.Operations.onboardTarget.Input.Path(teamId: ""), query: XcodeCloudAPI.Operations.onboardTarget.Input.Query(), headers: XcodeCloudAPI.Operations.onboardTarget.Input.Headers(), cookies: XcodeCloudAPI.Operations.onboardTarget.Input.Cookies(), body: XcodeCloudAPI.Operations.onboardTarget.Input.Body.json(XcodeCloudAPI.Components.Schemas.TargetOnboardingRequest(projectName: "Runner", targetName: "Runner", targetType: app, repoHandle: XcodeCloudAPI.Components.Schemas.RepoHandle(host: Optional("bitbucket.org"), provider: bitbucket, repoId: ""), deviceFamilies: Optional([iPhone, iPad]), deploymentTarget: Optional("15.0"), productCreationEntryPoint: xcode_product_menu))), request: path: /teams/onboard-target, query: , method: HTTPMethod(value: OpenAPIRuntime.HTTPMethod.(unknown context at $14c94d79c).OpenAPIHTTPMethod.POST), header fields: [accept: application/json, content-type: application/json; charset=utf-8], body (prefix): { "deployment_target" : "15.0", "device_families" : [ "iPhone", "iPad" ], "product_creation_entry_point" : "xcode_product_menu", "project_name" : "Runner", "repo_handle" : { "host" : "bitbucket.org", "provider" : "bitbucket", , baseURL: https://appstoreconnect.apple.com/ci/api, response: , underlying error: The operation couldn’t be completed. (XcodeCloudCombineAPI.NetworkResponseError error 1.) Domain: OpenAPIRuntime.ClientError Code: 1 System Information: macOS Version 27.0 (Build 26A428)

I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only) I unpaired/removed the Watch in Xcode (Devices & Simulators). I did not unpair the Watch from the iPhone. Now: iPhone appears in Xcode and works normally for builds. Watch is still paired to the iPhone and works normally. Watch no longer appears anywhere in Xcode Devices & Simulators (no paired watch section, no watch run destination). What I’ve tried Reboots of Mac, iPhone, Watch (multiple times) Watch unlocked, awake; iPhone unlocked and close to Watch Verified Watch is paired and connected in iPhone Watch app Developer Mode enabled on iPhone and Watch Wi-Fi and Bluetooth ON (Mac/iPhone/Watch), tried toggling both Tried on home Wi-Fi and also with iPhone hotspot (same result) Resetting trust prompts / reconnecting iPhone via USB, re-trusting Mac Apple Watch: “Clear Trusted Computers” Xcode: removing/re-adding devices; clearing derived data; restarting Xcode Watch Developer networking test: Responsiveness = Medium (430 RPM) Questions 1. Is this a known issue/regression with Xcode 26.2 + watchOS 26.2 tunneling (CoreDevice / devicectl)? 2. Is there an Apple-supported way to force Xcode to re-discover a paired Watch after it was removed from Xcode Devices & Simulators (without unpairing the Watch from the iPhone)? 3. Any recommended logs or diagnostic steps I should collect (Console logs, sysdiagnose, specific Xcode/CoreDevice logs) to include in a Feedback report? If helpful, I can provide the full error text from Xcode’s Devices window and any logs you recommend. Thank you in advance,

I file a lot of bug reports. I also ask a lot of third-party developers to file bug reports about problems they see. This post is my attempt at collecting together some hints and tips about Apple’s bug reporting process. To file a bug report, use Feedback Assistant. To file an enhancement request (ER), use Feedback Assistant. In the “What type of issue are you reporting?” popup, choose Suggestion. If you’re filing a bug against an API, choose Developer Technologies & Resources at the top level. The technologies popup should then list familiar items, from Accelerate Framework to XPC. If you can’t find the correct item, select “Something else not on this list”. Feedback Assistant is both a website and an app. For details on how to access the app, see Opening the app on the Developer > Bug Reporting page. For lots of great hints and tips about filing bugs, see File effective bug reports. I may repeat some of the info covered by that article, but only where I think it’s particularly important. After filing a bug report, please include the bug number in your DevForums post. Feedback Assistant shows the bug number in both the bug list and the bug detail view. Bug numbers start with FB and continue with a sequence of digits. For example, a recent bug report posted here on DevForums was FB11357055. Including the FB prefix avoids any confusion as to what type of bug number this is. Occasionally you’ll see other types of bug numbers. In release notes they are just in parens, so (99071807), and in DTS documents they have an r. prefix, so (r. 99071807). These are Radar numbers. Radar is the internal bug system here at Apple. Other developers can’t see your bug report. However, posting the bug number is still important for a couple of reasons: It allows Apple folks to quickly track down your issue. If another developer wants to file a related bug, they can reference your bug number in their bug report. You can share bug reports with other members of your team. For details on how to do that, see Collaborating with your team on the Developer > Bug Reporting page. Otherwise you can’t see a bug report filed by another developer, or one filed internally at Apple. One option here is to file your own bug and request that it be marked as a duplicate of the original bug. You’ll then be notified when the original bug is closed. The File effective bug reports article discusses the importance of including a sysdiagnose log with your bug report. I have a few additional tips: Include a sysdiagnose log from the machine that’s having the problem. Sometimes I see folks with an iOS problem include a sysdiagnose log for their development Mac )-: Include a sysdiagnose log even if you attach a test project that reproduces the problem. The contents of the log help with screening, making sure that your bug gets to the right person quickly. And that person will be very grateful to have your test project! If multiple machines are involved — for example, you’re reporting a Handoff problem — include a sysdiagnose log from each machine. Trigger the sysdiagnose log as soon as possible after you see the problem. The sooner you trigger the log, the more likely it is to capture relevant info. If the problem is hard to reproduce, see Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem for hints on how to capture an actionable sysdiagnose log. If you install a debug profile, install it before you reproduce the problem. These profiles typically enable more logging, and you want that logging to be active at the time of the problem. Most profiles activate immediately but some require that you restart. Follow the instructions that came with the profile. When reproducing the problem, make a rough note of the time and include that in your bug report. This doesn’t have to be super precise. Just note down the time, with seconds, shortly after you reproduce the problem. If the bug involves a crash, reproduce the crash outside of Xcode and then take your sysdiagnose log. This means running your code as the user would, so running an app from the Finder on macOS, running an app from the Home screen on iOS, and so on. If you reproduce the crash inside Xcode, the Xcode debugger catches the crash and prevents the system from generating a crash report to include in the sysdiagnose log. File focused bug reports. Imagine you’re seeing two problems, A and B, related to the same API. Don’t file a single bug that covers both A and B. Rather, file separate bugs for A and B. Feel free to reference your A bug in your B bug, and vice versa. Finally, some personal notes: DevForums is not an official support channel. Mentioning a problem here is not the same as filing a bug about it. That’s true even if you’re discussing your issue with an Apple person. Apple is a big company, and it’s very unlikely that the person you’re talking to is directly responsible for fixing your bug. Historically I used to post a lot of Radar links, of the forms rdar:nnn, where nnn is the bug number. I no longer use these links because I’ve found that they confuses folks. They click the link and wonder why it does nothing. If you post an FB number here, DevForums automatically turns it into a link. However, that link is only useful to you. Other folks can’t access the bug via that link. I’ve filed a bug against DevForums requesting that it only generate this link for the bug’s originator (r. 92946014). In the meantime, I work around this by putting FB numbers in code style, which disables this link generation. If you want to share bug information outside of DevForums, one popular option is Open Radar (https://openradar.appspot.com/). Apple uses a lot of open source and many open source projects maintain their own bug tracker. Two big examples are Swift and WebKit. If your bug originates in such an open source project, consider filing it in the project’s bug tracker. You can then go on to submit a pull request with the fix (-: If your bug originates in an Apple open source project that doesn’t have its own bug tracker, file you bug in Feedback Assistant and select Developer Tools & Resources > Open Source. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Revision History 2026-09-28 Expanded the comments on open source bug reporting. 2026-04-20 Added ER as a shortcut for enhancement request. 2025-08-07 Updated “Developer Technologies & SDKs” to “Developer Technologies & Resources”. 2024-03-07 Made minor editorial changes. 2023-10-26 Added a link to Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Added a recommendation to file focused bug reports. 2023-06-28 Updated the advice on how to file an API-level bug based on recent changes to Feedback Assistant. Corrected some link titles. 2023-03-21 Added a bunch of bullets to the personal notes section. 2023-03-13 Extended the discussion of seeing other folks’ bugs to make it clear that you can’t see bugs filed internally at Apple. 2022-12-13 Added advice about the “Something else not on this list” option. 2022-09-01 Added a personal notes section at the end. Added a new bullet in the sysdiagnose section about running your app outside of Xcode. Made other minor editorial changes. 2022-08-29 Added a note about filing duplicate bugs. 2022-08-24 First posted.

I feel I'm missing something really obvious, but how are files copied to simulators in Device Hub now? From my MacOS Finder, there's no share with simulator option and drag and drop is ignored. What am I missing?