Overview

I'm hitting the same issue. Deploying the Development schema to Production fails every time with HTTP 500 internal-error on the …/schema/<developmentSchemaId>/promote request. It fails from both the "Changes" tab and the "Diff View" tab of the Confirm Deployment dialog. detailedMessage is undefined. Filed as FB25280547, with the container ID, request UUIDs and screenshots. Example requestUuid: 7f4aec62-6ead-4e86-8784-77be751d3622 The diff is purely additive: Core Data / NSPersistentCloudKitContainer fields such as _ckAsset assets, CD_moveReceipt and one new string field, plus QUERYABLE indexes on ___recordID. No type changes and no removals. I tried refreshing, re-signing in, and a private window. It still fails. This blocks our App Store release because the new build writes a field that Production doesn't have yet. Could someone from the CloudKit Console team take a look? Thank you!

Hello, I paid for the Apple Developer Program membership on October 20, 2026, and submitted my passport and ID for verification, which Apple confirmed receiving. My enrollment is still Pending, and my support case (103006113844) has had no reply. The callback option is unavailable because the case is open. Could Apple Developer Program Support please review and complete my enrollment? I can provide any additional information through an official channel. Thank you.

Hello Apple Developer Support, I paid for the Apple Developer Program on Friday, October 16, 2026. The payment was approved (the invoice shows an amount due of 0.00), but my membership has still not been activated. It has been 7 days, and I have not received any email asking for documents, verification or more information. I am posting with the same Apple ID that I used for the enrollment and the payment. Purchase details (from the Apple invoice): Online order number: D005368439 Invoice number: MD20790795 Sales order number: AFG2425219 Invoice date: 2026-10-16 Product: Apple Developer Program (D4521G/A), 99.00, paid by credit card Name on the invoice: Victor Hugo, Brazil Enrollment details: My identity was already verified in the Apple Developer app with my passport. I intended to enroll my company: FRAME STUDIO SERVICOS DIGITAIS LTDA (Brazil). The invoice was issued in my personal name, so I am not sure whether the enrollment was registered as an individual or as an organization. What I need: Please check why my membership was not activated after the payment. Please confirm whether my enrollment is registered as an individual or as an organization. If anything is missing on my side (a document, a D-U-N-S Number or any other verification), please tell me exactly what to send. I need the membership to sign and notarize the macOS installer of our software, and our users are blocked until then. Thank you for your help. Victor Hugo FRAME STUDIO SERVICOS DIGITAIS LTDA

Dear Apple team, we kindly ask for your help in resolving an issue, as our attempts to contact support - both via email and by requesting a callback - have not produced any results. We believe that the removal of our application from the App Store may be related to a synchronization discrepancy between our App Store Connect account and our Apple Developer Program membership status. At the same time, the subscription status appears to be inconsistent between App Store Connect and the Apple Developer account. We would appreciate your assistance in checking whether the membership status and associated entitlements have been correctly synchronized. Our support ticket number is 102978608429. Could you please advise on the next steps? Also, if possible, please reach out to us via email at dev@aigenis.by or by phone at +375 29 239-70-27. Apple Account used for the membership: dev@aigenis.by App name: AIGENIS: понятные инвестиции

Hi everyone, I'm an individual developer with a sole proprietorship registered in Poland. I'm a citizen of Belarus, I live in Poland with permanent residence and I'm a Polish tax resident. The problem is that in App Store Connect the Country of citizenship field in my W-8BEN form is set to Poland and I can't change it. I tried resetting the tax questionnaire, didn't help. I don't want to submit the form with wrong info, so my Paid Apps agreement is stuck in Pending User Info since September 23. My bank account has been stuck in Processing since the same day too. What I've done so far: Sep 23 wrote to Developer Support (case 102973741691), on Sep 25 they told me to contact Finance Sep 26 opened Finance case 22490850, followed up on Oct 5, 12 and 19, also sent an official extract from the Polish business register that shows my citizenship. No reply at all Oct 12 wrote to Developer Support again, nothing Oct 16 called support, they said someone would help me within a week, nobody contacted me Did anyone have the same issue with the citizenship field? How did you get it fixed? Thanks

Hi everyone, I'm trying to enroll in the Apple Developer Program, but I'm facing an issue with my Apple Account. When I open the Account section in the Apple Developer app on my MacBook, I see the following error: This address is not valid. To continue enrolling, contact us. The “Enroll Now” button is also disabled, so I can't proceed with enrollment. I'm signed in with my Apple Account, and I would like to understand why this error is appearing and how I can resolve it. Has anyone faced this issue before? Do I need to contact Apple Developer Support, or is there another way to fix it? Any help or suggestions would be greatly appreciated. Thanks!

