I enrolled in the Apple Developer Program and my payment was charged in April 2026 (annual membership, paid in full). Shortly after, I had to verify my identity/enrollment. I replied with the requested information but never received any response. I followed up again on June 20 and still received no reply. My account has been showing "Pending" this whole time, i sent over +3 emails to support and i never get a reply and im speaking about now almost half of year is gonna be past, and the dashboard keeps prompting me to "complete your purchase" even though the payment already went through months ago. I've been charged but cannot access my membership. Can anyone from Apple advise how to get an enrollment that's stuck in verification reviewed, or point me to the right contact? I've already emailed Developer Support twice with no reply. Thank you.

I'm trying to enroll in the Apple Developer Program. Following Apple's instructions, I developed an app on my Mac, signed in with the Apple ID that I want to use for the Developer Program, and attempted to enroll. However, I consistently receive the following error: "Unable to continue. Contact support at https://developer.apple.com/contact/." I contacted Apple Developer Support and a support ticket (102918021274) was created during the first week of June 2026. Since then, I've provided all the requested information, including screen recordings and other evidence. The support team later informed me that the case had been escalated to the Operations team and was being handled as a priority. It has now been more than two weeks since the escalation, and I still haven't received any update or resolution. Has anyone else experienced a similar issue? Is it normal for the Operations team to take this long to investigate an enrollment problem after all the required evidence has already been provided? Also, does Apple have any service-level agreement (SLA) or expected turnaround time for resolving Developer Program enrollment cases? Any insights or suggestions from others who have gone through this process would be greatly appreciated. Thank you.

Nothing changed on my end, Pro subscription still active, but Xcode 26.5 (17F42) simply does not want to log into Codex anymore. It opens the OAuth flow and after finishing and closing the window, it still says "Not Signed In". Codex login works everywhere else, including the Codex app. What to do?

Hello, I'm requesting a status update on our Apple Developer Program Organization enrollment. Enrollment ID: 7A7WRTQW97 Organization: SWISS KEY TRADING AG (Switzerland, Commercial Register No. CHE-455.888.722) Enrolled as: Organization Applicant role: IT Responsible, enrolling on behalf of the company We initially received a document verification rejection citing (1) a photo ID mismatch and (2) an employment verification letter missing official letterhead and signature. We have since resubmitted corrected documentation addressing both points. The enrollment has been showing "Your enrollment is being processed" since 08.07.26. Could someone let us know if any further information is needed, or confirm expected next steps ? Thanks in advance and have a great day !

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574

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!

We need guidance regarding the Python runtime bundled with Apple Command Line Tools. Environment: macOS Tahoe 26.5.2 (25F84) Xcode 26.6 (17F113) Device type: Mac Command Line Tools Python path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/ Version confirmed locally with: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/bin/python3 --version Output: Python 3.9.6 Our vulnerability-management platform, Qualys, reports this Apple Command Line Tools Python runtime as vulnerable under QID 387170, referencing CVE-2022-4303 and CVE-2023-0286. The detection points to: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/Resources/Python.app My understanding is that this runtime is bundled and managed by Apple as part of Command Line Tools, and that manually replacing or modifying this framework is not a supported remediation path. Installing a separate standalone Python version also does not remediate the finding at this Apple-managed path. Could Apple or the community confirm the supported approach for this scenario? Specifically: Is Python 3.9.6 intentionally bundled with the current Command Line Tools release for this macOS/Xcode version? Has Apple applied security fixes or backports to this bundled Python runtime that are not reflected in the upstream Python version number? Is updating Command Line Tools/Xcode the only supported remediation method for this component? Is manually replacing or modifying the bundled Python framework unsupported? Is there any known mitigation or official guidance for vulnerability-management exceptions while waiting for an Apple-provided update? I have also filed this through Feedback Assistant: FB23893693. Any official Apple guidance or reference to existing documentation would be very helpful, as we need to provide an auditable response to our internal security and audit teams.

