I created an new Apple developer account, completed enrollment by finalizing the payment and uploading my Passport, yet there has not been any correspondence or approval since 8 days and the dashboard still shows I need to complete the payment to enroll, while I have a transaction in my bank account and received the invoice+confirmation. Not getting any response via phone or email contact. Where can I reach out / what can I do? It's quite annoying as we're losing momentum.

Hello Apple, Just subsribed to the DEV Program and paid the $99 fee. But my account still says pending and to complete enrollment. Do I simply need to wait 1-2 business days before we can begin deploying our app? Please advise. Thank you, Ken

Order: W1480222859 Case: 102881078750 I submitted my National ID card on April 25, 2026. Received confirmation email that review would take 2 business days, but it has now been 5 days with no update. Account still shows "Purchase your membership." Please review my enrollment status.

Hello, My Enrollment ID: T7QXDY4LM6. I submitted application business days ago. However, the status remains ‘Pending’ ‘Your enrollment is being processed’ and I have not received any further instructions or payment link. This delay is significantly impacting our project timeline and business launch. I have tried to contact support via emails without success. Could Apple Developer Enrollment Team escalate this case for me right now please?

I have paid and uploaded my driving license and I have been charged. No enrolment confirmation and if I I visit again I'm only prompted to pay again. I have logged a case and contacted "support"who do not respond to emails and on the phone I have waited multiple times for 1hr+ and no-one picks up. "Normal"apple support say they can't contact apple developer support. I'm SO ANNOYED. 4 days of this now. no end in sight. now I can't even make a call back request as entering my number generates a "we cannot process this request"or similar message

Hi. I have submitted all required documents, and paid the yearly fee but now my Developer application on iphone and mac say that "Enrollment through the Apple Developer app is not available for this Apple account" and to visit website. When I visit website it wants me to pay again to continue. Is that normal? In my Apple subscriptions I can see it already active, and it for sure was paid, eg. deducted from my bank account

Order: W1480222859 Enrollment ID: M7TXT2MAAM Case: 102881078750 Submitted identity document but no update. Account still shows "Purchase your membership. (Your purchase may take up to 48 hours to process.)" Please review.

Xcode 26.3 MCP xcode-tools: RunSomeTests / RunAllTests response violates tool output schema (missing required errors per test) I’m using the MCP server “xcode-tools” shipped with Xcode 26.3 to run tests. Two tools fail consistently due to a schema mismatch: RunSomeTests RunAllTests Steps Call XcodeListWindows and get a valid tabIdentifier for my workspace. Call GetTestList with that tabIdentifier. This works and returns test identifiers like: ChatKitManagerCreationTests/testInitializesWithDependencies() Call RunSomeTests with tests = [{ targetName, testIdentifier }, …] (or call RunAllTests). Actual result The tool call fails with an MCP schema validation error like: Structured content does not match the tool's output schema: data/results/0 must have required property 'errors', data/results/1 must have required property 'errors', ... Why this looks like an xcode-tools bug According to the tool descriptor JSON for RunSomeTests / RunAllTests, each element of results[] is required to contain: targetName identifier displayName state errors (required, array of strings) But the actual response returned by RunSomeTests / RunAllTests appears to omit the errors field for one or more results (for passed tests it should still be present as an empty array []). Expected result RunSomeTests / RunAllTests always return structured content matching their declared output schema. In particular, every results[i] should include errors: [] when there are no errors. Environment Xcode: 26.3 macOS: Darwin 25.4.0 Workspace: Grocery.xcworkspace Scheme: GroceryCoreTests Active test plan: GroceryCoreTests Question Is this a known issue in Xcode 26.3’s MCP xcode-tools? Is there a workaround (e.g. alternative output mode, or reading a full summary file) until the schema/response is fixed?