I have been accepted in the Apple Developer program as an organization since October 14, 2027. However till date I was unable to log into the App Store Connect platform. I get a message saying "Your Apple Account isn't enabled for App Store Connect." I have raised two tickets since that date and still have not received a response. Anyone having a similar experience? Applied to Google Play and App Store at the same time and the process in Google Play was much faster. Case ID is 102992261865 (3x follow-ups)

Hi! I've tried reaching out to support but I'm not getting any responses. It's been two days since I created my account and I've been trying to enroll in the development program ever since but I keep getting this error: { "responseId": "10025cd6-1bdb-4ac3-8c9d-e7d615fc1ccc", "resultCode": 202018, "resultString": "Your request could not be processed", "userString": "Your request could not be processed", "creationTimestamp": "2026-10-22T13:21:51Z", "userLocale": "en_US", "requestUrl": "https://developer.apple.com/services-enrollment/submitIndividualEnrollment", "httpCode": 406 } I don't know what the problem is nor what I can do to fix it. Please, can anybody help me?

Hi When I try to Enroll into the Developer Program via the Apple Developer App using MacBook Air M1, it gives error message as shown in the screenshot attached - Unable to Continue. Contact Support. I contacted Apple Developer Support Ref No 102984813085 and got some checklist that I completed. Even after all these steps, still getting the same error. Now, after trying to follow up with Support, there is no reply coming back for last 4 to 5 days. Also, Developer Phone Support is totally unavailable in India these days at all times. Can this be resolved or is there any other way to Enroll. Regards Kapish

Hello Apple Developer Support, I am requesting assistance with my Apple Developer Program enrollment, which has been stuck in "Pending" since September 26, 2026. Today is October 22, and 26 days have passed without activation. I have completed the membership payment. I have the order number and the official Apple invoice in PDF format. I have an Enrollment ID associated with my application. I have contacted Apple Developer Support by phone, but the issue remains unresolved. I have also sent emails to the relevant support department without receiving a resolution. Could an Apple Developer Support representative please help escalate this case to the enrollment team and clarify: Why is my enrollment still pending after 26 days? Has my payment been correctly linked to my enrollment? Is there any missing verification or action required from my side? Can this case be manually reviewed and escalated? I can provide my Enrollment ID, order number, invoice, and previous support correspondence through a private official support channel. I would appreciate a concrete status update and a clear next step. Thank you.

Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried. The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection. I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall. WHAT THE FRAMEWORK ACTUALLY RETURNS The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed": ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: NSUnderlyingError: So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there. Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here. WHAT I RULED OUT Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way. Not the entitlement. Verified inside the signed binary, not just in the portal: application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"] I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active. Both distribution types fail. TestFlight and ad-hoc. WHAT IS LEFT After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself. This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025. THE ASK Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)? I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases. Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure). This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login. Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.

Subject: Supported fail-closed ACL absence verification on macOS 27.0.1 / APFS Environment: macOS 27.0.1, build 26A434; APFS; installed macOS 27.0 SDK. We need a supported, documented way to determine whether an existing filesystem object has no effective ACL entries, while rejecting genuine retrieval failures and unsupported or unavailable ACL evidence. We are seeking clarification of the public interface contract, not alleging an Apple defect. For existing directory and regular-file fixtures, pathname metadata and descriptor metadata identify the same object. Errno is cleared immediately before each native call and captured immediately afterward. ACL retrieval uses ACL_TYPE_EXTENDED: acl_get_file(path, ACL_TYPE_EXTENDED) acl_get_fd_np(fd, ACL_TYPE_EXTENDED) On fresh objects, both return NULL with ENOENT. Explicit one-entry fixture ACLs are retrieved successfully. Explicit zero-entry fixture ACLs can also yield NULL/ENOENT, while attribute queries return a serialized zero-entry ACL. The attribute queries use getattrlist() and descriptor-bound fgetattrlist(), requesting ATTR_CMN_RETURNED_ATTRS | ATTR_CMN_EXTENDED_SECURITY, with FSOPT_NOFOLLOW | FSOPT_REPORT_FULLSIZE and WITHOUT FSOPT_PACK_INVAL_ATTRS. Buffer lengths, variable-reference bounds and returned-attribute validity are checked. For the existing directories of interest, both calls succeed but omit the ATTR_CMN_EXTENDED_SECURITY returned bit. Explicit populated and zero-entry fixture records do set the bit. APFS reports valid VOL_CAP_INT_EXTENDED_SECURITY support; we do not assume that volume capability proves per-object ACL availability. On macOS 27.0.1, build 26A434, using APFS, which supported interface and documented conditions allow software to distinguish an absent ACL from unavailable or unsupported ACL evidence when descriptor-bound attribute queries succeed but omit ATTR_CMN_EXTENDED_SECURITY and native ACL getters return ENOENT for an existing object? Please clarify: Whether ENOENT has a supported ACL-absence interpretation, and under exactly which checked conditions. Whether an omitted extended-security attribute can establish ACL absence, rather than unavailable or unsupported evidence. How explicit zero-entry ACLs differ from absent ACL records through supported interfaces. How KAUTH_FILESEC_NOACL should be interpreted through supported APIs. How genuine retrieval failures, including permission, I/O, allocation and unsupported-operation errors, must remain distinguishable. Whether a supported descriptor-bound verification method exists that preserves fail-closed security checks and object identity binding; please identify its guarantees and limitations regarding pathname/ancestor changes and later operations. Whether relevant behavior is specific to this macOS/APFS version. Please identify the applicable public documentation or supported verification sequence. We do not want to modify permissions, synthesize ACLs on target objects, treat invalid-attribute defaults as real evidence, or accept ambiguous omission/ENOENT as success. Existing ownership, mode and confinement checks must remain separate mandatory checks. If no public API can make this distinction reliably, please state that limitation.