I am developing a large iOS application with an extensive UI test suite (hundreds of UI test scenarios). After upgrading our CI runners to macOS Tahoe 26, we started observing an intermittent issue where an iOS Simulator may operate normally for many successful application launches before unexpectedly entering a persistent degraded state. Once this occurs, every subsequent application launch crashes inside dyld before reaching our application’s main(). The degraded state persists until the simulator device is reset This causes UI tests to hang and eventually timeout. Business impact CI/CD jobs frequently timeout (90+ minutes per failed run) Significant loss of CI capacity Difficult to maintain reliable quality gates At our scale, this has become a serious issue affecting release confidence and overall engineering productivity. Technical details Crash report MyProject-2026-07-13-125307.ips — a crash report from a CI Demo project dyld_crash_demo — a minimal reproducible project demonstrating the relevant dyld execution path. The project intentionally returns errors from system functions along the shared cache initialization path to demonstrate that dyld continues execution until DyldSharedCache::getUUID(), where it subsequently crashes. Simply open the project and run it in iOS Simulator 26.2. Environment Component Version macOS Tahoe 26.x Xcode 26.2, 26.5 iOS Simulator 26.2, 26.5, 26.6 Architecture Apple Silicon dyld 1378 dyld_sim 1335 What we have ruled out multiple Xcode versions multiple macOS 26.x releases multiple iOS Simulator runtimes multiple simulator devices UI tests with parallel execution disabled deleting the simulator dyld shared cache recreating simulator devices application-specific issues (the crash happens before main()) The issue is still reproducible. Investigation The earliest observable failure sequence is consistently: shared_region_check_np() → "Cannot allocate memory" (ENOMEM) Shared cache mmap(0x180000000, ...) → EACCES The shared cache region remains unmapped DyldSharedCache::getUUID() reads 0x180000058 EXC_BAD_ACCESS (Translation fault) The crash occurs before any application code executes. The first faulting instruction belongs to DyldSharedCache::getUUID(), while the shared-cache region is still unmapped. Published dyld source analysis Relevant execution path: loadDyldCache() ↓ mapSplitCachePrivate() ↓ preflightCacheFile() Based on the published sources of dyld-1378, this appears to be the execution path leading to the observed failure. After the loadDyldCache() function failed to load the cache, dyld continued execution anyway and moved on to calling the DyldSharedCache::getUUID() function, where it subsequently failed. Additional observations Once the simulator enters the degraded state: simctl spawn succeeds. simctl launch crashes inside dyld before reaching main(). During our experiments, both processes were created by the same launchd_sim instance Before dyld::_dyld_start, both processes expose the same virtual address layout, including an unmapped shared-cache region (0x180000000–0x300000000). Current workaround As a temporary mitigation, we launch the application with DYLD_SHARED_REGION=avoid In our environment, this completely avoids the launch failures. However, this mode appears to be undocumented and intended primarily for debugging. We are concerned that it may change or stop working in future macOS or Xcode releases, so we are reluctant to depend on it in our production CI infrastructure. Questions 1. dyld Is it expected for dyld to continue dereferencing the shared-cache header after both the shared-region initialization and the shared-cache mapping have already failed? Execution appears to continue into: loadInfo.loadAddress->getUUID(cacheUuid) which results in an access to an unmapped address. The attached demo project reproduces this behavior by simulating failures from the shared-cache initialization path. Is there an expected fallback behavior for this situation or is continuing into DyldSharedCache::getUUID() the intended behavior ? 2. Simulator state Why does a simulator that initially launches applications successfully eventually enter a state where every subsequent launch fails while the shared cache can no longer be mapper? The earliest related system log we have found is: vm_shared_region_start_address() returned 0x1 Is this a known CoreSimulator or macOS Tahoe issue? If so, is there a supported workaround or recommended long-term solution besides DYLD_SHARED_REGION=avoid? Any guidance would be greatly appreciated.

