Overview

Hello Apple Developer Support, We need assistance with migrating Sign in with Apple users after completing an app transfer between two Apple Developer Teams. Current situation The app transfer has been completed and accepted by the recipient team. The recipient team has not yet released a new version on the App Store. Our production server, database, API domain, Bundle ID, and existing application user accounts remain unchanged. Before the transfer, we had never created a Sign in with Apple private key under the transferor team. Therefore, we do not have a previously generated .p8 private key for this app. This is not a case of a lost or revoked key. After the transfer, the app’s identifier is no longer listed under the transferor team’s Certificates, Identifiers & Profiles. When attempting to create a Sign in with Apple key under that team, we cannot select the transferred App ID as the primary App ID. Migration blocker According to Apple’s migration documentation, the transferor team must use its own client_secret to obtain a migration access token and generate a transfer_sub for each existing user. We are unsure how to obtain valid transferor-team credentials now that the App ID has moved to the recipient team and no private key was created before the transfer. Questions What is the supported procedure for obtaining valid transferor-team migration credentials in this situation? Can the transferor team create or configure a new Sign in with Apple private key for the transferred App ID after the transfer has been completed? If this cannot be done through the developer portal, can Apple Developer Support assist, or is there another supported migration method? Is transferring the app back to the original team, preparing the migration credentials and user transfer identifiers, and then transferring it again necessary in this situation? We would like to confirm whether this is required before making any further changes to the app’s ownership. We understand that the user migration process has a 60-day transfer window. We would appreciate guidance on resolving this credential issue promptly so that existing users can continue signing in to their original application accounts. Thank you for your assistance.

For an application supporting iOS 16 and later, is there a supported public API that exposes a monotonic timestamp for the original determination of a CLLocation, rather than the time it is delivered to CLLocationManagerDelegate? The requirement is to reject observations whose original acquisition age exceeds 10,000,000,000 ns at the final native transport-dispatch check. Exactly 10 seconds is allowed; 10 seconds plus 1 ns is rejected before conversion to milliseconds. This is an arithmetic boundary requirement, not an assumption that location measurements have nanosecond physical accuracy. CLLocation.timestamp is a Date for when the location was determined. Sampling a continuous monotonic clock in didUpdateLocations instead measures callback receipt. Cached observations, batched updates and delayed background delivery can separate those events. Does a public API provide either: A monotonic acquisition/determination timestamp associated with that same CLLocation; or A documented finite uncertainty bound and supported method for relating its Date timestamp to a sleep-inclusive monotonic clock at dispatch? How do the documented guarantees handle wall-clock adjustments between determination and delivery, device sleep, suspension, queued updates and process restarts? If a newer API supplies stronger evidence, what is its minimum supported iOS version? If neither mechanism is available, is there a supported request or delivery mode that establishes a documented lower bound on the original determination time and can reliably reject older cached observations? A recent callback or request by itself would not establish that relationship. I would appreciate documentation describing the guarantees, limitations or supported alternatives. I have not established that such a mechanism is impossible; this is a capability clarification, not a claim of a reproduced operating-system defect.

Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.

We develop SpinCut DJ, a free-to-download proprietary DJ application by LALAMO CORPORATION for iPhone, iPad and Mac Catalyst. We want to add Apple Music subscription playback for users with an active subscription, similar to the integrations featured in DJ with Apple Music. This question is about the officially supported integration path, not extracting or bypassing protected audio. Our existing engine uses app-owned PCM for two independently controlled decks, scratch/reverse playback, tempo changes, hot cues, loops, beat synchronization and independent master/headphone outputs. We have reviewed MusicAuthorization, MusicSubscription, catalog/library requests, ApplicationMusicPlayer and SystemMusicPlayer. We understand that ordinary catalog access and protected queue playback do not establish a documented route to feed subscription audio into our custom engine, or permission to modify or synchronize MusicKit content. We have not enabled subscription-catalog DJ playback. Apple Developer Support advised us to ask the Developer Forums about the required technical integration. Could an Apple representative clarify: Is there a documented public API for two independent, simultaneous Apple Music DJ decks with scratch/reverse/tempo control? If a separate Apple Music DJ integration, agreement, SDK or capability is required, what is the current official application or referral process for a Japan-based developer? Are iOS, iPadOS and Mac Catalyst supported through the same integration, and what technical material is required for evaluation? What approved interfaces govern waveform/beat analysis, seeking and separate master/headphone routing? We are not requesting recording/export, stem separation, offline file extraction or rebroadcast permission through ordinary MusicKit. Those features would remain unavailable for subscription content unless separately and expressly supported. We can provide a product demonstration and integration brief through an appropriate private channel. Product: https://spincutdj.com/ App Store: https://apps.apple.com/app/id6804328893 Please point us to the supported technical and onboarding path rather than an undocumented entitlement or workaround.

