Overview

Hi, I submitted an Apple Developer Program organization enrollment for my LLC almost a month ago, but the enrollment status is still showing as “Pending.” Enrollment ID: X2M9S3DC5L I have contacted Apple Developer Support regarding the enrollment, but it has still not been completed. Has anyone experienced a similar delay with an organization enrollment? If so, how long did the verification process take, and was there anything additional you had to do to get the enrollment completed? Any guidance would be appreciated. Thank you.

Hello, I am experiencing a serious issue with my Apple Developer Program enrollment and would appreciate help from Apple staff or anyone who has experienced the same situation. I enrolled as an Individual through the Apple Developer website and completed the €99 payment on August 8, 2026 at approximately 21:57 (Portugal time). Today is August 13, 2026, so five days have passed since the purchase. The situation is currently: Apple successfully created my €99 Apple Developer Program order. I received an official Apple Store email confirming that the order is being processed. The order has not been cancelled. I have received no refund. I have received no payment rejection. The Apple Store order page still shows the order as active and processing. The order page even displays a delivery-style progress bar with Processing → Preparing to Ship → Shipped → Delivered, although this is a digital Apple Developer Program membership. My Apple Developer account still shows “Pending”. The account page still displays “Purchase your membership” and “Your purchase may take up to 48 hours to process”, even though the membership was already purchased five days ago. So Apple Store appears to have an active paid order, while the Apple Developer system behaves as if the membership has not been purchased. I contacted Apple Developer Support. Case ID: 20000133984820 The first response I received after waiting several days did not explain what happened to the existing payment or order. I was instead advised to resubmit the enrollment through the Apple Developer app. However, this does not answer the main issue: What happened to the existing €99 purchase, and why has it remained unresolved for five days? I also currently do not have access to an iPhone, iPad, or compatible Mac, so simply restarting the enrollment through the Apple Developer app is not a practical solution for me. The web enrollment is an officially supported enrollment method, and the purchase through that method has already been completed. I have replied to Developer Support requesting escalation and asking them to investigate: whether the €99 payment was successfully captured; whether the order is correctly linked to my enrollment; why the order is still being processed; whether any identity/payment verification is required; and whether the existing enrollment can be manually reviewed and activated. My application is ready for release, including real-device testing, and this unresolved enrollment is now directly blocking the launch. I am fully willing to complete any legitimate identity, address, or payment verification Apple requires. I am also available for a telephone call if Developer Support needs to verify any information. I am not looking for a workaround or a way to bypass verification. I simply need Apple to either process the enrollment I already paid for, tell me exactly what additional verification is required, or explain clearly what has happened to the existing payment/order. Has anyone recently experienced this exact situation — payment completed, order still processing, account Pending, and “Purchase your membership” still displayed after several days? If anyone from Apple Developer Relations sees this, I would greatly appreciate a review or escalation of Case ID 20000133984820. Thank you.

Container ID: iCloud.com.bluecrestcreative.HouseholdWizard (and a brand-new test container, iCloud.com.bluecrestcreative.HouseholdWizard2 — see below) Calling persistentContainer.share(_:to:) on an NSPersistentCloudKitContainer never successfully completes against the Production CloudKit environment. The identical code works fine against Development. What I've ruled out so far, each with a real test: Stale local state — wiped the local Core Data store entirely and retried from empty. Same failure, new share/zone UUID each time. Container-specific corruption — created a brand-new CloudKit container under the same team (never used before, zero history) and pointed the app at it instead. Same failure. Permissions — confirmed full "Edit Production" access in Container Permissions for my account. Entitlements mismatch — verified identical entitlements between a working Development build and the failing Production build (only the environment key differs). Daemon/session staleness — rebooted the Mac, retried. Same failure. CloudKit Dashboard schema — "Deploy Schema Changes to Production" shows zero pending changes even after a successful share in Development, so the cloudkit.share system type doesn't appear to be tracked by the normal schema-deploy mechanism. The specific error captured from the original container (Xcode 26.6, macOS): NSCloudKitMirroringDelegate _requestAbortedNotInitialized: Never successfully initialized and cannot execute request due to error: CKError "Partial Failure" (2/1011); "Failed to modify some records"; partial errors: { cloudkit.zoneshare:(com.apple.coredata.cloudkit.share.:defaultOwner) = CKError "Invalid Arguments" (12/2006); server message = "Cannot create new type cloudkit.share in production schema" } On the brand-new test container, the failure mode was slightly different (an initial CKError Code=5 / notAuthenticated during user-identity fetch, then CKShare.url simply never populates, indefinitely), but the end result is identical: sharing never actually completes. Has anyone seen this, or know what's needed to make CKShare record creation work against Production for a container? Already have a DTS incident open (Case-ID 21466535) but wanted to ask here in parallel since code-level questions get routed here anyway.

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??

