Hello Apple Developer Community, I am looking for guidance regarding an Apple Developer Program organization enrollment issue. I am enrolling as a Company / Organization for my US LLC. My organization has a valid D-U-N-S Number, and Apple Developer's D-U-N-S lookup successfully recognizes my company information. I also received confirmation from Apple Developer Relations that my D-U-N-S information can be used for organization enrollment. However, my organization enrollment was declined without a clear explanation. During the previous review process, there was also a technical issue with my company email server, and I may have missed some communication from Apple Developer Support. The email issue has now been resolved. I am the founder and authorized representative of the company, and I can provide any required company documents or verification information. Has anyone experienced a similar situation where: D-U-N-S verification was successful, company information matched, but organization enrollment was still declined? Any advice on how to request a proper manual review would be appreciated. Thank you.

Hello Apple Review Team, I respectfully request a review of the decision to terminate my Apple Developer account. I was very surprised to receive the termination notice because I have not engaged in any fraudulent, dishonest, or deceptive activity. I am the only person who uses this developer account, and I have never shared, sold, or transferred it to anyone. The only application I have been developing is DEM Vakit Quran-Ezan, which is my own project. I created and maintained this application myself. I have not made any suspicious changes to my app, and in fact, I have not even submitted an update for more than two weeks before receiving the termination notice. I sincerely do not understand what action or behavior Apple considers to be “fraudulent conduct.” If there has been a misunderstanding or an error in your detection systems, I kindly ask you to review my account again and explain the specific reason for this decision. I have always tried to follow the Apple Developer Program License Agreement and the App Store Review Guidelines. If additional information or verification is required, I am fully willing to provide it. Please reconsider this decision and allow me the opportunity to continue developing my application. Thank you for your time and consideration. Sincerely, Izzet Umit ONEN

Hi all, I'm running 2 macOS VMs on a bare-metal Mac (host is also macOS). I'm seeing inconsistent iMessage sign-in behavior depending on the Apple ID type and whether it's bare metal or virtualized: Managed Apple ID (ABM-issued): signs into iMessage fine on the bare-metal host. Same Managed Apple ID: fails to sign into iMessage inside the VM on the same physical machine. Personal/basic Apple ID: signs in fine in the VM without issue. Has anyone run into this specific combination — MAID working on bare metal but not inside a VM, while a personal ID works fine in both?

Hi everyone, I’m having an issue with my Apple Developer Program membership and App Store Connect access. My Apple Developer Program membership appears to be active. I received confirmation from Apple that the membership was approved and that the payment was successfully processed. However, when I try to sign in to App Store Connect with the same Apple Account, after completing two-factor authentication, I still get this message: “To access App Store Connect, you must be an individual or team member in the Apple Developer Program, or invited by an individual to access their content in App Store Connect.” It has been nearly a week since the payment settled at my bank, but App Store Connect still does not recognize my account. I contacted Apple Developer Support several times, but only received a canned response that only confirmed the advisor didn't actually read my ticket, and walked me through the purchase process. I've already paid. I'm already enrolled. I just have no access to my account. Has anyone experienced this before? Is there an additional activation step, account linking issue, or App Store Connect setup step that I might be missing? I would really appreciate any advice from the community or any Apple Support Advisors that may be seeing this. Thank you.

Hello everyone, I'm looking for some advice regarding the Apple Developer account migration process. Around 2–3 weeks ago, I submitted a request to convert my Apple Developer account from an Individual account to an Organization account. Since then, I have contacted Apple Support several times and have followed all the instructions they provided. However, the migration is still in progress, and I haven't received any update about the expected completion date. I would like to ask the community: How long did your account conversion take? Is 2–3 weeks considered normal for this process? Has anyone recently completed this migration? If so, how many days or weeks did it take? Is there anything I can do to help speed up the review, or is it simply a matter of waiting for Apple's team? For context: My business is already registered. All requested information has been submitted. I'm currently waiting for Apple to complete the account conversion. I'd really appreciate hearing about your experiences or any advice. Thank you!