Summary On Xcode 26.6 (17F113) / Swift 6.2, a Debug build (-Onone) crashes at runtime when comparing UIScene.ActivationState inside a closure passed to Array.first(where:). The exact same code runs fine when built with optimizations (-O / Release). This looks like an -Onone code-generation (miscompile) bug rather than a logic error in the app. Environment Xcode: 26.6 (17F113) Toolchain: Swift 6.2 (Apple default toolchain) Optimization: SWIFT_OPTIMIZATION_LEVEL = -Onone (Debug scheme) Deployment target: [ iOS xx.x ] Run destination: [ Device / Simulator — model, OS version ] Configuration: also reproduces in a fresh checkout after Clean Build Folder + DerivedData wipe Steps to Reproduce Add the following to any app and call it early in the launch path (e.g. from an async context / Task during startup): import UIKit enum ScreenUtil { static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } // Crashes here in Debug (-Onone) on Xcode 26.6 (17F113) return scenes.first { $0.activationState == .foregroundActive } ?? scenes.first } } 2. Build and run with the Debug scheme (-Onone). 3. The app crashes as soon as keyScene is evaluated. Expected keyScene returns the foreground-active UIWindowScene (or the first scene), identically to the optimized build. Actual Immediate crash when the closure evaluates $0.activationState == .foregroundActive. UIScene.ActivationState is an Objective-C-imported (NSInteger-backed) enum, and the failure appears tied to how its value is handled under -Onone. The crash surfaces inside Swift concurrency resume plumbing because keyScene is reached from an async context at launch. Representative frame: (1) await resume partial function for partial apply forwarder for reabstraction thunk helper ... @isolated(any) @callee_guaranteed @async () -> (@out τ_0_0) ... -> ldr x0, [x22, #0x8] ; faults here br x0 ; preceding: bl swift_task_dealloc Reproducibility - Debug (-Onone): crashes 100% - Release (-O): works correctly Workaround Rewriting the closure comparison as an explicit loop avoids the crash: static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } for scene in scenes where scene.activationState == .foregroundActive { return scene } return scenes.first } Notes A sysdiagnose / crash log and a minimal sample project are attached via Feedback Assistant (FB[ number ]). Happy to provide additional details.

Hi all, I've hit a reproducible issue where the presence of the SwiftUI instrument in a template prevents any data from being recorded, including from the other instruments in the same template. Removing the SwiftUI instrument immediately restores normal recording. Environment Host: macOS 26.4.1 (25E253), Mac mini Xcode / Instruments 26.4.1 (17E202) Device: iPhone 17, iOS 26.4.2 (23E261) (physical device, USB-attached) Symptom Recording the same app, same device, same session, only varying the template contents: SwiftUI template (as-is) => All lanes empty across the entire recording Same template with the SwiftUI instrument removed => Data collected normally (Time Profiler samples, Hangs, etc.) So it seems not an issue with the SwiftUI lanes specifically being empty — including the SwiftUI instrument appears to silence the entire recording. Steps to reproduce Open Instruments → pick the SwiftUI template (or build a custom template that includes the SwiftUI instrument alongside, e.g., Time Profiler). Target the device, attach to the running app. Record for ~10s, interact with the app. Stop. Result: every lane is empty. Edit the template, remove the SwiftUI instrument, re-record with no other changes. Result: normal data appears in the remaining instruments. Questions Is this a known regression in Instruments 26.4.1 on iOS 26.4.x? Is there a workaround to use the SwiftUI instrument on this OS combo (different Xcode build, runtime flag, entitlement)? Does it work for anyone on iOS 26.4.x + Xcode 26.4.1, or is everyone seeing this? I can file a Feedback if confirmed as a bug — wanted to check here first in case I'm missing a setup step. Thanks!

I'm on a Mac. I have Xcode installed but it's not running, nor is the Simulator. And yet Mac pops up an alert asking, ""Allow ServiceExtensio to find devices on local networks?" Creepy! No you can't scan my network. What gives? And why not tell me your real name?

Individual Apple Developer Program account, Team ID 2779RW9TB8, membership active (all App Store Connect agreements, banking, tax, DSA now Active). Every notarization submission since 2026-07-09 is Rejected with statusCode 7000 "Team is not yet configured for notarization", issues: null. This is not a package problem: notarytool authenticates fine, the app is signed with a valid Developer ID Application cert (codesign --verify --deep --strict passes, hardened runtime + secure timestamp), and 7000/issues:null means the service rejects at the team level without evaluating the package (a signing issue would return "Invalid" with issues). Developer Support case 102938170713 has been unanswered for 11+ days. I've also filed FB23976939. Could an Apple engineer please escalate enabling Team ID 2779RW9TB8 for the Developer ID Notary Service? Recent submission IDs: 62b46f4c-3508-4bf9-b28c-e62eb94efd35, a10c8786-6193-4013-8b86-f81a5d173013.

