My switch from an individual to an organization enrollment (ID: 484G9X5T3Z) has been pending for more than seven weeks, and recent follow-up requests to Apple Developer Program Support for status (case numbers: 102880166579 and 20000117404816) have gone unanswered. In the meantime, I have paid for the renewal of my subscription but since member benefits are suspended during migration I haven't been able to use it for more than a month. Please Apple, let me know if there is anything I need to do to get my enrollment switch completed.

Hello, I am writing to ask whether this delay is normal or if anyone has experienced a similar situation. I enrolled in the Apple Developer Program and completed the annual payment on February 4, 2026. On February 10, I received an email requesting identity verification. I uploaded the front side of my ID on February 11 through the official verification link. Since then, I have not received any confirmation or status update. On February 15, I contacted Developer Support through the website. The support page indicates that responses are usually provided within two days. However, I have not received any reply yet. I also chose the call option and was advised to wait a few more days. On February 20, I followed up again under the same case. As of today (February 25), my enrollment is still pending and I have not received any update. Has anyone recently experienced a similar delay in identity verification? Is this timeframe considered normal? Thank you.

I’m having a weird issue that I wonder if someone might be able to shed some light on. I’m a fully registered Apple Developer. Paid the $99 a few months ago and have since published 2 iOS apps. So fully registered - this part is important to remember. Also, only one AppleID that I’ve used for years. Zero chance of the issue being a wrong Apple ID. The issue, I can’t see the Mac OS 27 beta or iOS 27 beta being available to download on any of my devices. 2 fully up to date Mac’s (mini / m5 air) running the latest production version of Tahoe and an iPhone 17 pro max, running the latest production version of iOS. When I go to the beta section in software updates all I see is the iOS 26 / Mac OS 26 public betas. Nothing about 27. I have signed in / out of beta updates, no change. Nothing to sign on the developer site. Anyone ever see this before? I have no idea what to do. I emailed apple developer support but who knows when I’ll hear back.

Currently the Apple Developer Forums RSS feeds only include the latest 20 items. It would be nice if it supported RFC 5005 to allow accessing older posts through the feed. FB23356085 https://github.com/feedback-assistant/reports/issues/807

It's really frustrating even after having 15 days of communication we are still not able to enroll in the program. we tried reaching out to the support but showing no empathy at all. Our case number (102902932662) if anyone from apple seeing this pls provide the necessary support.

Hi, Since today I'm unable to stay logged in to App Store Connect. Every time I click on an app, it immediately redirects me back to the login page. Things I've already tried: Cleared cookies and cache Multiple browsers (Edge, Safari, Chrome, incognito mode) Mobile app Different network (WiFi and mobile data) Checked appleid.apple.com — no suspicious devices or logins Apple System Status shows everything green. No account changes were made recently. Is anyone else experiencing this today? Could this be an account-level session issue? Thanks

How can I enable an external display in the Device Hub via Xcode 27, similar to the external display option previously available in the Simulator?

Trying to enroll my LLC as an organization, fully blocked at the account level. Web Enroll redirects to /enroll/identity/status with "could not be completed at this time" instantly, before any org form. The Apple Developer app says "Enrollment through the Apple Developer app is not available for this Apple Account." Already ruled out the usual: valid non-expired default card with correct billing address, no VPN, multiple networks/days, real legal name, 2FA on, US-based, valid D-U-N-S. Open support case since June 9, no resolution. This looks like it needs a manual account review to clear a flag. Can Apple staff help route this? Happy to share my case number privately.

Hey guys I am trying to enroll to apple developer program, but I am facing this issue from previous 1 week, I tried contacting the support but no one replied yet. If anyone knows the fix to it please help me resolve by replying to this post.

Hey guys I am trying to enroll to apple developer program, but I am facing this issue from previous 1 week, I tried contacting the support but now one replied yet. If anyone knows the fix to it please help me resolve by replying to this post.