We've spent several days diagnosing a CoreData migration crash that is iOS 26-specific and reproducible 100% of the time. Posting here in case others have hit this and because we believe it's an Apple bug worth documenting. Upgrading from our App Store build (CoreData model v10) to our latest TestFlight build (model v11) crashes on iOS 26 with: NSCocoaErrorDomain / Code 134110 no such column: "Z_110GROUPITEMS1" The same upgrade path on iOS 17 and iOS 18 works perfectly. What v10→v11 changes Two new entities added alphabetically early in the alphabet One new optional boolean attribute on an existing entity One new optional to-many relationship on the same existing entity All changes are lightweight-migration compatible. We use shouldMigrateStoreAutomatically = true and shouldInferMappingModelAutomatically = true Here's what we observed Adding two entities alphabetically shifts Z_ENT numbers for all subsequent entities. A central entity (EntityA) moves from Z_ENT 110 (v10) to Z_ENT 112 (v11). It has many-to-many relationships with four other entities (EntityB, EntityC, EntityD, EntityE), all using the same inverse relationship name: groupItems. Because multiple join tables reference EntityA via the same inverse name, CoreData appends a disambiguation suffix (1, 2, etc.) to column names in each join table. In v10, the relevant join tables are Z_110ENTITYB and Z_110ENTITYC, each with a column named Z_110GROUPITEMS + a suffix. -com.apple.CoreData.SQLDebug 3 prints: ALTER TABLE Z_112ENTITYB RENAME COLUMN Z_110GROUPITEMS1 TO Z_112GROUPITEMS1 But the actual column in a fresh iOS 26 v10 store is Z_110GROUPITEMS2. Column not found → crash. iOS 17/18 is consistent: both code paths use suffix 1 for Z_110ENTITYB and 2 for Z_110ENTITYC. Migration succeeds. To confirm We opened the SQLite store from a fresh iOS 26 v10 install and inspected the schema: CREATE TABLE Z_110ENTITYB ( Z_110GROUPITEMS2 INTEGER, Z_112ENTITYB INTEGER, PRIMARY KEY (Z_110GROUPITEMS2, Z_112ENTITYB) ); Then we manually renamed Z_110GROUPITEMS2 → Z_110GROUPITEMS1 and Z_110ENTITYC.Z_110GROUPITEMS1 → Z_110GROUPITEMS2 in the SQLite file. Re-ran the app — migration succeeded. The suffixes are literally swapped between what iOS 26 creates on fresh install vs. what iOS 26's migration engine expects. Our database has over 50 entities and we never before faced such an issue. This is not the first lightweight migration we are releasing after iOS 26 and that's what puzzled us. Why now?