On watchOS, the Developer Mode entry under Settings -> Privacy & Security is hidden by default and only appears after Xcode has attempted to connect to the watch as a development device. In my case, once Xcode triggers that surfacing, opening Settings -> Privacy & Security on the watch prompts for a 4-digit Screen Time passcode before granting access. No Screen Time passcode I set on the paired iPhone is accepted at this prompt, which prevents me from reaching the Developer Mode toggle to enable it. The passcode prompt only appears in this specific state. With no Xcode connection attempt (and therefore no Developer Mode entry surfaced in the menu), Settings → Privacy & Security opens normally on the watch with no prompt at all. Environment macOS: Tahoe 26.4.1 (Build 25E253) Xcode: 26.4.1 (24909.0.3) (Build 17E202) iPhone: iOS 26.4.2 Apple Watch: Ultra 3 running watchOS 26.4 All devices on release software (no betas). Xcode error Developer Mode disabled Domain: com.apple.dt.deviceprep Code: -28 Recovery Suggestion: To use [Watch Name] for development, enable Developer Mode in Settings → Privacy & Security. User Info: { DVTErrorCreationDateKey = "2026-04-30 09:38:57 +0000"; "com.apple.dt.DVTCoreDevice.operationName" = checkDeveloperMode; } Reproduction Pair Apple Watch to iPhone (paired fresh, set up as new, not restored from backup). Connect iPhone to Mac running Xcode 26.4.1. Before any Xcode connection attempt, open Settings -> Privacy & Security on the watch. The menu opens normally with no passcode prompt. There is no Developer Mode entry visible. In Xcode, attempt to use the Apple Watch as a run destination. Xcode returns the -28 / Developer Mode disabled error above and instructs me to enable Developer Mode in Settings -> Privacy & Security on the watch. After this attempt, the Developer Mode entry is surfaced in Settings -> Privacy & Security on the watch. Open Settings -> Privacy & Security on the watch in this surfaced state. The menu now prompts for a 4-digit Screen Time passcode before allowing access. The passcodes I have set on the paired iPhone are rejected. The passcode prompt is therefore conditional on the Developer Mode entry having been surfaced by a recent Xcode connection attempt. In step 3 (no surfacing) the menu opens freely; in step 6 (surfacing in effect) the menu is gated. What I have already tried Confirmed Screen Time is disabled on the paired iPhone. Confirmed Share Across Devices is enabled. Confirmed Content & Privacy Restrictions is off on the iPhone. Confirmed I am an adult in my Family Sharing group (not a managed/child account). Confirmed there are no configuration profiles installed (Settings -> General -> VPN & Device Management is empty). Set a fresh Screen Time passcode on the iPhone. Not accepted by the watch prompt. Used Forgot Passcode? → Apple ID authentication to reset the Screen Time passcode and set a new one. Not accepted by the watch prompt. Turned the Screen Time passcode off entirely on the iPhone. The watch still prompts for one when Xcode is connecting. Unpaired the Apple Watch and re-paired as new (not restored from backup). Issue persists. Tried entering the watch's own device passcode at the prompt. Not accepted. Question What credential is the watch's Privacy & Security menu actually checking against once the Developer Mode entry has been surfaced, and how can it be reset or cleared from a paired iPhone? Is anyone else seeing this conditional gating where the menu is only locked in the post-surfacing state? Any pointers from the Xcode / watchOS tools team would be appreciated. Happy to provide sysdiagnose or further details on request.

Hello, My app Wecheerup 360 Booth (App ID: 676214516, bundle ID: com.wecheerup.wecheerup360booth.ios) has been stuck in the App Review process for longer than expected. Version 1.0.3 was submitted on April 13, 2026 and has been in “In Review” status for over 15 days. There are no messages in the Resolution Center and all metadata appears to be complete on my side.