Hello, I am experiencing a serious TestFlight issue that began immediately after I removed some testers from an External Testing group. Right after removing those external testers, all existing TestFlight builds for my app were suddenly marked as Expired, even though they were still within the normal 90-day TestFlight validity period. I did not manually expire any build. Removing an external tester should only revoke that tester’s access and should not affect the status of any TestFlight build. After the mass expiration, I uploaded a replacement build. The new build uploaded and processed successfully in App Store Connect, but I could not add or submit it for External TestFlight Beta App Review. App Store Connect incorrectly displays the following message: Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership. However, my account currently shows: Account type: Individual — Account Holder Apple Developer Program membership: Active Apple Developer Program License Agreement: Accepted Free Apps Agreement: Active No pending Apple Developer Program agreements Replacement build uploaded and processed successfully I inspected the failed App Store Connect network request and found the actual backend error: POST /iris/v1/betaAppReviewSubmissions HTTP 422 Unprocessable Content { "errors": [ { "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] } The exact sequence was: External testers were removed from the External Testing group. All existing TestFlight builds suddenly became Expired. A replacement build uploaded and processed successfully. The build could not be submitted for External Beta App Review. The backend returned ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. I have found reports from other developers describing the same sequence after removing external testers, including all TestFlight builds unexpectedly expiring and TestFlight distribution no longer working. This appears to be an account or team-level TestFlight backend issue in which the Beta Contract or distribution state becomes detached after modifying external testers. I have already contacted Apple Developer Support and provided the private account, app, request, and error identifiers through my support case. Could an Apple engineer please confirm whether this is a known backend issue and whether the TestFlight Beta Contract needs to be re-provisioned or re-attached? Has anyone else experienced this exact issue after removing external testers? If Apple resolved it, what action was required on the backend? Thank you.

Hi, our organization's Apple Developer Program enrollment was recently completed, but App Store Connect access has never been provisioned, and I'd appreciate help escalating this. Timeline: Organization enrollment verified and completed; "Welcome to the Apple Developer Program" email received more than 50 hours ago Membership shows as active on developer.apple.com under the correct team Apple Developer Agreement accepted; Apple Developer Program License Agreement accepted on August 11, 2026 - no pending agreements are shown on the account page I am the Account Holder, signing in with the same Apple Account that was used to enroll the organization Despite this, signing in at appstoreconnect.apple.com consistently returns: "Your Apple Account isn't enabled for App Store Connect." What I've already tried: signing out of both developer.apple.com and App Store Connect and signing back in via a private/incognito window, different browsers, and navigating to App Store Connect from the developer account page. The error is unchanged. I contacted Apple Developer Support by email (no phone option is available in my region) and am waiting on a reply - case number: 20000135517368 This looks like the known issue where App Store Connect provisioning doesn't trigger for a new organization enrollment. Could someone from Apple take a look or advise how to get the provisioning kicked off manually? Happy to provide the Team ID privately if needed.

Apple Developer Program enrollment stuck on Pending — payment not charged and profile fails to load Hello, I’m having an issue with my Apple Developer Program enrollment and would appreciate any guidance from Apple or anyone who has experienced the same problem. I submitted my Individual enrollment on August 10 through the Apple Developer website and completed the $99 membership purchase process. After submitting the order, I received the “Thank You — We are processing your order” page stating that processing may take up to two business days. However, since then: My enrollment is still showing Pending. The $99 membership fee has not been charged to my card. I have not received a membership activation email. The website sometimes shows “Complete Your Order” again and allows me to enter payment details again. In the Apple Developer app, Enroll Now is disabled and it says: “Enrollment through the Apple Developer app is not available for this Apple Account.” The Profile section also displays: “Profile failed to load.” I already contacted Apple Developer Support and have an open support case, but I have not yet received a substantive response. My Apple Account itself works normally, and other Apple purchases have successfully gone through, so this appears to be specific to the Developer Program enrollment. I do not want to submit the $99 payment again because I’m concerned about creating a duplicate purchase while the original enrollment is still Pending. What is especially frustrating is the complete lack of communication. Are Developer Program applicants from Kazakhstan handled differently or given lower priority? If not, I would appreciate some clarity on why an enrollment can remain stuck with no payment processing and no response from support for several days. Has anyone from Kazakhstan or another country experienced this exact situation? If so, was your enrollment eventually activated automatically, or did Apple Developer Support need to manually fix the account? Apple Developer Support: I have an existing Enrollment ID and Case ID and can provide them privately if needed. Thank you.

Hello, My app submission has been waiting for review for 7 days. I've requested expedited review twice and contacted Developer Support; no response to either yet. Apple ID: 6789087223 Bundle ID: ai.spinsports.app Is there anything that can hold a submission in "Waiting for Review" before assignment that I should be checking on my end? If there's a common blocker at the pre-assignment stage, I'd rather find it myself than keep waiting. Or anything else I can do on my end? Thank you.

welcome I created an account as a developer and paid the subscription fee and I did not receive any response from you to activate the account. Please inform me when the account will be activated

Hi, My Mac app allows a customer to drag and drop a file package onto a SwiftUI view. I can't seem to find a way to successfully call .startAccessingSecurityScopedResource() with the file/dir that was dropped into the view. I put together a simple test app. Here is the code: struct ContentView: View { @State var isTargetedForDrop: Bool = false var body: some View { VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) Text("Hello, world!") Rectangle() .stroke(Color.gray) .onDrop(of: [UTType.fileURL], isTargeted: $isTargetedForDrop) { providers in guard let provider = providers.first(where: { $0.hasItemConformingToTypeIdentifier(UTType.fileURL.identifier) }) else { return false } provider.loadItem(forTypeIdentifier: UTType.fileURL.identifier, options: nil) { item, error in if let error = error { print("Drop load error: \(error)") return } if let url = item as? URL { print("Dropped file URL: \(url)") } else if let data = item as? Data, let url = URL(dataRepresentation: data, relativeTo: nil) { print("Dropped file URL (from data): \(url)") let access = url.startAccessingSecurityScopedResource() if access { print("Successfully accessed file at URL: \(url)") } else { print("Failed to access file at URL: \(url)") } url.stopAccessingSecurityScopedResource() } else { print("Unsupported dropped item: \(String(describing: item))") } } return true } } .padding() } } When I drop a file package into this view I see, "Failed to access file at URL: <the_full_file_path>" I'm running Xcode 26 on macOS 26.

If a ViewAttachmentComponent moves into frame, it is low resolution until something changes the view while it is in frame. Video demonstrating the behavior: https://youtu.be/KXEFFiAnv1s I am on visionOS 27 beta 4. This did not occur when I was on visionOS 26.5. Also using Xcode 27.0 beta 4 and macOS 27.0 beta 4. To reproduce, have a ViewAttachmentComponent in an immersive space, look away, then look back, and it'll be low resolution. Anything which would change the view while it's in frame will then cause it to update in full resolution. Screenshot of low-resolution view after it moves back into frame from being out of frame: Screenshot after updating the view, making it high-resolution again: I've submitted feedback as FB24116473.

I've just downloaded the Xcode 27.0 beta 5 on a macOS 26.6.1 machine and tried to build my app (which includes Metal CoreImage kernels). I'm met with a new (to me) error; /Users/…/Developer/…/air-lld:1:1 symbol(s) not found for target 'air64_v28-apple-macosx26.0.0' and from the build log; air-lld: warning: ignoring file '/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage.metallib', file AIR version (2.9) is bigger than the one of the target being linked (2.8) air-lld: error: symbol(s) not found for target 'air64_v28-apple-macosx26.0.0' metal: error: air-lld command failed with exit code 1 (use -v to see invocation) I have no MTL_LANGUAGE_REVISION in my build settings. If I add one, with value Metal41 the app builds fine, but crashes at runtime as Metal 4.1 isn't supported on macOS 26. I imagine this is a beta Xcode and or macOS SDK bug, is there a workaround?

Hello, We are seeking guidance regarding our Apple Developer Program account, which is currently under a Pending Termination Notice related to Section 3.2(f) of the Apple Developer Program License Agreement. The notice stated that our account had repeatedly submitted apps with unresolved guideline violations and that Apple believed these submissions were attempting to evade the review process. We want to make it clear that we never intended to mislead Apple or bypass the review process. We understand the seriousness of Apple's concerns and have taken the matter very seriously. Following the notice, we submitted an appeal to the App Review Board on June 4, 2026. In our appeal, we acknowledged the issues raised, explained the circumstances that led to the repeated submissions, and committed to implementing stronger internal review and compliance procedures. We also expressed our willingness to remove the app involved if necessary to ensure full compliance with Apple's policies. We have been members of the Apple Developer Program for several years and have always aimed to build products that comply with Apple's guidelines. We value the App Store ecosystem and would like the opportunity to address any concerns and continue serving our users responsibly. We want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Thank you for your time and any guidance you can provide.

Hi Everyone, we've started working on the Xicap tag, a new general purpose active spatial accessory puck for the Vision Pro here at Xikaku. It can be attached to any type of rigid object or will work as a wearable device. We're adding customizable buttons and IO ports for switches etc. to make it versatile for all kinds of tracking applications. I created an intro on our blog with some more info: https://xikaku.com/blog/xicap-vision-pro-spatial-accessory Happy to receive any kind of feedback or comments so we can kepp that in mind while finalizing the device. Klaus

Hello, My app submission has been waiting for review for 8 days, and there has been no status update or request for additional information. Submission ID: f9cc5319-693b-4809-8bcb-5eb0e8ad28bd I understand that review times can vary, but this is considerably longer than I have experienced before. Could an Apple representative please check whether the submission is progressing normally or if any action is required from my side? Thank you.

So how can I still login

Hello, I've been trying to enroll in the Apple Developer Program as an Individual/Sole Proprietor for several days now, and I keep hitting the same error after submitting my personal information: "We are unable to process your request. An unknown error occurred." What I've already checked and tried: -Tried multiple browsers (Chrome, Safari, Edge) -Cleared cache and cookies, tried incognito/private mode -No VPN active -Two-factor authentication is enabled and working -My Apple ID region is set to France -Tried both the Developer app flow and developer.apple.com/enroll (web) directly Additional context that may be relevant: I'm based in La Réunion (French overseas department/DOM), and my trusted phone number for 2FA is a local +262 number. La Réunion isn't listed separately as an App Store region (it falls under France), so my Apple ID country/region is set to France — but I wonder if there might be a mismatch check happening somewhere between the phone number's country code and the Apple ID region that's causing this. This is blocking my app's TestFlight/App Store release, so any guidance — from Apple staff or from other developers who've faced this and found a fix — would be really appreciated. Thank you!

Hello everyone, I need help about ASK. AccessorySetupKit: removeAccessory confirmation dialog displayed in English while device, app and ASK picker are localized in French. Area: AccessorySetupKit / Bluetooth Type: Incorrect/Unexpected Behavior iOS version: iOS 26.6 When calling ASAccessorySession.removeAccessory(_:completionHandler:), the system confirmation dialog ("Remove paired accessory? "MyAppXXX" is attempting to remove MyDevice.") is displayed in English, even though: The device language is French Locale.current.identifier = fr_FR The app's effective localization resolves to French Bundle.main.preferredLocalizations = ["fr"] The app bundle declares French Bundle.main.localizations = ["en", "es", "it", "fr", "nl"] developmentLocalization = "en" All other AccessorySetupKit UI is correctly localized: the ASK picker shown by showPicker(for:) and the pairing dialogs appear in French as expected. Only the remove-accessory confirmation dialog falls back to English. Issue is already open with Apple feedback Assistant: FB24306024 And also by Apple technical support 21587044 Thank you

When using AccessorySetupKit to remove accessories, a pop-up window appears when calling removeAccessory. However, the text in the pop-up window does not change according to my iPhone's language settings and remains only in English. Has anyone encountered this issue? Does Apple have any plans to address this compatibility issue?

In the most recent tvOS 27 betas, the icons for Apple’s apps on tvOS gained Liquid Glass refraction effects that change as you move your finger over the remote’s touch surface. This can be most clearly seen in the icons for Photos and Podcasts. How can our third-party apps make use of these effects on tvOS, which isn’t supported by Icon Composer? Is the intention for third party apps to continue using flat design while Apple’s own apps use Liquid Glass?