Subject: Supported macOS containment for a sandboxed worker after controller failure I'm investigating an Apple Silicon/macOS architecture in which an untrusted, signed, sandboxed worker must be independently containable by a separate trusted supervisor. The worker needs only a narrow authenticated communication channel. It requires no direct network access, external operational credentials, privileged file access or authority to launch helpers. I understand that App Sandbox does not inherently prevent child-process creation, and that RLIMIT_NPROC alone does not prevent every form of execution delegation. Could you clarify: Is there a public, supported macOS mechanism to deny all worker-originated subprocess creation and execution delegation at launch, while retaining one restricted communication channel? Alternatively, is there a supported mechanism for a surviving supervisor to identify, terminate and positively verify the complete execution domain of a worker, including any descendants, after its controller crashes or is suspended? What guarantees and limitations apply to stable identity, process exit, automatic relaunch and loss of the supervisor? I'm specifically seeking supported operating-system guarantees, not private sandbox profiles, polling, heartbeat inference or best-effort process-tree enumeration. The goal is to determine whether a bounded synthetic containment experiment is technically justified. No production implementation has been attempted.

Hello App Review team and fellow developers, Could someone help clarify whether our submission is progressing normally, or whether there is a specific blocker that requires action from us? App: MountaPulse Apple ID: 6762391064 Current iOS version: 1.6.7 Timeline (Europe/Sofia local time): October 23, 2026, 18:59: an earlier submission entered Waiting for Review. October 27, 17:12: we withdrew that earlier submission after prolonged waiting without a substantive support response. October 27, 17:23: we submitted version 1.6.7. This is the current active submission; we are not claiming it has been waiting since October 23. October 28: our expedited review request was accepted, with confirmation that Apple would expedite review for MountaPulse. October 29: the latest status remains Waiting for Review. We have received automated support acknowledgments but no substantive explanation or request for action. We also requested escalation to senior support today. We have a deadline tomorrow, October 30. The uncertainty around the iOS release is affecting our participation plans, advertising launch and potential partnerships. Could an Apple representative please clarify: Is the accepted expedited review associated with the current 1.6.7 submission? Is the delay due to queue volume, an account/submission issue, or missing information we need to provide? Can the existing support requests be reviewed and an actionable status update provided? We understand that review times vary and are not asking for guaranteed approval. We need to know whether anything is required from us and what to expect next. We want to keep the current submission active. If other developers have resolved a similar situation after an expedited request was accepted, we would appreciate hearing what helped. Thank you, MountaPulse

When attempting to access the (Certificates Identifiers & Profiles) page, I receive the message "Unable to find a team with the given Team ID to which you belong". Even while set as a developer or as an admin I still receive the same message above.

We build a medical scanning app. A practitioner walks a slow orbit (~1 m radius, two laps, 25–35 s) around a standing subject while an ARSession runs, and we capture ~50 high-resolution stills with captureHighResolutionFrame. The ARKit camera poses for those frames are later used to set the metric scale of a photogrammetry reconstruction. We need the resulting scale to be within about 2 % of true. What we observe, measured against a printed A4 sheet on the floor in every scan: Devices with LiDAR (iPhone 16 Pro Max, iPad Pro), using the sceneDepth frame semantic as a check: scale within ±0.8 % across 11 sessions. Devices without LiDAR (iPhone 13, iPad 9th and 11th gen, plus non-LiDAR runs on the Pro devices): the world-frame metre is on average 2–3 % short of true, and varies by a further ±2 % from one session to the next, across 24 sessions in four rooms. Within a session the scale is stable: lap-to-lap variation is under 0.4 %. The error appears to be set during initialisation and held. Nothing we record about capture correlates with the error: time spent before capture, distance walked, vertical camera movement, orbit radius, rotation speed, tracking state, or the residual of our pose fit. Questions: Is there any session setup, initialisation practice, or motion during the first seconds of tracking that is known to improve the metric scale estimate on devices without LiDAR? Does the choice of video format, resolution or frame rate affect scale estimation? Is there any signal, beyond ARCamera.trackingState, that indicates how well scale has been determined for a session, so we could flag sessions rather than accept them? Does anything in the configuration above, in particular locking exposure on the capture device or using the high-resolution video format, work against tracking quality or scale?