Hello, I have been unable to install any development-signed app on any physical device for five months. Builds succeed, code signing passes locally, but every device rejects the app at install time with: Failed to verify code signature of .../extracted/MyApp.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) ApplicationVerificationFailed The app installs briefly, then iOS immediately removes it. This started right after my account (Team ID MB4DXDTDMT) was reinstated following a duplicate-account flag. Background: I had a personal account that was converted to a business account (Wakeout LLC), then created a new personal account, which Apple flagged as a duplicate and later reinstated. The signing failure began immediately after that reinstatement. Isolation already done (this is not a local-setup problem) I have run the full isolation sequence — including every step DTS typically asks for — and the result points squarely at the account/team, not my machine: New blank Xcode project, automatic signing, new bundle ID → same 0xe8008018. Brand-new macOS user account → same failure. Multiple Macs, fresh Xcode installs → same failure. Multiple iOS devices (iPhone 17 Pro, iPhone 15 Pro, others) → same failure. Different Apple ID / different developer team on the same Mac + same device → installs fine. This is the decisive one: the local environment is healthy; only Team MB4DXDTDMT is rejected. Xcode Cloud builds for this same team install fine. Apple's cloud signing trusts MB4DXDTDMT; the device-verification backend does not. That gap can only exist server-side. I have also: revoked/regenerated all certificates multiple times, deleted/recreated all provisioning profiles, cleared ~/Library/MobileDevice/Provisioning Profiles, cleared DerivedData and CoreDevice, removed device pairing records, re-paired devices, confirmed Developer Mode and correct system time. Simulators work. codesign --verify --deep --strict passes. Profile certificate SHA-1 matches the signing cert exactly. Entitlements match. Why I'm posting here This is the same failure documented in thread 755762, where Quinn concluded: "this seems to be tied to your primary developer account and only DevPrograms has access to those details." That matches my evidence exactly: the problem isolates cleanly to one team, and only DevPrograms can see the account-side state. I've already gone through Developer Support on this — an open case has been with them for about five months without a resolution, which is what convinced me the fix isn't something I can reach from the support side. I'm posting here in case a DTS engineer can confirm the diagnosis and point me to the right path. Question for any DTS engineer: given that the failure isolates to a single team — different teams sign and install fine on the same Mac and same device, and Xcode Cloud builds for this same team install fine — can you confirm this is an account-side signing-trust state that has to be reset by Apple, and what's the most direct way to get that reset actioned? Happy to attach a sysdiagnose, full console output, or codesign -dvvv dumps on request. Thank you.

Is there a known workaround (other than forking) for watchOS builds in Xcode 27 that depend on packages without a declared watchOS 9.0 floor? I depend on several Apple SPM packages with no minimum deployment target, such as https://github.com/apple/swift-algorithms. My project's minimum is 26.0. Xcode 27 will not build watchOS targets with these packages because watchOS 8.0 is below its range of supported targets. /.../SourcePackages/checkouts/swift-algorithms/Package.swift The watchOS Simulator deployment target 'WATCHOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 27.0.x.

Hi everyone, I’m looking for advice or shared experiences regarding the Apple Developer Program membership conversion process from an Individual membership to an Organization membership. I submitted my request more than two months ago, but the process still does not appear to have started. Current support cases: Case 102844790649 Case 102884491745 I have followed up multiple times, but several follow-up emails did not receive any response, which has made it difficult to understand the actual status of the request. I have already confirmed that: Two-factor authentication is enabled on my Apple Account My organization has a valid and publicly accessible website I am ready to proceed with the migration However, I still have not received confirmation that the migration has officially begun. I would appreciate advice from anyone who has gone through this process: Is it normal for the Individual → Organization membership conversion to take more than two months? Did you receive confirmation when the migration officially started? Were there any escalation methods that helped move the process forward? Is it safe to continue publishing apps while the migration request is pending? Any advice or shared experiences would be greatly appreciated. Thank you.

Posting here after a month of going in circles through Developer Support email, in the hope an Apple staff member can review or escalate. Timeline: Individual-to-organization migration submitted for Spentz LLC. Enrollment ID: S4QC6PLPTT. During the migration my active signing certificate was revoked. I have been unable to produce ANY builds (EAS or device) for over 30 days. This is the core blocker. 20 May: advisor confirmed my documents were received and forwarded to the review team, and that the team would contact me directly if anything further were needed. Nothing further was requested. 29 May: automated email warning the enrollment would be withdrawn within 7 days if requested info wasn't received but no email has ever specified what is outstanding or where to send it. This directly contradicts the 20 May confirmation. Callback requested only to be left on hold for over an hour before giving up What I'm trying to resolve: (1) confirmation of whether anything is genuinely outstanding from my side and, if so, what and where to send it; (2) assurance the withdrawal timer won't fire while my documents are confirmed with the review team. If any Apple staff can look at S4QC6PLPTT, I'd be grateful. Happy to provide anything needed. This is the sole blocker on a scheduled launch. Topic: Developer Tools & Services SubTopic: Apple Developer Program