Hi Apple Developer Technical Support Team, I hope this message finds you well. I am writing to seek urgent clarification on a profiling question that is directly impacting our SDK customers. Context We provide an iOS SDK that is integrated into third-party applications. Our SDK includes a background monitoring thread created via: -[NSObject performSelectorInBackground:withObject:] As documented, threads created through this API carry a default (relatively low) scheduling priority. Inside the thread, we call sleep(1) once per second for periodic idle intervals, and we collect CPU usage metrics using kernel APIs: • task_threads() • thread_info() Both calls involve kernel-level operations and are known to trigger context switches internally. The Core Issue — Customer Misinterpretation When our customers profile their apps using Instruments with "Context Switch Sampling" enabled, they observe that our SDK thread shows a large proportion of time labeled as "Runnable" and "Blocked". A representative example: • Total (wall clock): 4.30 s — 100% • Runnable: 3.06 s — 71.4% ← customers flag this as high CPU usage • Blocked: 1.05 s — 24.5% • Running: 176 ms — 4.1% ⚠️ Our customers are interpreting the "Runnable" time (71.4%) as CPU consumption by our SDK, and are raising concerns that our SDK is degrading their app's performance. We strongly believe this interpretation is incorrect — a thread in the "Runnable" state is merely waiting in the scheduler's ready queue and has NOT been assigned to any CPU core, therefore it should NOT consume any CPU resources. However, we need an official confirmation from Apple to address our customers' concerns definitively. Our Questions Do the time values shown next to "Runnable" and "Blocked" in the Time Profiler call tree represent wall-clock waiting time (i.e., time spent in that state), or actual CPU consumption time? Does a thread in the "Runnable" state consume any CPU resources on the device? We want to confirm clearly: does Runnable time contribute to CPU load or battery drain in any way? Is it correct that the high Runnable time observed is caused by the combination of: a. The low thread scheduling priority assigned by performSelectorInBackground:withObject:, and b. Context switch overhead introduced by the task_threads() and thread_info() kernel calls? Is there any official Apple documentation that explicitly describes the semantics of "Runnable" and "Blocked" time in Instruments, which we could reference when communicating with our customers? An authoritative answer from Apple would allow us to accurately explain the profiling data to our customers and clarify that the high "Runnable" time does NOT represent CPU consumption by our SDK. Thank you very much for your time and support. Best regards

Is there any way to activate Storekit External Purchase Entitlements in Russian region currently? External Purchase documentation's form link for this specific region is not working. Is there a workaround to register for it?

Hi Apple Developer Technical Support Team, I hope this message finds you well. I am writing to seek urgent clarification on a profiling question that is directly impacting our SDK customers. Context We provide an iOS SDK that is integrated into third-party applications. Our SDK includes a background monitoring thread created via: -[NSObject performSelectorInBackground:withObject:] As documented, threads created through this API carry a default (relatively low) scheduling priority. Inside the thread, we call sleep(1) once per second for periodic idle intervals, and we collect CPU usage metrics using kernel APIs: • task_threads() • thread_info() Both calls involve kernel-level operations and are known to trigger context switches internally. The Core Issue — Customer Misinterpretation When our customers profile their apps using Instruments with "Context Switch Sampling" enabled, they observe that our SDK thread shows a large proportion of time labeled as "Runnable" and "Blocked". A representative example: • Total (wall clock): 4.30 s — 100% • Runnable: 3.06 s — 71.4% ← customers flag this as high CPU usage • Blocked: 1.05 s — 24.5% • Running: 176 ms — 4.1% ⚠️ Our customers are interpreting the "Runnable" time (71.4%) as CPU consumption by our SDK, and are raising concerns that our SDK is degrading their app's performance. We strongly believe this interpretation is incorrect — a thread in the "Runnable" state is merely waiting in the scheduler's ready queue and has NOT been assigned to any CPU core, therefore it should NOT consume any CPU resources. However, we need an official confirmation from Apple to address our customers' concerns definitively. Our Questions Do the time values shown next to "Runnable" and "Blocked" in the Time Profiler call tree represent wall-clock waiting time (i.e., time spent in that state), or actual CPU consumption time? Does a thread in the "Runnable" state consume any CPU resources on the device? We want to confirm clearly: does Runnable time contribute to CPU load or battery drain in any way? Is it correct that the high Runnable time observed is caused by the combination of: a. The low thread scheduling priority assigned by performSelectorInBackground:withObject:, and b. Context switch overhead introduced by the task_threads() and thread_info() kernel calls? Is there any official Apple documentation that explicitly describes the semantics of "Runnable" and "Blocked" time in Instruments, which we could reference when communicating with our customers? An authoritative answer from Apple would allow us to accurately explain the profiling data to our customers and clarify that the high "Runnable" time does NOT represent CPU consumption by our SDK. Thank you very much for your time and support. Best regards