On watchOS 27, a third-party watch app that advertises an application service with NWListener (default NWParameters.applicationService, service declared in NSApplicationServices → Advertises) is never advertised: the advertiser path is denied by NECP policy. As a result, when a tvOS app presents DDDevicePickerViewController and the user selects the watch and taps Connect on the watch, sharingd finds no listener (listenerID (null)), the pairing times out after ~30 s, and the tvOS picker's endpoint never returns — neither an endpoint nor an error. Raw lines: watchOS 26.6 (success, pid 267) 16:00:55.891 AppleWatch[267] -[_NWAdvertiser start] [L1] Starting advertiser 16:00:55.891 AppleWatch[267] -[_NWAdvertiser updateFlows:]_block_invoke [L1] Added listener flow ID 667B9945-… 16:00:55.926 rapportd[48] Found registered listener RPNWListener[…][com.fitonapp.fiton.FitOnWorkout]=0A1149F2-… : ageOut=179s agentClient=0x0 { 'kebike' } 16:00:55.927 rapportd[48] Updated RPNWAgentClient[0x176cc550] (LSTNR): < appSvc=com.fitonapp.fiton.FitOnWorkout PID:267 entitled=0 … browseToken=[pid:267,id:667B9945] … > 16:00:55.930 rapportd[48] [pid:267,id:A20E8919] createListenerFramer calling assign with local endpoint=::.51714 16:01:09.956 rapportd[48] [pid:267,id:F7883D0D] ADVERTISE: Start advertise 'FitOnWorkout' request QUIC=NO isTCP=YES params:[tcp, pid: 267, local: ::.51714, …] 16:01:29.352 rapportd[48] Created incoming RPNWConnection[CONN[5BCD2213-…] (IN): … appSvc=com.fitonapp.fiton.FitOnWorkout … EP={kebike:…}] 16:01:29.399 rapportd[48] [pid:267,id:3346E704] assigning connection ::.51714 <-> app_svc: com.fitonapp.fiton.FitOnWorkout, service_id: D2D4D049-… 16:01:29.404 AppleWatch[267] nw_connection_report_state_with_handler_on_nw_queue [C2] reporting state ready Raw lines: watchOS 27 (failure, 10-21) 16:00:48.761 AppleWatch[556] -[_NWAdvertiser start] [L1] Starting advertiser with descriptor: FitOnWorkout scope:3f … 16:00:48.761 AppleWatch[556] -[_NWAdvertiser updateFlows:] [L1] Listener skipping advertise flows due to unsatisfied path with policy drop 16:00:48.760 rapportd[98] [pid:556,id:C1D4B82D] createListenerFramer: incorrect agent type ← never upgraded to LSTNR afterwards … 16:05:37.919 sharingd[458] setupDDUIListenerIfNeeded, incoming pairing session … ← TV's pairing request did arrive 16:05:40.538 sharingd[458] Attempting to launch application com.fitonapp.fiton.watchkitapp 16:05:40.688 rapportd[98] Searching for listener agent client with appSvc='com.fitonapp.fiton.FitOnWorkout' 16:05:40.688 rapportd[98] Created new listener RPNWListener[…][com.fitonapp.fiton.FitOnWorkout]=F625EFB1-… : ageOut=180s agentClient=0x0 { } ← no FitOnWorkout ADVERTISE afterwards; the listener never gets the app's agent client

I have submitted a feedback report regarding Xcode 27.1 RC Device Hub: iPhone Duo screen captures function only work when the device is fully closed; alternative hinge positions produce a blank display.

Environment: macOS 26.6.2 (25G83) Xcode 26.6 (17F113) macOS command-line process Security.framework SessionGetInfo ASID obtained from the kernel-provided audit token in a received Mach message I’m implementing a security-sensitive Mach IPC receiver. The receiver obtains the sender’s audit token from the Mach message trailer and derives the sender PID, effective UID, and audit session ID (ASID). The sender executable identity is validated separately. Given the ASID, SessionGetInfo can successfully return the corresponding SecuritySessionId and session attributes. The question is about the freshness and synchronization semantics of that lookup. At the point where the receiver authorizes a request, can a successful SessionGetInfo(asid, ...) result be treated as authoritative evidence that the corresponding login/audit session is still currently valid? In particular: What happens if the session logs out, terminates, or is revoked concurrently with the lookup? Can SessionGetInfo successfully return information for a session that is no longer current due to caching or propagation delay? Are there documented ordering or synchronization guarantees between session termination and subsequent SessionGetInfo calls from another process? Can the lookup block for an unbounded period if the underlying security service is unavailable? Is there a supported timeout or cancellation mechanism? Is there another supported public macOS API better suited to establishing authoritative current-session liveness for an ASID obtained from an audit token? The security requirement is fail-closed. I’m specifically trying to avoid private APIs, process-table heuristics, diagnostic launchctl output, or assumptions that the ASID encoded in a previously received audit token necessarily represents current session state. If the public API does not provide an authoritative liveness/freshness guarantee, confirmation of that limitation would also answer the design question. I also have a minimal 122-line Xcode sample that: creates and receives a Mach message, reads the kernel-provided audit trailer, extracts the ASID, calls SessionGetInfo, and prints the returned session ID and attributes. I can provide the sample project if useful.