I'm a third-party MDM developer using the Automated Device Enrollment (DEP) cloud service API. My flow is the standard token exchange: I upload my public key to Apple Business Manager, download the encrypted server token, and store the resulting OAuth credentials (consumer_key, consumer_secret, access_token, access_secret) to authenticate and fetch device information. Recently I've started seeing authentication failures on tokens whose access_token_expiry still has 6+ months of validity remaining. The credentials were working fine and then began getting rejected, with no change on my side. My questions for anyone who has seen this: Has anyone else observed DEP/ADE server tokens being rejected well before their stated access_token_expiry? What are the known triggers for early invalidation? (e.g., the ABM user who created the MDM server being deactivated or having a role change, the token being re-downloaded/regenerated, edits to the MDM server record, or Apple-side session invalidation.) Is there a supported way to detect that a still-unexpired token has been invalidated, other than catching the auth failure at request time? I want to confirm whether this is expected behavior tied to the ABM account/server lifecycle rather than the token's expiry date, so I can handle it correctly (i.e., prompt for a token re-download) instead of treating it as a bug. Any confirmation, similar reports, or official guidance would be appreciated. Thanks.

Case ID: 102924093872 Case ID: 102924089648 Hi Apple Support Team, I’m reaching out regarding a critical issue that is blocking my app testing and affecting hundreds of users. I cannot receive the two-factor authentication code for my Apple Developer account. My mobile operator has confirmed that SMS messages from Apple are not reaching their network at all. I also receive no calls. Since my account is not logged in on any device, SMS is the only way I can verify my identity - and it’s not working. I have already submitted two support cases but have not received any response yet. Here is the impact this is having right now: • 250+ people are waiting to get access to test my app • 400 users are already using the app • I cannot sign the new agreement that appeared in App Store Connect • Because of this, TestFlight is completely blocked - both the 10,000 user limit and the 100 user internal testing • Even when I add someone to my team and grant them access, it still doesn’t work for them either I have been building this app for almost 7 months. We are in the final testing stage before I plan to release it for sale. Every day without access is a day my users are waiting and I cannot move forward. I am asking you to please help me resolve this as quickly as possible. I really need your support right now. Thank you so much for your time. Best regards, Tata

Hello Apple Developer Support / Community, Our company's iOS app launch is currently paralyzed due to an automated enrollment block, and we are facing intense customer backlash because our Android version is already live. We urgently need an Apple representative to reset our enrollment status. The Situation: Originally, we started developing our app under a temporary legal entity (Homeflow BV) while our final corporate entity (Luo BV) was being legally formed. We initially opened Case 102912721623 to transfer the account from Homeflow to Luo. However, Developer Support informed us that because Luo is not acquiring Homeflow, a simple transfer isn't permitted. Accepting this, we decided to do it the right way: we abandoned the transfer, unlinked the primary Apple ID (s.aerts@...) from the old Homeflow account, and attempted to enroll Luo BV from scratch as a brand new Apple Developer Program member. The Blocker: When we attempt to enroll the new entity, we are immediately hit with the error: "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time." It seems our attempt to clean up our accounts and start fresh has triggered an automated security block. We are stuck in a catch-22: we can't transfer the old account, and the system won't let us pay for a new one. Business Impact: • We are a registered energy provider in Belgium • Our Google Play app is live, but our Apple users are entirely blocked from managing their energy contracts. We literally have households where one partner can use the service and the other cannot. • We cannot publish under the old Homeflow entity as it exposes private residential data. Could an Apple representative please clear this security block so we can finalize the enrollment of Luo BV and get our app to our customers? Thank you, Sam Aerts Luo BV

The new Device Management Service APIs provide support for creating and updating MDM servers programmatically, including updating the public key. However, we could not find a documented API workflow for retrieving, downloading, or renewing the associated Device Management Service token after a public key update. Could you please clarify whether there is an API-supported method for managing the server token ? If such functionality is not currently available, we would like to request support for token management APIs, as this would help enable fully automated MDM onboarding and certificate rotation workflows.