I am developing an iOS app using Capacitor and Xcode. The app installs on my device but fails to launch with the error: “Quarantined due to high logging volume.” I have already: Configured signing correctly Enabled Developer Mode Disabled excessive logging in the app code Cleaned build and re-synced Capacitor The app still fails to run on a physical device (My iPhone 17Pro Max). Please advise on how to resolve this issue or whether this is related to a system-level logging limit or WebView restriction. Please suggest a reliable solution to the issue.

Subject: [SDK / Instruments] Clarification on Runnable & Blocked Time Semantics — Customers Misinterpreting as CPU Usage Hi Apple Developer Technical Support Team, I hope this message finds you well. I am writing to seek urgent clarification on a profiling question that is directly impacting our SDK customers. Context We provide an iOS SDK that is integrated into third-party applications. Our SDK includes a background monitoring thread created via: -[NSObject performSelectorInBackground:withObject:] As documented, threads created through this API carry a default (relatively low) scheduling priority. Inside the thread, we call sleep(1) once per second for periodic idle intervals, and we collect CPU usage metrics using kernel APIs: • task_threads() • thread_info() Both calls involve kernel-level operations and are known to trigger context switches internally. The Core Issue — Customer Misinterpretation When our customers profile their apps using Instruments with "Context Switch Sampling" enabled, they observe that our SDK thread shows a large proportion of time labeled as "Runnable" and "Blocked". A representative example: • Total (wall clock): 4.30 s — 100% • Runnable: 3.06 s — 71.4% ← customers flag this as high CPU usage • Blocked: 1.05 s — 24.5% • Running: 176 ms — 4.1% ⚠️ Our customers are interpreting the "Runnable" time (71.4%) as CPU consumption by our SDK, and are raising concerns that our SDK is degrading their app's performance. We strongly believe this interpretation is incorrect — a thread in the "Runnable" state is merely waiting in the scheduler's ready queue and has NOT been assigned to any CPU core, therefore it should NOT consume any CPU resources. However, we need an official confirmation from Apple to address our customers' concerns definitively. Our Questions Do the time values shown next to "Runnable" and "Blocked" in the Time Profiler call tree represent wall-clock waiting time (i.e., time spent in that state), or actual CPU consumption time? Does a thread in the "Runnable" state consume any CPU resources on the device? We want to confirm clearly: does Runnable time contribute to CPU load or battery drain in any way? Is it correct that the high Runnable time observed is caused by the combination of: a. The low thread scheduling priority assigned by performSelectorInBackground:withObject:, and b. Context switch overhead introduced by the task_threads() and thread_info() kernel calls? Is there any official Apple documentation that explicitly describes the semantics of "Runnable" and "Blocked" time in Instruments, which we could reference when communicating with our customers? An authoritative answer from Apple would allow us to accurately explain the profiling data to our customers and clarify that the high "Runnable" time does NOT represent CPU consumption by our SDK. Thank you very much for your time and support. Best regards

Our Account Holder has requested transfer of Account Holder to me. This transfer needs me to verify my account on the developer app. I am based in South Africa, its only giving me drivers license option to verify, but it keeps failing, no matter what i do. I urgently need help with this, my apps are not being able to be updated or anything. Please can anyone help and guide me. I have created numerous support requests and call back, without success.

Hello, I requested to change my Apple Developer account from Individual to Organization, but I haven’t received any feedback for several weeks now. I also don’t see any indication in the UI that the request is still pending, which makes me unsure whether it was processed at all. Additionally, I created a support ticket regarding this issue, but I have not received any response there either. Could someone please help me check the status of my request or advise me on what I should do next? Thank you.

I cannot distribute an app on xcode becouse he cannot find a certificate valid for my personal or business team. Need to address XCODE to access to my business account and not personal

Individual enrollment stuck after identity document upload, no response after days Order W1683765476 Enrollment ID 4Q6XCD5F3Z Case 102879350376

I have raised multiple tickets for the same on developer enrollment. There's no one to get back on the status. I have submitted all documents as requested, and was acknowledged of the same. Yet it's been more than a week, and I have no status update and no email from the developer enrollment team. My enrollment ID is M5B36N5PJ9. Kindly look into this at the earliest. This is not the experience I expected from Apple. Best