Hello everyone, I'm a new developer and this is my first app, Frenchie Dash (Apple ID 6822067764), a small offline game about my rescued French bulldog. Here is the timeline: October 12: first submission. It was reviewed the same day, and App Review asked for more information about my new developer account (Guideline 2.1). October 13: I replied with all the answers and a screen recording from my iPhone, and submitted build 1.0 (2). After that, the submission sat in "Processing" for a whole week and never reached review. October 16: I accepted the updated Apple Developer Program License Agreement and the new Paid Applications agreement. Banking and tax forms are Active. October 20: I removed the stuck submission and submitted the app again. Today, October 22: it is still "Waiting for Review", more than 48 hours later. I also contacted Developer Support three times (case 102998013460) but haven't received a reply yet, and phone support is currently unavailable. Has anyone seen this before? Is there anything else I should do on my side? If someone from App Review could take a look, I would really appreciate it. Thank you! Vasilii

Hello, Our app, Hera Media Player, has received different review outcomes on iOS and macOS. The iOS version, 1.0.2 (3), was rejected under Guideline 4.3(a) on October 16. The macOS version of the same project has since been approved for App Store distribution under the same developer account. We replied in App Store Connect with additional information and the macOS approval, asking for the iOS decision to be reconsidered. Three days have passed since our latest reply without a response. We understand that each platform is reviewed separately. Could someone from App Review help us understand the different outcomes and advise on the next step? App: Hera Media Player iOS submission: 814d35ea-f1ac-40c9-bd34-d32cb662f117 Thank you.

Hello, Our app, Alda Safety, Apple ID: 6444542075, has remained in "Waiting for Review" since October 11. The app is used by fishing vessel crews for safety management, including drill and incident reporting. We have contacted Developer Support (Case ID: 103004841304) If an Apple representative can help investigate, we can provide the app and submission details through a private support channel. Thank you.

Hi I am curious if others are seeing the same delays where the review team is taking 5 business days to review your submission even in the expedited queue? My app has been submitted for review since 9/23 and I am still not approved. The level of support and customer centricity has really gone downhill over the last few years. Google reviewed and approved my app in under 2 hours.

Hello, My first iOS app has not been picked up by App Review for over two weeks, and I haven't been able to reach anyone. Sep 18: App Review requested more information under Guideline 2.1 (new developer account, "limited App Review history"). Oct 8: I replied in App Store Connect with a screen recording and all the requested answers. App Review then asked me to sign the updated Apple Developer Program License Agreement and reply. I signed it, but the submission was removed when I resubmitted, so that thread closed before I could reply. Oct 8 – 18: submission 91c4bf1a-f343-496e-8595-bc84d2c2a788 sat in "Waiting for Review" and never moved. Since Oct 18: the current submission, d2ac6b73-8f2f-4a73-8501-9649a153d9af (iOS 1.8.0, plus an auto-renewable subscription and its group), is also "Waiting for Review". All agreements, banking and tax are active. The full walkthrough video and the 2.1 answers are in App Review Information. Support cases 102997498785, 103003701199 and 103003710479 have received only automatic confirmations. Could someone from App Review please check whether this submission is blocked or needs anything else from me? Thank you.

Hello App review Team, Our app has been submitted for up to a week now. Submission id - 8b32ad4d-9912-4f25-837c-13b15323a258. Kindly review. Thank you

Hello everyone, I'm the president of a French software development company, and I'm facing an extremely frustrating situation with Apple's App Review process. We submitted an event application for a major international client 14 days ago, on October 9, and it has been stuck "In Review" since Monday, October 19. Despite our repeated attempts to resolve the situation, nothing has changed. So far, we have: Called Apple Developer Support between 6 and 8 times. Submitted 2 expedited review requests. Sent 3 follow-up emails. Repeatedly explained the critical business impact of this delay. During nearly every phone call, we've been told that someone is actively reviewing our application and that approval should happen very soon. Yet days keep passing, and we have received absolutely no explanation, no rejection, no request for additional information, and no estimated resolution date. The situation has become extremely serious for our company. Our client publicly announced that the application would launch on Friday, October 16. When that deadline passed, the launch was announced again for this week. We have now missed two publicly communicated launch windows, through circumstances entirely outside our control. As a small development company working with a major brand, this is causing significant reputational and commercial damage. We are doing everything possible to protect our client's trust, but we have no visibility into what is happening. We fully understand that Apple needs to review applications carefully. We respect that process. However, 14 days without any actionable information, despite 8 calls and 2 expedited review requests, is extremely difficult to understand or justify from a developer's perspective. At this point, we are not even asking Apple to bypass its guidelines. We simply need transparency and a meaningful escalation. Has anyone experienced a similar situation recently? Is there any way to contact the App Review team directly or escalate a review that appears to be stuck, beyond the standard support channels and expedited review requests? Any advice or assistance from an Apple representative would be greatly appreciated. Thank you.