Hello everyone, Back on March 2023, Apple made the payout to our Wise bank account, however by some internal reason we decided to return this payment back to Apple and send it to another bank account and this was the biggest mistake I've ever made So, when Wise received funds we clicked on "cancel" and send it back to the sender. We expected that funds would return to Apple within 3-4 working days, but more than 5 months passed and Apple still can't find this money. And the weirdest thing is that Apple does not answer my emails. Does anyone know what to do in this case? What I've already tried: Write to Apple email support inside of the Apple dev account (more than 50 emails are sent and no reply) Called Apple global phone support (they can't help) Called Apple UK finance support (after several questions about my money and where are they the representative simply dropped the phone (Can't share how I was shocked didn't expect that this is possible when your working with Apple)) Wrote an email to Wise (and they gave all confirmations that they refunded money back to the sender) Wrote an email to db (the bank that Apple is using)(But they answered that they are not going to help) Long story short Apple do not want to send me my 57k EUR because they can't and do not want to find them... For Apple representatives that want to help please reply to email - Payments and Financial Reports (89JF8QQ45W); Case-ID: 1998672

I am currently working on mdm.push-token status item subscription via the DDM User Channel while testing on Beta OS 27. I have observed that the User Channel subscription consistently returns the device's push token rather than a unique user-specific push token. This behaviour is persistent across both macOS and Shared iPad environments. Before I conclude that this is a bug, I would like to clarify if this is the expected behaviour for the DDM User Channel. If so, could anyone provide guidance on the correct or alternative method to retrieve a unique, user-specific push token within the DDM framework to ensure proper notification routing? I have submitted a detailed report with a sys diagnose log via the Feedback Assistant (FB ID:FB23214856). Any insights or documentation references would be greatly appreciated.

Hello, I forgot to renew my Paid Apps Agreement when the previous one expired. As a result, all of my In-App Purchases and subscriptions became unavailable. I have now signed the new agreement, and it appears as active in App Store Connect. However, my In-App Purchases are still unavailable and purchases cannot be completed in my apps. Is there a propagation delay after signing the agreement before In-App Purchases become available again? Does Apple need to perform any manual action on their side after the agreement is renewed? If there is a delay, how long did it take in your experience? My products are still marked as "Ready for Sale" and everything else appears to be configured correctly. This issue is currently affecting live apps and preventing customers from making purchases, so I'm trying to understand whether I should simply wait or contact Apple Support. Thanks for any insights.

