I can't enable Xcode Cloud for my app. Integrate > Xcode Cloud > Create Workflow is greyed out in Xcode. Environment: macOS: 27 beta (paired with iOS 27 beta on device) Xcode: 27 beta (only version that opens on this macOS) Xcode 26.6 (stable) fails to launch with: "This version of Xcode is not supported by this version of macOS" I am the Account Holder on my team (confirmed in Users and Access) What I've tried: Signed out and back into Xcode with my Apple ID Confirmed Team is set correctly in Signing & Capabilities Restarted Xcode App Store Connect also rejects my build upload with: "This build uses a beta version of Xcode and can't be submitted. Be sure to use the latest Xcode or Xcode GM seed available in News and Updates." Is there a way to run an Xcode Cloud workflow with Xcode 26.6 as the build environment without having 26.6 installed locally? Or is Create Workflow expected to be disabled while on macOS beta?

My organisation enrolment was promoted by Developer Support and I've signed the Program License Agreement. The only remaining step is paying the £79 membership fee, and the payment fails every time. The error on the Apple checkout page is: "Your payment authorisation failed on card ···XXXX. Please verify your information and try again, or try another payment method." The key detail: I've spoken to my bank and they have no record of a declined transaction and no record of any authorisation request arriving. So this doesn't appear to be an issuer decline — it looks like the request is failing before it reaches the card. What I've already ruled out: The Program License Agreement is signed, confirmed by email. The billing address on the checkout form matches the address registered to the card. The card is a UK credit card from a high-street bank, well within its limit and not expired. The bank has confirmed no block, no fraud flag, and nothing arriving at their end. Apple Pay appears on the payment page but shows "Items in your order are not eligible for this payment method", so card is the only available route. Three attempts, identical result each time. Questions for anyone who's hit this: Has anyone had an enrolment payment fail where the issuer confirmed no authorisation request was ever received? What turned out to be the cause? Does removing the saved card from the Apple Account and entering the details fresh make a difference, or does the checkout keep using the stored record either way? Is this a known issue with organisation enrolments specifically, as opposed to individual ones? Do repeated failed attempts risk anything on the enrolment itself? Mine has already taken several weeks to reach this point and I don't want to jeopardise it. Thanks for any pointers.

What is going on with Apple App Review??? for a week they are not responding, didn't even start reviewing my app which means that I can't even get it tested with external developers. This is a shockingly bad service from a team that is usually reasonably quick. Does anyone else experience these horrible wait times???

Attaching a C program which has a #include of the form #include <stdlib.h> strips the text after the #include literal. For example, consider the attached file in this current discussion, it should show up as: #include <stdlib.h> int main() { } but instead shows up as: #include int main() { } It looks like the presence of < and > characters causes this behaviour in the forum software. test.c.txt

Hello, I’m trying to complete enrollment in the Apple Developer Program, but the process is completely blocked at the identity verification step. Every time I submit my government-issued photo ID in the Apple Developer app, verification fails and I’m instructed to contact Apple Developer Support. I contacted Developer Support more than two weeks ago and case 102951828241 was opened. I received the initial acknowledgement, but I have still not received any substantive response or instructions on how to proceed, despite following up again. I also tried to use phone support, but the Developer Support page currently says that phone support is temporarily unavailable due to high call volumes. This is urgently blocking our Apple Developer Program enrollment and our ability to distribute our application. Could an Apple Developer Support representative please review or escalate case 102951828241 to the Program Enrollment / Identity Verification team, or let me know what I need to do to get the identity verification manually reviewed or reset? I can provide any additional identification or company documentation immediately through Apple’s secure process. Thank you.

In August my developer account was suspended. I still have no idea why. Zero rejected builds before that, not one. I sent a description of my projects and the standard documents they asked for. Then on 11 September the email arrived: "We approved your reinstatement request. You can now sign in to your account and access development resources." It's October now, and I still cannot sign in or create new certificates. App Store Connect has me as Account Holder and Admin, with "Access to Certificates, Identifiers & Profiles" ticked and everything in order. developer.apple.com hands me the "Need assistance with accessing your developer account?" form. Xcode goes further. It signs in, finds my team, lists my revoked certificates, and then, asked to make a new one, says: "You are not allowed to perform this operation. Please check with one of your Team Admins." I am the Team Admin. Since September I have sent more than ten emails and been passed between three different advisors. Each of them assures me the issue is being actively worked on. I have an active app with tens of thousands of monthly users. They aren't exactly thrilled that the Android version has already been updated while the iPhone one hasn't. I have no idea what I’ll do if I need to release a hotfix. Our team was ready to ship several more projects. Right now we are all staring at the wall, and I keep paying for the backend of an app we never got to release. And no, we cannot publish it from another account: that would count as getting around the suspension, which is against Apple's rules. Case 102950490774, escalated 18 September, currently with an operations team that needs nothing from me. Anyone been through this? What moved it?

