“Account Locked”

I’m trying to complete my Apple Developer Program enrollment, and I’ve now been stuck in this process for about a month. The main issue is that the passport upload step in the Apple Developer app fails almost immediately every time with the same error, so I can’t complete identity verification and move forward. I’ve already gone through a very long back-and-forth with Apple Developer Support. At first, my enrollment through the website failed, and I was told to continue through the Apple Developer app instead. Then I ran into the passport upload issue in the app. Support asked me to upload identification documents through secure links, and I uploaded the requested documents, including my passport. I also updated my Apple Account name to match my official identification. During this process, one support representative, James, was helping me and there was a lot of back-and-forth. At one point it seemed like the case was being escalated and moving somewhere, but after that the responses became slower an

We are a development team building an application targeted specifically for the Southeast Asian market. We have been caught in a frustrating review cycle and are hoping to get some guidance on how to move forward. The Situation Our application is intentionally unavailable in the United States. Per Apple's guidance, we implemented a We are currently not available in your country error screen that displays when a user's location falls outside our supported regions. This is intentional, expected behavior — not a bug. The Problem Despite providing detailed testing instructions and dedicated test accounts tied to the correct region, our Reviewers consistently: Do not use the test accounts we created for them Do not follow the regional setup instructions we provided Access the app from a US-based location See the geographic restriction screen (the one Apple instructed us to build) Flag it as a bug and reject the submission We have confirmed this is the root cause, as the rejection notes reference

Hello, I am seeking guidance regarding a Pending Termination Notice received on March 18, 2026 for the developer account of Kaagapay Platform Inc. Background: Our app, CreditKaagapay: Score & Report (App ID: 6744999391), is a credit report and loan matching platform operating in the Philippines in partnership with the Credit Information Corporation (CIC). The app maintained a 4.8-star rating with over 4,000 reviews. No prior warnings were issued before the notice. Notice Details: The notice cited Guideline 5.6 and Section 3.2(f), alleging dishonest or fraudulent activity related to account information. Timeline: • March 18: Received the Pending Termination Notice. Submitted two appeals (App Removal + Pending Account Termination) on the same day. Both received on-screen confirmation. • March 25: Submitted a follow-up through the App Review Status contact form. • March 26: Developer Support confirmed the appeal was forwarded to the App Review Board (Case ID: 30000003321343). • Apr

I’ve developed an authorization plug-in with a mechanism that runs an SFAuthorizationPluginView subclass and I’m facing a couple issues: - Glitch after successful login After setting kAuthorizationResultAllow in the context the user is successfully logged in and brought to the desktop but the login controls remain onscreen for a few seconds after login is complete, resulting in them being visible at the same time as the dock, menu bar and desktop.
 I’ve also tried what’s mentioned here https://developer.apple.com/forums/thread/780212 but without any luck. It’s also worth mentioning that the deinit() in my SFAuthorizationPluginView subclass never gets called when the plugin it’s loaded at the login stage but it does get called the plugin is used to re-authenticate the user after they locked their screen. - update() doesn't trigger the plugin to call view(for:) I’m trying to update the UI elements out of my control (like buttons and user avatar images) in order to have them placed at the proper positio

Hi Apple Community, We are using Automted Device Enrollment to Enroll macOS Devices and we used to Create AutoAdmin, PrimaryAccount using the Command Account Configuration . As a Part of Primary Account Creation while testing we see that BootStrap Token is Escrowed to MDM, and SecureToken is Created to Primary Account. The Primary Account user will enable FileVault as part of our process. As Tested internally, we seen that SecureToken is escrowed to AutoAdmin only when BootStrapToken is escrowed to MDM By device and AutoAdmin logs in then. That too After FileVault Unlock Since we Sendout the Laptop to users to setup themselves there are no chances of AutoAdmin Login to occur. And it defeats the purpose of having the AutoAdmin Account in emergency situation to login into it from Login Window. Can someone confirm if this behavior is expected and what are the expectation and recommendations from Apple on when to use AutoAdmin Account. Is there any other ways

Hello everyone, I am trying to understand whether this is a normal delay or if there may be an account-level review issue affecting my submissions. I am an individual developer. I submitted my first app for review on March 14, 2026. It remained without a meaningful response until March 31, 2026. During this time, I sent three expedite review requests, but none of them helped. Because nothing moved, I withdrew the previous submission and uploaded a third build for the same app. However, the app is still stuck in review flow. At the same time, I submitted my second app on March 22, 2026. I also requested an expedite review for that app, but it is still in Waiting for Review as well. So currently: • App 1 was first submitted on March 14, 2026 • Multiple expedite requests were sent • The original submission was withdrawn and a new build was submitted • App 2 was submitted on March 22, 2026 • Both apps have been heavily delayed • One is still in review flow, and the other is still Waiting for Review I wou