Hello, My iOS App (Apple ID 6811252087)update fixes a serious bug and has remained In Review for several days, even though an expedited-review request was accepted. I understand that the review may take a long time, but I really don't understand why the app has already been in the "In Review" status for several days and there is still no result. An earlier submission also stayed in review for a long time, so I withdrew and resubmitted it. The overall process has now taken more than a week. Developer Support says the review is ongoing but cannot provide a completion estimate. Is there anything else I should check or provide while keeping the current submission active? Have other developers experienced similar delays recently? Thank you.

Hello Apple Developer Team, I am experiencing an issue with my Apple Developer Program enrollment and would appreciate assistance. I registered as an Individual developer on October 26, 2026, and submitted my payment details for the $99 annual membership. I received an official Order Acknowledgement email confirming that my order had been received. What happened: Apple attempted to charge $99 through APPLE.COM/US. My bank (Kaspi Bank, Kazakhstan) declined the transaction because online purchases were disabled on my card. I immediately identified and resolved the issue by enabling online and international payments. My card is now ready for payment, and sufficient funds are available. However, Apple has not attempted to charge my card again, and my enrollment status remains "Pending – Purchase your membership." Support history: I have already contacted Apple Developer Support multiple times and emailed the Apple Developer payment department at devpayment@apple.com. My support case number is: Case ID: 103010597182 I also received a payment failure notification stating that my order may be cancelled if the payment issue is not resolved within seven days. Unfortunately, I have not received a substantive response or instructions on how to retry the payment. My questions: Can Apple retry the $99 payment using my existing payment method? Is there a way to manually complete payment for my existing order? Can I safely enroll through the Apple Developer app instead, without creating a duplicate enrollment or risking a second charge? Could an Apple Developer Support representative review or escalate my existing case? I am ready to complete the payment immediately. The banking restriction has already been removed. I would really appreciate any assistance in resolving this issue before my order is cancelled. Thank you for your time and support.

Hello, Our first app, Bookella: Book Tracker & Log (Apple ID 6804023709), has been waiting for review since October 14. It was reviewed once, but the review ended early because of a temporary StoreKit sandbox error, and the app went back to the end of the queue. Timeline: Oct 14 - submitted version 1.0.14 Oct 22 - expedited review requested and accepted Oct 28 - reviewed and returned under Guideline 2.1(b) because of a StoreKit sandbox error Oct 28 - resubmitted as 1.0.15, back in Waiting for Review Oct 29 - expedited review requested again and accepted According to our logs, the review lasted about 5 minutes. The plans loaded, and the App Store payment sheet opened. Then the sandbox returned a "store problem" error, and the products stopped loading. Purchases work correctly in our own sandbox and TestFlight testing. Version 1.0.15 also retries loading the plans automatically. We have now been waiting for over two weeks, and the first launch is still on hold. Could someone from App Review please look at our submission? Submission ID: 47af8ce4-c8ea-457a-af1b-32e122fe8e02 Thank you!

Hello, My first app submission has been in "Waiting for Review" status for 6 days without any progress. App name: Kor: Buradayım Apple ID: 6826731517 Platform: iOS Version: 1.0 Case ID: 103011637471 All agreements are active, and all required metadata, privacy details and review information have been provided. I haven't received any messages from App Review. I contacted App Review through the Contact Us form 2 days ago but haven't received a response yet. Is there anything that could be blocking the review, or anything I should do on my side? Any help would be appreciated. Thank you!