We noticed some irregular activity associatedwith your vendor number 89341607 andhave paused your earnings payments whilewe investigate.Once our review is completewe'll determine if we can resume your payments. If you have any questions, contact us. Best regards, Apple Developer Relations Today I received this email. May I ask who has encountered the same issue and how long it will take to resolve?

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, It seems that starting Xcode 27, the logs from NetworkExtensions do not show up in the Xcode Console anymore. They still show in Console.app somehow. I have filed a bug report (FB24985332) about it, if you encounter the same issue, please upvote this so that the NetworkExtension team can fix this faster, thanks !

Has anyone successfully broken out of a multi-month enrollment loop with Apple Developer Support when hit with the generic "You may not sign up at this time" error? I have been trying to complete my Apple Developer Program enrollment since July 2026. The issue has spanned multiple support cases, numerous escalations, and repeated document submissions with zero resolution. Here is the timeline of what has taken place so far: July 2026: Began the verification process. Hit errors tied to device association and identity verification. Uploaded my government photo ID as requested by support advisors. The case was eventually escalated and merged into a new tracking thread. Early September 2026: Support requested my government photo ID a second time for account verification. I provided it immediately. September 18, 2026: Support performed an identity verification reset on my account so I could attempt the process fresh. Upon trying to enroll again, I immediately encountered the error: "You may not sign up at this time." September 21, 2026: A senior advisor informed me they were gathering internal diagnostic information regarding the enrollment failure. October 2, 2026: Sent another follow-up requesting a definitive status update, as the enrollment blocker is now entering its fourth month with no actionable next steps provided. At this stage, my identity documents have been submitted multiple times, resets have been attempted on Apple's end, and standard troubleshooting yields the exact same sign-up block.

I am stuck on an organization enrollment for over five weeks and I have run out of options on my side. Timeline: 21 August: company documents submitted and accepted by Developer Support (case 20000139491733). Genius Coach SRL, Romania. 27 August: order D005167219 created for the membership fee. Apple's website could not process the payment. My bank confirmed that no authorisation attempt from Apple ever reached them. The order was cancelled and my verified organization enrollment (ID LDPDVNFG3B) was removed with it. Developer Support advised me to re-enroll through the Apple Developer app, where alternative payment methods are available. In the app, Individual is the only entity type offered. There is no Organization option at any point in the flow. I reported this and supplied screenshots at Developer Support's request on 22 September. No reply since. I have written to Developer Support on 30 August, 6 September, 9 September and 22 September on case 20000151796483. The only reply I received was the request for screenshots. Telephone support is not offered for any subtopic in my region, so email is the only channel available to me. Has anyone enrolled as an organization from Romania recently, and if so, through which route? And is there any way to have a stalled enrollment case looked at when email support does not respond? My Android app is already published. The iOS release has been blocked for the entire period.

Since Xcode 27 GA, text entry from a UI test on a physical iOS 27 device delivers only the first 3–4 characters and then stops, while the call still returns success. Taps and scrolls are fine. The same tests pass on Xcode 27 beta 1. Filed as FB24932647. Broken: Xcode 27.0 (27A266a), 27.1 beta (27A9269), 27.2 beta 2 (27B5028f) Works: Xcode 27 beta 1 (27A5194q) Device: iPhone, iOS 27.0 (24A437) Repro. We drive it through WebDriverAgent. The failing step is XCTest's own event synthesis in testmanagerd, which is the same path XCUIElement.typeText goes through. Xcode 27.2 beta 2, run sudo xcodebuild -runFirstLaunch, reboot the device. Type subjectline into a plain UITextField. Read the field's value back. Expected subjectline. Actual sub or subj, in every one of 16 attempts. In a recipient-style field the fragment appears and is then erased, so nothing survives. 0 of 32 attempts completed. Device log, all within one second: testmanagerd Failed to load displays from CADisplay testmanagerd Failed to resolve displays. Defaulting to generic keyboard sender. testmanagerd Recap event action playback initiated UIKitCore hardwareKeyboardAttached = YES UIKitCore Moving from placement OnScreen to OffScreenDown UIKitCore Change to input view set: (empty) testmanagerd Recap event action playback completed testmanagerd can't resolve a display, so it falls back to a generic keyboard sender that registers a virtual HID keyboard. iOS then treats that as a hardware keyboard and dismisses the software keyboard while the text is still being typed. What changed. Comparing testmanagerd in the two DeveloperDiskImages: beta 1 derived the display from the app's identity (Computed display ID … from embeddedApplicationIdentifier … bundleID). GA removed that and added CADisplay enumeration with the generic fallback. That code is unchanged through 27.2 beta 2. This is not 181945323, which is marked fixed in 27.2 beta 2. That one needs Device Hub and clears on its own. Is anyone else seeing this on device? Is there a supported way to type on device under Xcode 27 GA, other than staying on beta 1?