Since weeks I am waiting for my enrollment. I Receive E-Mails telling me "To complete your enrollment, please agree to the terms of the Apple Developer Program License Agreement . " When I click that Link (https://developer.apple.com/enroll/status/) there is not button, checkbox or link to agree to the terms. I do have an Enrollment ID: ZW------- which is written there Has anybody an idea where I should go to do that? HELP, my time is running out

We would like to enforce the use of Managed Apple IDs on company-owned devices. At the same time, users should be able to install free applications on their own without requiring administrators to deploy every app through MDM, as this creates additional administrative overhead. Why is this required? The primary objective is to ensure that company-owned devices are used only with corporate-managed accounts and to prevent corporate data from being synced, backed up, or transferred to employees' personal iCloud accounts. This helps protect organizational data and reduces the risk of company information remaining accessible after an employee leaves the organization or stops using the device. We are looking for a solution that enforces Managed Apple ID usage while still allowing users the flexibility to install free apps independently.

I'm a solo developer and owner of my companies account. I'm trying to sign on to my Mac so I can use my developer account to get a certificate for wallet use and to select the correct developer account for applications in Xcode. I'm am brand new to all this so apologize if I'm missing the simple solution. I'm not able to edit the roles of my developer account but being an Admin I should already have all the necessary access...I think. I get an error when trying to logon as a work account: Searching for the long error doesn't provide a solution in the forum or through search engines. AI says to check the roles.

Hi, we're urgently trying to resolve the changing of our account membership details. We need our app developer name to match our business name as it's currently wrong. All the information can be found under the case number 102893432961. Could this please be urgently looked into?

Hello, My Paid Apps Agreement has been stuck in "In Process" status since May 16, 2026 — now 9 days with no resolution. I have received no emails from Apple regarding this The agreement has not been rejected The system does not allow me to make any edits I have contacted Apple Developer Support twice with no real response

Hello everyone, I’m posting here because I’m waiting for an update regarding my Apple Developer Program enrollment. My enrollment currently shows: “Your enrollment is being processed.” My Enrollment ID is: 35QVL65M9K I submitted my enrollment several days ago and I haven’t received any email updates or requests for additional information yet. I wanted to ask if anyone from Apple Support or a community admin could please check my case status, or let me know if anything else is needed from my side to continue the review. If additional documents or verification are required, I’m happy to provide them. Thank you very much for your help.

Hello everyone, We’re currently facing an issue with an existing Apple Developer Organization account tied to our company. The original account holder is no longer accessible/unavailable, and our organization needs ownership transferred so we can continue deployment and App Store operations. Over the past ~4 weeks we have: Submitted a CEO-signed authorization letter Contacted Apple Developer Support multiple times via phone/email Had the case escalated to a senior technician/team Been told we would receive a callback within a week However, we still have not received follow-up communication or resolution, and our app launch is currently blocked because we cannot access the organizational developer account. We are considering temporarily enrolling under an Individual Developer account to continue deployment while the organizational escalation remains pending. A few questions: Has anyone successfully gone through a manual organizational account holder reassignment? What was the actual timeline for resolution? Is there a more effective escalation path to Developer Program Operations? Would enrolling as an Individual account create issues later when transferring the app back to the organization account? Any insight or recommendations would be greatly appreciated. Thank you!!!

Hi, We're implementing a DDM-capable MDM server. A DEP-enrolled, supervised iPad (iOS 26.4.2) successfully completes manifest synchronization but never proceeds to fetch the individual declaration bodies. Looking for guidance on what we might be missing. Observed flow (from our server logs): We enqueue a DeclarativeManagement MDM command and APNs-wake the device. The command body is: RequestTypeDeclarativeManagement (no Data field) Device acknowledges the command on the Connect endpoint (Status=Acknowledged). Device calls CheckIn with: MessageType = DeclarativeManagement Endpoint = tokens We respond 200 with: { "SyncTokens": { "DeclarationsToken": "", "Timestamp": "2026-05-19T..." } } Device calls CheckIn with: MessageType = DeclarativeManagement Endpoint = declaration-items We respond 200 with: { "Declarations": { "Activations": [{"Identifier":"...","ServerToken":"v1-..."}], "Configurations": [{"Identifier":"...","ServerToken":"v1-..."}], "Assets": [], "Management": [] }, "DeclarationsToken": "" } ---- Nothing further. ---- No request for Endpoint = declaration/activation/ No request for Endpoint = declaration/configuration/ No status report on Endpoint = status The MDM channel is healthy. The same device responds normally to non-DDM commands (DeviceInformation, etc.) immediately before and after this flow. Questions: Is an empty "Management" array acceptable in the declaration-items response, or is at least one declaration (e.g. com.apple.management. organization-info) required before the device will proceed to fetch declaration bodies? The DeclarationsToken returned in step 3 (tokens) and step 4 (declaration-items) are byte-identical. Is that correct, or should they differ in some way? Are there any additional preconditions for the device to begin fetching declaration bodies after receiving the manifest -- e.g. a specific Activation->Configuration linkage we might be missing? Is there a server-side log signal Apple can suggest we look for, or a way to see why the device decided not to fetch? Activation payload sample we publish: { "Type": "com.apple.activation.simple", "Identifier": "...", "ServerToken": "v1-...", "Payload": { "StandardConfigurations": ["<configuration-identifier-from-step-4>"] } } Configuration payload sample we publish: { "Type": "com.apple.configuration.softwareupdate.settings", "Identifier": "...", "ServerToken": "v1-...", "Payload": { ... softwareupdate settings ... } } Any pointers appreciated. Happy to share full server-side logs / payloads if useful. Thanks.