Hello Apple Developer Team, I am experiencing an issue with my Apple Developer Program enrollment and would appreciate assistance. I registered as an Individual developer on October 26, 2026, and submitted my payment details for the $99 annual membership. I received an official Order Acknowledgement email confirming that my order had been received. What happened: Apple attempted to charge $99 through APPLE.COM/US. My bank (Kaspi Bank, Kazakhstan) declined the transaction because online purchases were disabled on my card. I immediately identified and resolved the issue by enabling online and international payments. My card is now ready for payment, and sufficient funds are available. However, Apple has not attempted to charge my card again, and my enrollment status remains "Pending – Purchase your membership." Support history: I have already contacted Apple Developer Support multiple times and emailed the Apple Developer payment department at devpayment@apple.com. My support case number is: Case ID: 103010597182 I also received a payment failure notification stating that my order may be cancelled if the payment issue is not resolved within seven days. Unfortunately, I have not received a substantive response or instructions on how to retry the payment. My questions: Can Apple retry the $99 payment using my existing payment method? Is there a way to manually complete payment for my existing order? Can I safely enroll through the Apple Developer app instead, without creating a duplicate enrollment or risking a second charge? Could an Apple Developer Support representative review or escalate my existing case? I am ready to complete the payment immediately. The banking restriction has already been removed. I would really appreciate any assistance in resolving this issue before my order is cancelled. Thank you for your time and support.

When trying to access new Siri in macOS 27 beta 7 it always showing 'I’m having trouble with the connection. Please try again later.'. Tried changing the language multiple times and restarted the mac as well. But nothing resolved the issue. Has anybody faced this issue. is this related to network settings ?.

Hello Apple App Review team, My first iOS app submission, Gymestix 1.0, has remained in Waiting for Review since October 8, 2026, at 12:41 AM. As of October 29, the submission has been waiting for 21 days and still has not transitioned to In Review. I have already contacted Apple Developer Support and followed up on my existing support case approximately five times, but I have not received a meaningful response or an update explaining the delay. I understand that review times can vary. However, this is my first release, and I have no way of knowing whether the submission is correctly queued, blocked by an issue requiring action, or awaiting additional verification. Could someone from App Review please investigate the submission and confirm whether any action is required from my side? I am not requesting expedited review without a qualifying reason. I am requesting a status check and assistance with an unusually long delay. I can provide my existing support case number and any additional submission details through a private channel. Thank you.

Hello App Review team / fellow developers, Our first iOS app has been pending for 22 days across two review cycles and has now been in “Waiting for Review” for 12 days with no status change and no message. I’d be grateful if someone from App Review could take a look, or if anyone has seen the same pattern this month. App details App: PropTek Apple ID: 6746718503 Bundle ID: com.proptek.proptek Version / build: 1.0.3 (120) Submission ID: 31f34ed9-ceef-4353-8a31-6afc3c7f7e4b Team: PropTek Realty Private Limited (Team ID D9GG49R3XC) Timeline 7 Oct 2026 – Build 120 submitted (resolved the Guideline 5.1.1(iv) issue raised on build 119). 16 Oct 2026 – After 9 days in “Waiting for Review”, rejected under Guideline 2.1(a): the reviewer could not sign in. Cause was a demo account our QA team deleted by mistake on the review day, not an app defect. 17 Oct 2026 – Demo account restored and verified; Sign-In Information and Notes updated with the mobile number and static OTP; replied in the submission thread; resubmitted the same build. No binary changes. 17–29 Oct 2026 – “Waiting for Review”, no movement, no messages. What we have already done Replied in the submission thread (17 Oct, 22 Oct and 29 Oct), including a request for a call. Submitted a status inquiry via Contact Us → App Review. Requested an expedited review. Verified: Agreements, Tax and Banking are active; no pending agreements; no unread messages in App Store Connect; demo account and backend are live and tested on iPhone and iPad. We have not removed or resubmitted the submission, per Apple’s guidance that doing so restarts the review. Questions Is there anything on our side preventing this submission from entering review? Is the current queue genuinely this long for resubmissions, or is this submission stalled? The Android version is already live, and we missed a committed launch date of 19 October, so any guidance is appreciated. Thank you, S S Gill (Director) PropTek Realty Private Limited

Hi all, I'm wondering if anyone else is seeing this right now, or has been through it before. I resubmitted my iOS app (version 1.0, with one In-App Purchase in the same submission) on October 16 after answering a Guideline 2.1 information request. I requested an expedited review the same day and it was accepted. It has now been 13 days, and both the app and the In-App Purchase are still in "Waiting for Review". Nothing in App Store Connect has changed since October 16, and there are no new messages from App Review. I've contacted Developer Support by email several times and once by phone. Their latest reply only confirmed that the expedited review was accepted and that the review "should begin shortly". For those who had a similar wait: How long did it take before the review actually started? Did anything help, such as contacting a different support topic, or cancelling and resubmitting? Or did it just start on its own eventually? I'd rather not cancel and resubmit unless that's known to help. Apple ID of the app, in case it's useful: 6809826557 Thanks.