I want to release an app under my company's name. From what I understand you need a DUNS number to verify your business. Because that takes about 30 days to be granted, I was thinking of releasing the app under my personal name and then moving it to the business account. Is that something I could do? Thanks

Hi, I am still unable to complete my Apple Developer Program enrollment. My Apple Developer Support case number is 102973696378. Developer Support previously informed me that the issue appeared to be caused by a mismatch between the trusted phone numbers on my Apple Account and my enrollment region. At that time, my account had both a Pakistan (+92) number and a UK (+44) number. Following Apple Support’s instructions, I removed the UK (+44) number several days ago. My Apple Account now only has my Pakistan (+92) trusted phone number, and I am enrolling using Pakistan as my country/region with my Pakistani identification details. However, I am still receiving the same error: “Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time.” Since the phone number mismatch has already been corrected, I believe the previous enrollment attempt or old region information may still be associated with my account. Could Apple Developer Support please manually reset or clear my Apple Developer Program enrollment so I can submit a fresh enrollment? Case ID: 102973696378 I would appreciate any help in getting the enrollment reset. Thank you.

Hi everyone, I’m running into a frustrating issue with the Apple Developer Program and would really appreciate any advice. I was charged $99 USD for the membership and received the confirmation email saying it would be processed within 2 business days. However, I still don’t have access to the membership, and nothing has been activated on my account. What makes it worse — I’ve already tried contacting Apple support multiple times via email, but I haven’t received any response at all. So right now I’m stuck: payment went through, but no membership and no support response. Has anyone faced this before? Did your membership eventually activate on its own? Is there any way to actually reach Apple support (chat, phone, anything that works)? Should I escalate this somehow or request a refund through my bank? Any advice would really help — I feel like I’m just shouting into the void at this point. Thanks 🙏

if i try to take a screen shot of the iPhone duo simulator with the screen shot button at the bottom of the device hub, it turns out all black. This only happens in the folded state.

Hello , We have discovered a potentially suspicious software signed with your Apple Developer Program Developer ID certificate. Public distribution of such applications could negatively impact users and is not a permitted use of the Apple Developer Program. Effective immediately, access to your Apple Developer Program membership has been disabled and certificates have been revoked. This is to ensure your assets are kept secure and protect users from the software that may qualify as malware or contain malicious, suspicious, or harmful code or components while you investigate the issue. To provide further details and request that your membership access be reinstated, contact us within 30 days. If you do not contact us within 30 days to resolve the matter, your Apple Developer Program membership will be terminated at that time and any apps distributed through your account will be removed from the App Store. Sincerely, Apple

Seems like there is an issue in Xcode 27 beta 4 & 5 where DeviceHub doesn't show iOS 16 devices or simulators. I've checked the filters to ensure I haven't hidden anything and the are listed in the Xcode destination dropdown.

is there a way to change where device hub saves its screenshots? i remember being able to change this in the old Simulator app. i tried holding down the option key while clicking the screenshot button, but that did nothing.

Hello team, We are currently evaluating the Declared Age Range API for supporting age-related regulatory requirements in our application, and we would appreciate some clarification regarding iOS version compatibility. Based on the documentation, we understand that newer age-related capabilities such as isEligibleForAgeFeatures and Regulatory Features are available only on newer iOS versions (for example, iOS 26.4+). We would like to clarify the following: Is the Declared Age Range API itself available only on iOS 26+ devices, or can age range information also be retrieved on earlier iOS versions? For users running iOS versions below 26, will the Declared Age Range API: Return age range information? Return a limited response? Be completely unavailable? Is our understanding correct that applications running on iOS versions earlier than iOS 26 cannot obtain age range information through the Declared Age Range API and therefore cannot determine whether age-related regulatory requirements apply? Are there any recommended fallback approaches for supporting age-verification or age-assurance requirements on devices running iOS versions below 26? Has anyone successfully implemented a solution that provides equivalent age-related signals or regulatory age-verification handling for users on earlier iOS versions? If so, are there any best practices or recommended approaches? Any clarification or guidance would be greatly appreciated. Thanks!