I'm trying to enroll in the Apple Developer Program as an individual, but I keep hitting a dead end. Every time I attempt to enroll, I get a generic error saying my enrollment could not be completed at this time, with no detail on why. I've reached out to Apple Developer Program Support by email about this but haven't received any response, which is why I'm turning to the community here. On my end, I've ruled out all the common issues. Two-factor authentication is on, I have a valid major credit card on file, I'm enrolling through the web rather than the Developer app, no VPN is active, and my Apple ID is email-based. If anyone from Apple can take a look at my account, or if someone in the community has run into this same error and found a fix, I'd really appreciate the help. Thanks in advance.

I'm building a freediving app for Apple Watch Ultra using the shallow depth entitlement (com.apple.developer.submerged-shallow-depth-and-pressure). My app uses WKExtendedRuntimeSession with the underwater-depth background mode, and it works correctly — the session starts, Water Lock activates automatically, and Crown hold water ejection ends the session as expected. However, the app does not appear in Settings > General > Auto-Launch > When Submerged on the watch. Other third-party apps (including one that hasn't been updated in ~2 years and presumably only has the shallow entitlement) do appear in this list. My configuration: WKBackgroundModes: [underwater-depth, workout-processing] WKSupportsAutomaticDepthLaunch: true (Boolean, in watch app Info.plist) Entitlement verified in both the signed binary and provisioning profile watchOS 26.3, Apple Watch Ultra 2 Tested with: development build, TestFlight, and direct Xcode deploy. Watch restarted after each. The app does not appear in any case. T

Team ID: MB9VR977ND We have changed apple developer account for the our application, after changing account we have submitted app for notarization multiple times but all showing in-progress without any logs. do we need to wait until this passed from apple side ? does submitting many request has any issue ? Submission id: 8c5ac51d-bcd3-4fc4-9b38-671e5ea2bf14

I purchased the Apple Developer Program on March 26, 2026. Payment went through immediately. I have the invoice (UA31019584), the order confirmation (W1318171870), and €99 charged to my card. Apple had no problem taking my money within seconds. Five days later: Account status: Pending Portal still says Purchase your membership and asks me to pay again App Store Connect: inaccessible TestFlight: inaccessible I contacted Apple Developer Support on day one — both by email and callback request. I now have three open cases and have received exactly zero responses: Case ID: 102856462218 — Program Purchase and Renewal Case ID: 102853916886 — Program Purchase and Renewal Case ID: 102853919455 — Program Enrolment Not a single acknowledgment. Not even an automated we're looking into it. Nothing. My app is built and ready. I have testers waiting. I cannot distribute anything — not even through TestFlight — because Apple took my payment and then stopped responding. I see dozens of threads on this forum from deve

Hello Apple Developer Support / StoreKit Team, We recently observed a behavior regarding the appAccountToken in App Store Server Notifications v2 that seems to completely contradict the official documentation. According to the Set App Account Token documentation: The same appAccountToken continues to apply to renewal transactions if the customer upgrades, downgrades, or cross-grades the subscription. However, we encountered a scenario where an active in-app crossgrade resulted in an updated/overwritten appAccountToken inside the subsequent JWSRenewalInfoDecodedPayload, despite our backend never calling the Set App Account Token REST API. Our Observation: A user subscribes to our 1-month plan (Product A). Apple generates an originalTransactionId bound to their initial appAccountToken (Token A). Later, a crossgrade to a 1-year plan (Product B) is initiated from within the app while the user is logged into a different account in our system (Token B), but using the same underlying Apple

Hi, My app status is currently “Ready for Distribution”, but it still hasn’t appeared on the App Store and I’m not sure what is blocking the release. In App Store Connect, I have already completed: • Agreements, Tax, and Banking (all active) • Pricing and Availability (countries selected) • Automatic release is enabled However: • My Digital Services Act (DSA) status is still “In Review” • I am also in the process of changing my account from Individual to Organization At this point, I’m not sure if the delay is caused by DSA review, account type change, or something else. Has anyone experienced a similar situation? Is there anything else I should check or complete to make sure the app goes live? Apple ID: 6760753842 Thank you.