Hello, I’m posting a new thread in case anyone has seen this before. My Apple Developer Program membership is paid and should remain active until March 10, 2027, but my account suddenly lost access to membership-related resources. Current symptoms: developer.apple.com/account shows “Join the Apple Developer Program” In Certificates, Identifiers & Profiles, I get: “Team ID is not associated with an active membership.” A few weeks ago, I received a “We need more information” email asking for ID and proof of address. I did upload the requested documents, and after contacting Developer Support in China, I uploaded them again as a second submission. Developer Support in China has confirmed that the issue is related to an additional identity verification review, and that my second submission was forwarded to the relevant internal team. My Team ID is: 84FV5VNGS2 My China Developer Support case number is: 102922928162 But after about 3 weeks, the account is still not restored. Has anyone had a similar case? If so: how long did it take? did Apple manually restore the membership / team linkage? was there anything else you needed to do besides waiting? Any similar experience would be appreciated. Thank you.

Case ID: 20000117609350 I've been stuck in the Apple Developer Program (Individual) enrollment process for several weeks and support has not been able to resolve it. Details: During identity verification, I attempted to upload my national ID, passport, and driver's license (multiple attempts, different lighting/settings). Every attempt failed with a message that the document could not be verified, despite the images being clear and valid. After these failed attempts, the enrollment/ID verification step became inaccessible. I now only see a payment screen — no active "Enroll" button. I submitted payment ($99) in good faith. It has now been a while with no activation. I created a second Apple ID and attempted enrollment again from scratch. The same identity verification failure occurred. I have submitted multiple email support requests referencing my Case ID. Each response has been the generic instruction to "go back and enroll through the Apple Developer app," which doesn't help since the enrollment step itself is inaccessible. Has anyone experienced this same loop and found a way to get it escalated to a human reviewer, or get a manual document upload option instead of the automated scanner? Any guidance on getting this routed to the Enrollment Operations / Identity Verification team would be appreciated.

Emoji handling (usually a sign of underlying Unicode bugs) is broken in Xcode 27, all betas: The issue doesn't exist in previous Xcode source editors. FB23969935

When will this be available? (Opencode + LMStudio + Qwen 3.6 27B) FB23978071

Hello, I am facing a critical issue with my Apple Developer Account verification process where an automated timer suspended my account despite submitting all requested documents on day one. Timeline & Details: I received a request from Apple to upload address verification documents with a 14-day deadline. I uploaded all requested documents on the very first day. While waiting for the review process to be completed on Apple's end, the 14-day window expired. Consequently, the system automatically suspended my account, disabling certificate creation and blocking development/distribution. I have open support tickets, but have not received a response yet. Case ID: 102944887663 Since this is an automated timeout caused by review delay, could someone from the Apple team please help escalate this Case ID to the Enrollment / Account Verification team? Thank you very much for your help!

delete

When I use Xcode to create an Xcode Cloud workflow through Xcode > Integrate > Create Workflow for App A, and later create another workflow for App B, both workflows appear only under App B in App Store Connect, under App B > Xcode Cloud > Builds. I would expect the first workflow to remain associated with and visible only under App A, while the second workflow should be associated with and visible only under App B. This worked as expected previously, but the behavior appears to have changed recently, and it is now causing my builds to fail.

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 and then basically stopped. Since then I’ve been left waiting without a clear resolution, even though I’ve tried to follow every instruction carefully. This has become really frustrating and exhausting. I’m not trying to do anything unusual — I’m just trying to enroll in the Apple Developer Program so I can publish my app, and instead I’ve been stuck in a loop for weeks. Has anyone here had the passport upload fail immediately in the Apple Developer app, especially after already providing documents directly to Apple Support? Did anything help move the case forward? Thanks a lot.