Herkese merhaba, 19 Haziran 2026 tarihinde Apple Geliştirici Programı üyeliği satın aldım. Ödeme banka hesabımdan başarıyla tahsil edildi. 20 Haziran'da Apple'dan bir e-fatura ve siparişimin işleme alındağı söylemeden başka bir e-posta aldım. Ancak, Apple Developer hesabımda oturum açtığımda, hala “Enroll Today” düğmesini görüyorum. Hesabım ucretsiz bir geliştirici hesabına benziyor ve ucretli üyelik özelliklerine erişemiyorum. Satın alma işlemi için kullandığım Apple Hesabıyla oturum açtım. Üyelik ayrıca Apple Hesabımın abonelikler bölümünün altında da görünmüyor. Bu konuyu daha önce yaşayan var mı? Aktivasyon ne kadar sürdü ve bunu çözmek için ne yaptınız? Teşekkür ederim.

Hi, I tried paying for apple developer program. It keeps saying authorization failed. I tried 3 different credit cards. My visa and mastercard and 1 debit card and it still fails. I called my bank and there seems to be no issue on their side. I am able to pay apps and subscriptions on my credit enrolled in my account but it is failing in apple development program. I hope anyone can help. I need to enroll in app development program as soon as possible. I tried emailing support twice already still no response :( Thank you

Hi, For the questions the original posts they need to be notified by default. Presently unless the user taps on Opt in they wouldn't be notified. Having good default behavior is a big part of good design / usability. If user posts something then there is reason to believe that that the person would like to be informed when there is response to that thread. If the user wants to opt out that could be made as a button, usually a person would want to opt out only much later when the original poster has got response and doesn't want any more. Confusion There is an opt in banner on top of the thread and there is a bell icon below the post, not sure what the difference is. The banner is barely visible on dark mode as that is also black The whole experience causes confusion and lacks confidence whether the user will be notified or not. Forum participation Generally user participation in the forum is low. So by making opt in for the posts the user has posted that makes the participation even lesser even when the original poster wants to participate. Proposal By default any post the user posts, the bell icon would be pressed (turned on) for that post, meaning the poster will get notified If the user wants to opt out of the thread the user can press the bell icon to turn off notification for that thread. For all the posts that the user hasn't posted by default the user is turned off Please provide an option for users to turn on / off notifications on specific topics / tags, this can be helpful when some developer / Apple engineer wants to actively participate / follow a specific topic. Remove the banner on top seems and stick only to the bell icon.

I’m seeing a reproducible issue in both Xcode 26 and Xcode 27 where Coding Assistant appears to stop autocompleting when a project contains a larger number of Swift Package dependencies. Symptoms: Autocomplete suggestions from Coding Assistant stop appearing. File targeting with @ stops working. The issue typically appears shortly after opening the project If I start a brand-new chat immediately after opening the project, Coding Assistant sometimes works briefly before failing Reducing or removing Swift Package dependencies fixes the issue I’ve created a sample project that reproduces the problem and have also filed Feedback Assistant report: FB23341243 The issue seems related to package count or project complexity rather than any specific package, although I haven’t yet identified the exact threshold that triggers it. Has anyone else run into this or has anyone found a workaround?

Hello, I am looking for guidance on how to pre-provision TCC permissions for automated desktop app testing on the macOS 27 beta. We have maintained a CI testing setup by saving snapshots of VMs with pre-configured user TCC databases. This allowed our UI tests to run without being blocked by permission prompts. This included permissions like screen recording, full disk access or apple events. On the macOS 27 beta, this workflow appears completely broken. While the system TCC database seems to function as it used to, the user TCC database has been moved into a ProtectedSystem container. Direct modifications to the user database now seem impossible. Is there any officially supported way to pre-provision user-level TCC permissions on macOS 27 VMs for automated CI environments? Is Apple's intention here that the system DB is the only one that's actually editable (with SIP disabled)? How does Apple recommend CI platforms handle user-level permission prompts in headless or automated VM environments moving forward? Any insights or recommended alternative workflows would be greatly appreciated. Thank you!

iPhoneSimulator.app used to have the ability to show an external display / CarPlay display, but this feature does not appear to be available in DeviceHub.app, making it difficult (/impossible :( ) to test CarPlay features from the simulator.