Overview

I've been stuck on "enrollment processing" for several days now on our account dashboard. From friends, I've heard that the developer account enrollment is usually 24 hours after you have the DUNS number. Curious why this is taking so long or if there is something we are missing. Any thoughts or tips would be helpful!

I'm working on developing a transparent proxy provider extension, and I am trying to figure out how to handle a change in configuration that would result in a different verdict from handleNewFlow() Consider the following scenario: The proxy provider is started with configuration A, and a bunch of packet flows get a verdict of NO from handleNewFlow(). These flows are now handled by the system and get routed out to the internet normally. Some application changes the protocolConfiguration property to configuration B, and the proxy provider detects this change via KVO. This new configuration changes the verdict that would have been returned from handleNewFlow() to YES, requiring that traffic to be handled by the transparent proxy provider instead of the system. These flows should be closed (eg: by calling closeReadWithError()) but the proxy provider has no record of them because we previously returned NO Is there a way that a transparent proxy provider can get the operating system to close the currently open flows so that they can be re-evaluated by handleNewFlow() and directed into the transparent proxy instead?

I'm getting a log error and a slight delay in the UI when displaying a system image that changes at the end of a sequence. I'm using a ternary operator to determine the image; the fact that the image changes seem to be the issue, rather than the value itself. The issue only occurs for a newly installed app, and not when the app is rerun. (I'm using similar code to display an onboarding sequence after installation.) This happens on device (iphone 15 pro v25.6) and simulator (iphone 17 pro v25.6 and iphone 16 pro v18.5); xcode 26.5 (17F42). Console errors (device and iphone 17 simulator): fopen failed for data file: errno = 2 (No such file or directory) fopen failed for data file: errno = 2 (No such file or directory) Repro Code: import SwiftUI struct ContentView: View { // NOTE: error only occurs with new install. @State private var currentItem = 0 @State private var totalItems: Int = 4 var body: some View { VStack(spacing: 0) { Spacer() Text("totalItems: \(totalItems)") TabView(selection: $currentItem) { ForEach(0...totalItems, id: \.self) { item in Text("\(item) ~ \(currentItem)") .tag(item) } } //TV .tabViewStyle(.page(indexDisplayMode: .never)) .frame(height: 200) Button { if currentItem < totalItems { currentItem += 1 currentItem = min(totalItems, currentItem) } } label: { let imgString: String = (currentItem == totalItems ? "arrowshape.turn.up.right" : "arrowshape.right") // error // let imgString: String = ((currentItem == totalItems) ? "x.circle" : "smallcircle.filled.circle") // error // let imgString: String = "smallcircle.filled.circle" // no error // let imgString: String = "x.circle" // no error Text("\(imgString)") // if only print text, no error, so issue seems to be with Image. Image(systemName: imgString) } Spacer() } } } Click through the button sequence to see issue at end of sequence. Uncomment the various imgString lines to see indicated differences in behavior. Need to delete app each time to repro issue. Running in simulator on iphone 16 Pro iOS 18.5 has slightly different error messages: fopen failed for data file: errno = 2 (No such file or directory) Errors found! Invalidating cache... fopen failed for data file: errno = 2 (No such file or directory) Errors found! Invalidating cache...

Hi Team We are building a live activity feature for our app. While using the APNS broadcast API (https://api.push.apple.com:443/4/broadcasts/apps/), we are getting throttled. The updates are infrequent (sport games) and yet we are facing this issue. Our understanding was that the throughput is quite high but there is no documentation on the actual limitations. Furthermore, all of our updates are using a priority of 5. We have currently configured retry with exponential backoff and jitter but we would like to understand the APNS throttle limit for live activity broadcast. Is the limit per channel id or at API level? What is the hard limit for the API request per seconds? Can we request increase to the API rate limit?

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: NUBWYRAJXC I submitted my enrollment a month ago and I haven’t received any email updates or requests for additional information yet even after contacting apple developer support through email several times. 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.

Hi, My app submission has been waiting for review for an unusually long time after submission. This update is very important for us because it is related to payments. At the moment, a payment-related issue is preventing us from properly collecting revenue, so this is becoming a critical problem for our business. I submitted a request for an expedited review, but so far I have not received any action or update. I do not use the expedited review option often - only when there is a genuinely critical issue that needs to be resolved quickly. Could someone from Apple advise whether this waiting time is normal, or if there is anything I should check or do on my side? I can provide the Submission ID privately if needed. Thank you.

I'm trying to distribute our app through TestFlight's internal testing for our QA Analysts to run some tests in the non-production environment. In this page: https://developer.apple.com/documentation/storekit/testing-in-app-purchases-with-sandbox Is stated that: "Apps that you download from TestFlight always run in the sandbox environment." But we ran into the issue from the ProximityReaderAPI requesting a Sandbox account anyway (This token requires a sandbox test account from your Apple Developer account). Is that not the case for Tap To Pay on iPhone?

Our organization’s Apple Developer Program enrollment has been completely stuck for 45+ days. Callback requests is going unanswered, we have waited for half an hour to an hour several times. We are eager to ship our app. How to get attention and help from someone at Apple Developer Program Enrollment review team.

Our app supports Full Keyboard Access. We have a scroll view containing content that extends beyond the visible area. When navigating with the keyboard, focusable elements inside the scroll view are reached and the view scrolls to follow focus, but content that has no focusable elements (e.g. long blocks of static text, images, or footer content below the last control) can't be brought into view by the keyboard alone. Is there a supported way for Full Keyboard Access users to scroll a scroll view to see this off-screen, non-focusable content — e.g. a built-in scroll command, or an API to make the scroll view itself focusable/scrollable via the keyboard — without resorting to custom key handling?

Our app supports Full Keyboard Access. When an element is focused, the system-drawn FKA focus indicator (the ring/overlay) sits over the UI component. This overlay drops the content's colour contrast below the WCAG 2.1 minimums — 4.5:1 for text (1.4.3) and 3:1 for UI components and focus indicators (1.4.11) — causing the focused state to fail accessibility audits. Is there a supported way to completely remove this focus overlay on a view without breaking FKA keyboard navigation or VoiceOver?

Hello, I am doing a personal research project around ARKit camera frames and camera calibration data. For each accepted ARFrame, I export: ARFrame.timestamp ARFrame.camera.imageResolution ARFrame.camera.intrinsics ARFrame.capturedImage The target video mode is 4K / 30 FPS. In my test captures, I noticed two things: ARFrame.camera.intrinsics is not constant across the recording. Some neighboring frames from ARFrame.capturedImage have noticeably different sharpness: one frame can look sharp, while the next frame can look blurred. Regarding intrinsics, I observe small per-frame changes in fx/fy/cx/cy. For example, in one session: fx/fy changed by approximately 36 px cx changed by approximately 1.5 px cy changed by approximately 2.3 px I understand the standard meaning of the intrinsic matrix: fx / fy = focal length in pixels cx / cy = principal point in pixels relative to the image/reference frame My main question is not about the definition of these values, but about how to correctly interpret their changes over time. In particular, I am interested in cx/cy, because the principal point is important for measurements. I would like to understand whether a change in cx/cy corresponds to a meaningful update of the camera model for the current frame, and what physical or camera-pipeline process may cause this change. Questions about ARFrame.camera.intrinsics: Are ARFrame.camera.intrinsics values expected to change between frames during a single ARWorldTrackingConfiguration session? If fx/fy changes over time, can this reflect autofocus / focus breathing, internal camera calibration updates, digital crop/scaling, stabilization-related mapping, or other camera pipeline changes? If cx/cy changes over time, should I interpret this as an updated principal point for the current ARFrame image/reference frame? Does ARKit update cx/cy to account for any internal crop, scaling, stabilization, virtual camera behavior, lens movement, or calibration changes? Is there a known physical interpretation for small cx/cy changes reported by ARFrame.camera.intrinsics, or should these values simply be treated as ARKit’s best current camera model for that frame? In an ARKit-first pipeline where focus/exposure/stabilization are managed by ARKit/camera pipeline, is the recommended approach to store ARFrame.camera.intrinsics per frame together with ARFrame.timestamp and ARFrame.camera.imageResolution? Is there any public API that exposes the reason for intrinsics changes, such as focus position, stabilization transform, crop transform, active camera constituent, lens movement, or per-frame calibration update reason? I also have a related question about ARFrame.capturedImage frame quality. In some recordings, neighboring frames can have noticeably different sharpness. For example, one frame can look sharp, while the next frame can be visibly blurred, even though the scene and camera movement are continuous. Questions about frame sharpness / camera pipeline behavior: Is frame-to-frame sharpness variation expected when using ARFrame.capturedImage as the video source? Can ARKit change focus, exposure duration, ISO, white balance, crop/scaling, or other camera pipeline parameters between frames during an ARWorldTrackingConfiguration session? Is there any public API to inspect per-frame exposure duration, ISO, focus position, lens position, stabilization state, crop/scaling transform, or other capture parameters for ARFrame.capturedImage? If some frames are sharp and neighboring frames are blurred, should this usually be interpreted as motion blur / exposure behavior / autofocus behavior, or can ARKit internal processing also affect this? Is there any recommended way in an ARKit-first pipeline to reduce frame-to-frame sharpness inconsistency, or is the only reliable approach to use an AVFoundation-first capture pipeline with locked focus/exposure/ISO/white balance? The main goal of my research is to understand how to correctly interpret ARKit-provided intrinsics over time and how much of the camera pipeline behavior is observable through public ARKit APIs. Since fx/fy/cx/cy are important for measurements, I want to know whether treating ARFrame.camera.intrinsics as the Apple-delivered per-frame camera model is the safest approach. Thank you.

Hello App Review Team, I am following up on my earlier post about our app (App ID: 6761247061), as our situation has unfortunately not improved. Our app was finally reviewed on May 22 and rejected under Guideline 2.1(a). We resolved the issue on the same day and resubmitted, but the resubmission has been stuck in "Waiting for Review" again for several business days with no progress. Due to these repeated delays, we have been unable to release a new version of our app to our users for nearly three weeks. If there is anything we are missing, or any issue with our submission that we should address, we sincerely ask for your guidance. We are fully committed to complying with the Review Guidelines and resolving any concerns you may have. Any guidance from your team would mean so much to us. Thank you so much for your time and patience.

Hello, Adding our case to the long-running thread on this issue (https://developer.apple.com/forums/thread/118465). Our team is the latest to be hit by statusCode 7000 "Team is not yet configured for notarization", and we'd like to (a) document the data points in case it helps Apple correlate cases and (b) ask the community whether anyone has seen a faster resolution path than what's been reported here over the past 6 years. Our situation Team ID: A92X4FJ5HU Last successful notarization: 2026-05-18 11:23:26 UTC First rejection: 2026-05-18 17:19:15 UTC (~6 hours later, no apparent trigger on our side) Total rejections since: 22 submissions across 9 days, 100% rejected with statusCode 7000 Open support case: 102900780153 What we have already verified Apple Developer Program membership Active (Renewal Sept 17, 2026) Apple Developer Program License Agreement: Accepted Apr 15, 2026 Free Apps Agreement: Active (Apr 15, 2026 — Sept 16, 2026) Paid Apps Agreement: Active (Mar 17, 2026 — Sept 16, 2026) Banking and tax information complete Developer ID Application certificate valid (notBefore 2025-10-12, notAfter 2027-02-01) What we tested Variable Result API key A (Admin role, created 2025-10) Rejected, statusCode 7000 API key B (Admin role, created 2026-05-22) Rejected, statusCode 7000 Same Issuer ID, both keys Same rejection Bundle ID com.matrixai.app (one product) Rejected Bundle ID com.flowith.os.beta (different product) Rejected Locally-rebuilt clean DMG Rejected Pre-existing already-signed DMG Rejected The rejection happens server-side after upload completes — authentication, signing, hardened runtime, and timestamp are all confirmed correct (codesign verifies cleanly, both keys authenticate). The submission is accepted by the notary service, then rejected with statusCode 7000 after a few minutes of "In Progress". Sample submission IDs (all rejected, statusCode 7000) ac52531f-1b9e-4210-8123-54afea90f66f (2026-05-27 10:20 UTC) baba6420-e245-4597-b229-ec5af4b309c5 (2026-05-27 10:23 UTC) 72118f71-9f1d-4ce9-8068-3eca5017104d (2026-05-27 09:49 UTC) Question to the community I've read this entire thread (all 4 pages, 6 years of reports) and the related threads (749857, 813624, 825906, 827589, 130479, 130494, 741721, 809228). The consistent answer from DTS is "this is a Developer Program Support issue, escalate via official channels", but the threads also document wait times of 1 day to 3+ months with no SLA and no transparency. A few questions: Has anyone in 2025 or 2026 had this resolved in under 2 weeks? If yes, what (if anything) on your side accelerated it? Did anyone identify a specific account-level signal (recent agreement re-acceptance, banking change, AppID/Bundle ID conflict, recent role/Account Holder change, recent device verification, etc.) that correlated with the trigger date? Is there any escalation path beyond Case → DPS → "engineers are working on it" loop? Several users on this thread report 39 days, 3 months, 4 separate cases — and DPS still cannot give an ETA. I understand the official answer is "wait for Developer Program Support". Posting this here primarily so Apple has more correlated data points for the engineering team that owns notarization, and so other developers who hit this in the future can find one more datapoint. Thanks.

Hello, My app was submitted for review last week, but it is still showing the status Waiting for Review and has not moved into the review process yet. App details: App ID: 6751946791 Current status: Waiting for Review Submission time: Last week Additional context: Due to a time-sensitive launch schedule, I have submitted several expedited review requests, but the app status has not changed. I would like to ask: Could submitting multiple expedited review requests affect the normal review queue or delay the review process? Does staying in Waiting for Review for this long indicate any possible issue with the submission, metadata, account status, or review queue? If further follow-up is needed, should I contact the App Review team through the App Review contact form? Any guidance from Apple or developers with similar experience would be greatly appreciated. Thank you.

Hello Apple App Review Team, I am writing to urgently request your assistance regarding our application 'Kavra'. We are facing a critical situation that is heavily impacting our entire launch roadmap and user base. To give you the timeline: we initially submitted the app for review on April 30th. After waiting for two full weeks without any updates or status changes, we assumed there might be a technical stall in the review pipeline. Consequently, we canceled the submission and resubmitted the app on May 14th. Today is May 27th, and the application has been stuck in the "Waiting for Review" status for another 13 days. In total, we have been locked in the review queue for nearly a month. This prolonged delay has completely frozen our development cycle and disrupted our time-sensitive marketing plans. We have thoroughly audited our app against all App Store Review Guidelines and confirm 100% compliance. There should be no blockers from our end. If you require any additional information, test accounts, or documentation to move this forward, please let me know immediately. We kindly request you to look into our account for any technical glitches and expedite the review process. Thank you very much for your time, understanding, and support. Sincerely, [Bora Çoban]

I submitted my application on April 30th, and they responded with various errors. I fixed each one and resubmitted it, but I received no response until May 14th. Thinking it might be stuck in their system, I canceled the process and resubmitted it, but it's still pending review after 13 days. In short, I haven't received a response from Apple for a month. I leave a callback, they call back, I wait an hour, and no one gets through. It's a terrible customer support system.

Hi, I'm an Android Developer at Radio France, and we're currently integrating Apple Music into our Android application. We noticed that the Android SDK artifacts are currently distributed as raw .aar files, such as: mediaplayback-release-1.1.1.aar musickitauth-release-1.1.2.aar For Android projects, publishing these libraries through a Maven repository would greatly simplify integration and maintenance. It would provide a cleaner setup for dependency management, versioning, and future updates through Gradle. A Maven distribution model such as: implementation("com.apple.music:mediaplayback:1.1.1") implementation("com.apple.music:musickitauth:1.1.2") would make adoption significantly easier for Android teams. Thanks for your work on the SDK and for considering this improvement.

Dear Developer Technical Support, I wanted to ask for technical advice regarding the DeviceActivityMonitor which is part of the DeviceActivity framework: The DeviceActivityMonitor has a very strict memory limit of 6MB. That’s not a lot and it doesn't leave a lot of room for any kind of code that accesses permanently stored data. I would therefore like to ask for advice on best-practices on how to share information between the main app and that extension: Is UserDefaults a good idea to use here? Can/should we use CoreData or SwiftData? Should we build super small file-based data sharing (e.g. via .plists)? Why is it necessary to share data? This can be simple things that inform the decision of the device activity monitor in intervalDidStart, intervalDidEnd, eventDidReachThreshold, eventWillReachThresholdWarning. For example a setting where the user decides if they want to receive a push notification on eventWillReachThresholdWarning. Or the list of tokens that is supposed to be blocked in eventDidReachThreshold or intervalDidStart. I’m asking because even though we are super careful and conservative about memory allocations in our DeviceActivityMonitor we are regularly seeing it being killed due to memory pressure. What’s the best way to approach this? I’m grateful for any kinds of hints! Thanks a lot and have a great day! – Frederik

Notarization has been rejecting every submission with statusCode 7000 ("Team is not yet configured for notarization") for over five weeks. I'd appreciate any Apple staff who can confirm the gate status or re-route this internally. Account: Team ID: ZLPP2G8NG3 Account type: Individual, ACTIVE membership Region: EU (Czech Republic) The submission is technically clean — this is rejected at the gate, not on content: Developer ID Application cert valid (expires 2031), full WWDR chain Signed with hardened runtime + secure timestamp codesign --verify --deep --strict passes notarytool uploads succeed, then Rejected in ~30-60s log shows "issues": null (the archive is never opened) Confirmed it is NOT app-specific: a 50 KB hello-world C binary, signed the same way, is rejected identically. Latest canary submission: 95833847-e70f-41fe-b61f-c9dc9ffd90ed (2026-05-27) -> 7000 Timeline: 2026-04-20 first 7000 rejection (app, after ~60h "In Progress") 2026-04-29 escalated to engineering (case 102873818441, advisor Ronan) 2026-05-13 advisor Ira (case 102887849530) requested government photo ID + address verification — uploaded same day via the official file-upload portal, autoreply confirmed receipt 2026-05-14 to 05-27 silence; case was closed on Apple side, issue NOT resolved 2026-05-27 still 7000 I've completed everything on my side: License Agreement accepted, Free Apps agreement Active, DSA trader designation done, and the identity-verification documents submitted on May 13. Two weeks later the gate is still down with no reply on either case. Question for Apple staff: can someone confirm whether the identity-verification documents from May 13 reached the team that flips the notarization flag, and whether anything further is needed from me? The support cases have gone quiet and I have no other channel to check status. Thank you.

Environment Device: iPad Pro 11-inch 2nd gen (iPad8,9 / A12X) OS: iPadOS 26.5 (23F77) Xcode: 26.3 Issue App crashes with EXC_BREAKPOINT / SIGKILL when user scrolls through a PDF in PDFView on iPadOS 26.5. Crash Log (ASI) "BUG IN CLIENT OF LIBPLATFORM: Trying to recursively lock an os_unfair_lock" Abort Cause 259 Root Cause (from .ips) Two threads deadlock on os_unfair_lock inside CGPDFPageInsertTableDescriptions: Thread 0 (main): _os_unfair_lock_recursive_abort CGPDFPageInsertTableDescriptions [PDFPageAnalyzerV2 addTablesFromVisionDocument:documentImage:toPage:withBox:]_block_invoke_2 _dispatch_async_and_wait_invoke ← main thread waiting Thread (PDFKit.PDFDocument.formFillingQueue): _dispatch_sync_f_slow ← background queue waiting for main thread +[PDFPageAnalyzerV2 addTablesFromVisionDocument:documentImage:toPage:withBox:] +[PDFPageAnalyzerV2 analyzePage:withBox:requestTypes:] -[PDFView visiblePagesChanged:] ← triggered by scrolling PDFPageAnalyzerV2 dispatches_sync back to the main thread from PDFKit.PDFDocument.formFillingQueue, while the main thread is already blocked in dispatch_async_and_wait for the same operation. This results in a recursive lock on os_unfair_lock in CGPDFPageInsertTableDescriptions → SIGKILL. Notes PDFPageAnalyzerV2 appears to be a new iOS 26 Vision-based table analysis feature No public API found in PDFKit headers to disable this analysis Workaround: pdfView.usePageViewController(true, withViewOptions: nil) appears to reduce frequency of visiblePagesChanged: triggers Question Is there an official API to disable PDFPageAnalyzerV2 table analysis on iOS 26? Is this a known issue with a fix planned?