Overview

Hi, My app Duo Queue has been in "Waiting for Review" since September 22, about 160 hours now, with no status change since then. App: Duo Queue: Game Tracker Apple ID: 6809453548 Version: 1.1 (build 21), submitted with the in-app purchase com.adgames.duoqueue.full_shelf Submission ID: 3ff2dc7d-2435-43a3-bc3f-33b1ae3478d2 Submitted: Sep 22, 2026, 09:05 UTC An earlier submission was rejected under Guideline 4.3(a). For 1.1 I rebuilt the core of the app. Users now photograph a game box and the app identifies it, and game detail pages include trailers where available. I also renamed Swift types that shared names with types in my other apps, and attached a demo video for the reviewer. I withdrew the previous submissions for this app, so this is its only active submission in the queue. I know the team has a lot of apps to get through. I'd just like to confirm that the submission isn't stuck somewhere, or find out if I need to do anything on my side. Thank you.

Hi everyone, My app, QuitIt, has been waiting for review for quite some time after my appeal was accepted. I’m keen to get it through the review process and released, but I haven’t received an update on what happens next or whether anything else is needed from me. Has anyone experienced a similar delay following a successful appeal? Is there a recommended way to follow up with App Review and confirm that my submission is moving forward? I understand review times can vary, and I’d appreciate any guidance. Thank you!

Hello, My app 岩片 (YanPian, Apple ID 6800534375, bundle ID com.ajin.heartrate) was rejected on September 19, 2026 under Guideline 4.3(a) - Design - Spam. Submission ID: 69a97b70-0219-42fe-861f-ce737bc19b38, version 1.0 (202609061946). The app is original. I wrote it myself, it is the only app on my account, I have not submitted similar apps on any other account, and I have never used or bought an app template. It is a tool for lead climbers who film their climbs from a tripod far below the wall: Heart-rate overlay: pick a climbing video from Photos. Heart-rate samples recorded by Apple Watch are read from HealthKit (read-only), matched to the video by capture time, and drawn on the video with a heart-rate graph. Zoom and follow: the climber is tiny in a wide shot, so the app crops in and follows them with editable keyframes (on-device person detection). Live capture, with an optional Zhiyun CQ5 gimbal that moves only when the climber is about to leave the frame, and an optional Apple Watch companion. Everything runs on device. No account, no backend. What I have done so far: September 20: replied in App Store Connect with the explanation above. No response yet. September 29: submitted an appeal to the App Review Board. An earlier appeal got no confirmation, and I cannot find any record of it. The review was done on an iPad Air. The app is iPhone-only. Without a climbing video in Photos, the home screen only shows "New project" and "Live capture", so I understand it may look like a generic camera app. A screen recording of the full flow is attached to the submission in App Store Connect. If a specific app looks similar, I would be glad to know which part so I can change it. Could someone from App Review take a look? Thank you.

Trivial pass-through compositor fails on Xcode 27 (beta 2, beta 3); error code -11800 underlying error -12784. Repro included https://github.com/BugorBN/avplayer-custom-compositor-repro It works well on Xcode26 and lower

We ship a ~6.2 GB Apple-hosted managed asset pack and request it with AssetPackManager.ensureLocalAvailability(of:). If the app goes to the background even once while the download runs, the transfer continues to the end and then fails with ManagedBackgroundAssetsProcessingPipeline.Dispatcher.PipelineNotFound. The system discards the resume data, and the next attempt starts again from byte 0. What the sysdiagnose shows: On backgrounding, backgroundassets.user logs allows BG activity, pausing any foreground downloads for background demotion and hands the download to nsurlsessiond. On return it logs re-promoted 1 previously-demoted foreground downloads. Each handoff moves the stream to another STExtractionService.privileged instance, which logs No processing pipeline with the ID "…" was found; defaulting to an extraction memory footprint of 50 MB. When the HTTP response ends: [Relay] No endpoint was found for the key "…" (fault) → The stream couldn't be finished: No processing pipeline with the ID "…" was found → Removing the resumption info → the download fails. This happened on every app-requested download that was backgrounded at least once. One run reached 100 % in the foreground and still failed. The only download that ever completed was the system's own prefetch download, which ran entirely in the background with the app never launched. Over one afternoon about 46 GB were downloaded for a single 6.2 GB pack. Questions: Is this a known issue with the demotion/promotion of foreground asset-pack downloads? Is AssetPack.download(for: nil) plus BADownloadManager.scheduleDownload(_:) a supported way to request a managed pack from the app, so the download never gets foreground priority? We're testing it now. Is there any other way to keep a download requested from a foreground app from being demoted? Filed as FB24888599.

(lldb) p [@"ΗΙzzz" caseInsensitiveCompare:@"ᾚabc"] (long long) -1 (lldb) p [@"ᾚabc" caseInsensitiveCompare:@"ΗΙzzz"] (long long) -1 Note the unicode char in the second string. The results can't be both -1, afaik, if one is -1 the other one should be +1. This causes inconsistent indexing in a sorted array resulting in obscure crashes of my app. Am I doing something wrong? Tested on iOS 27 and macOS 26.6.

Update: I clarified the intended behavior after posting. The destination is the text input that has keyboard focus when the finished dictation is delivered, even if the user changed fields or apps while speaking. We do not need to return to the field where dictation started. I’m building a macOS dictation app for the Mac App Store, so it must run with App Sandbox enabled. For example, a user might start dictating with an input in Chrome focused, then click into a ChatGPT input while speaking. When the result is ready, it should insert at the ChatGPT caret. Moving the caret within one app should likewise change the destination. In an isolated signed sandboxed prototype, I write a marker to the general pasteboard and post Command–V with CGEvent.post after the user grants event-posting access. This inserts successfully in TextEdit at the current caret, including after a same-document caret move. That result is now consistent with the intended behavior. The prototype also has a frontmost-process guard that withholds insertion after an app switch; that is our own guard and could be removed. We have not yet verified cross-app delivery without it. The existing nonsandboxed app uses AXUIElement to inspect the focused field. Apple’s App Sandbox documentation lists assistive Accessibility APIs as incompatible with sandboxed apps. For a current-focus insertion design, is there any supported sandbox-compatible way to know whether the destination has a focused editable field or is a secure input, or to learn whether a posted paste was actually accepted? If not, is relying on the destination app’s paste handling and retaining the transcript for manual recovery the expected approach? I also tested an AppKit Service. TextEdit inserts its returned text when the caret stays put; after a physical click to another caret during a pending request, the provider returns but TextEdit inserts nothing. This does not appear to fit our hold-to-dictate, switch-apps-while-speaking interaction. I’d welcome experience with another system-mediated approach that does. Environment: macOS 27.0, Xcode 27.0, Apple Silicon. I’m asking about technical API behavior and implementation patterns, not a guarantee of App Review approval.

Hello Apple App Review team and developer community, I am Blessing Anumudu, the owner of RAYAAUSTIN LLC and the Account Holder of its Apple Developer Program membership. We received a Pending Termination Notice citing Section 3.2(f) of the Apple Developer Program License Agreement and App Review Guideline 5.6.2 (Developer Identity). Our app, LightXtreme VPN Unlimited (iOS), has been removed from the App Store. We submitted an appeal to the App Review Board six days ago—nearly a week—and have not yet received any response to the appeal. We have also contacted Apple Developer Support. Our support case ID is 102979575702. We understand that a thorough review takes time. However, with our app remaining unavailable and the notice specifying a 30-calendar-day appeal deadline, we would appreciate confirmation that our appeal has been received and is under review. Could an Apple team member help us confirm: The current status of our appeal. Whether any additional information or action is required from us. Whether an estimated response timeframe is available. We have identity, company registration, IRS, banking, and trademark documentation available for verification. Since the appeal form did not allow attachments, please advise how we can securely submit any relevant documents. We will not post sensitive records publicly. Our priority is to resolve the specific concerns, complete any necessary verification, and restore our app to the App Store as soon as possible. We are ready to respond promptly to any requests from the reviewing team. We would appreciate help directing this inquiry to the team handling our appeal, as well as firsthand guidance from developers who have resolved a similar identity-verification issue. Thank you for your time and assistance.

Hi, I'm hoping someone from Apple can help with the review of my app. My initial submission spent around 7 days in "Waiting for review," so I resubmitted it with changes immediately. The resubmission has now been waiting for another 2 days. This app is part of my submission to an ongoing competition, so release timing is important and I'm approaching a deadline. I would really appreciate it if someone could help get the app reviewed as soon as possible. I completely understand that review times can vary, but given the initial 7 day wait and the upcoming deadline, I wanted to reach out and see if there is anything that can be done. Thank you!

I have an app that I am implementing background assets, using self hosted unmanaged. Everything compiles fine, and I get no errors. But I can't figure out how to trigger the 'install' phase into the extension. I have tried copying the app into /Applications without luck. I have deleted the entire DerivedData and all copies of the application. Nothing seems to work. I tried using the Apple provided sample app from here and got the same results. I don't understand why the CLI tool backgroundassets-debug only works with iOS based connected devices? Please let me know how can I test my BADownloaderExtension on Mac via XCode. Thank you.

I've noticed a strange issue with the SceneDelegate lifecycle in iOS 27. [Environment] iOS 27 (Also tested on physical devices) UIKit / SceneDelegate based App [Description & Steps to Reproduce] When the app is in the foreground and the user locks the screen (presses the power button): In iOS 26 and earlier: sceneWillResignActive is called exactly once. (Expected behavior) In iOS 27: The following sequence is called rapidly in succession: sceneWillResignActive (Screen lock initiated) sceneDidBecomeActive sceneWillResignActive (Locks completely) When the user unlocks the screen later, sceneDidBecomeActive is called once as usual. [Impact] Because sceneDidBecomeActive is unexpectedly fired while the device is locking, it triggers foreground logics right before the app is pushed to the background. This is causing unwanted side-effects and glitches. Has anyone else encountered this unbalanced lifecycle issue in iOS 27? I'd like to know if there's a better approach or if Apple is aware of this. Thanks!

Is anyone else having issues uploading an archive to App Store Connect? I went to validate an archive of my app, and seems to hang during validation. I've tried just validating the app, and tried Transporter as well. It hangs on the analyzing app. How to troubleshoot?

I am displaying the same view via a push onto the secondary view of a modern uisplitviewcontroller and alternatively as a uisplitviewcontroller inspector pane. When pushed (initially compact size class, then opened to regular), toolbar items are moved to the side as expected: however when presented in an inspector pane the toolbar items are not moved to the side: The toolbaritems contain one less image in the later case. iOS 27.1 simulator

Hello, We are seeing an issue where AVPlayer sometimes reports time values close to 95,443 seconds (~26.5 hours), even though the actual content duration is much shorter. For example, in normal cases we see: currentTime: ~355 seconds duration: 6958 seconds seekableTimeRange: 0...6958 seconds However, in some cases AVPlayer reports values around: currentTime: ~95443 seconds duration: ~95449 seconds We checked the underlying MPEG-TS segments with ffprobe. The video and audio PTS values are around 6426 seconds and are consistent with the HLS EXTINF durations, so we do not see a 95,443-second timestamp directly in the media segments. Could you please help us understand: 1- Why can AVPlayer expose values close to 95,443 seconds? 2- Could this be related to MPEG-TS PTS wrap-around or AVFoundation timeline mapping? 3- How does AVPlayer calculate currentTime and AVPlayerItem.duration for HLS MPEG-TS content? Interestingly, Audio Only / Now Playing mode shows the expected timeline, while video playback can expose the incorrect values. Thank you.

Environment: Xcode 27.0 beta 6, Device Hub, tvOS 27.0 When focusing a TextField and using Device Hub to run on tvOS 27.0, I cannot type any text into the field. Focus moves to the TextField as expected, but keyboard input is not received. Has anyone else run into this? Any workaround would be appreciated.

I have been trying for 24 hours to upload app, and first time this has happened in 8 years and 100+ uploads. Please help. Validate App and Upload both hang indefinitely at "Preparing" in Xcode Organizer. No error is ever returned — the progress bar freezes and the operation never completes or times out. Transporter 1.4.5 fails identically. Key detail: archive 2.4.3 (build 123), which Apple accepted and processed on Sept 10, 2026, now hangs the same way when validated. Same machine, same Xcode, same Apple ID. This rules out the archive, its signature, and its provisioning profile. Already ruled out: two independent networks (home Wi-Fi and iPhone cellular hotspot); the archive itself (known-good build 123 fails identically); Xcode install (27.0 / 27A266a, xcode-select verified correct); Apple ID session (signed out and back in three times); full reboot. macOS 27.0 (26A428) on MacBookPro18,4. Last successful upload Sept 10, 2026. 100+ prior archives uploaded without incident over several years. macOS has updated twice since Sept 10. Separately: Transporter 1.4.5 crashes on macOS 27.0 with an unhandled exception in TransporterKit while drawing its activity queue (EXC_BREAKPOINT via +[NSApplication _crashOnException:]).

Hi everyone, I submitted my app for App Review on August 14, 2026, at 2:39 PM. I later submitted an updated version again on September 9, 2026. The latest submission has been showing “In Review” for the past 5 days, but I still haven’t received any review decision or additional information from the App Review team. As I understand it, once an app enters the “In Review” status, a review decision is generally provided after the review is completed. However, in my case, the status has remained unchanged for several days. Has anyone experienced a similar situation recently? Is it normal for an app to remain in “In Review” for this long, or is there anything I should do from my side? Any advice or guidance would be appreciated. Thank you!

I am a PSP for Apple Pay, and I have been experiencing timeouts while registering a domain for my merchant. What configurations should my merchant make?

When updating our Developer ID Application certificate, we encountered an issue where the Apple Developer portal consistently returns the exact same certificate file, regardless of the CSR submitted. Observed Behavior & Test Steps: We generated multiple new CSRs using both OpenSSL in the command line and Keychain Access (Certificate Assistant) on macOS following Apple's official guide: https://developer.apple.com/help/account/certificates/create-a-certificate-signing-request We uploaded these distinct CSRs to the Developer Portal (Certificates -> Add New -> Developer ID Application) on separate attempts. After downloading the issued .cer files, we performed a binary comparison (diff/checksum) across all of them. The comparison confirmed that the downloaded certificate files are 100% binary identical across all attempts. Key Pairing Verification: To further verify the key pairing, we checked the public key modulus hashes of the local Private Key and the downloaded .cer file via OpenSSL: Check local Private Key Modulus Hash: openssl rsa -noout -modulus -in new_developer_id.key | openssl md5 Check downloaded Certificate Modulus Hash: openssl x509 -noout -modulus -in developer_identity.cer -inform DER | openssl md5 The resulting MD5 hashes do not match. Attempting to export them to PKCS#12 (.p12) consistently fails with the error: no certificate matches private key. Question: Could this be related to a profile caching or binding issue on our team account, or is there a recommended way to clear this state and obtain a newly issued certificate? Any guidance or advice would be greatly appreciated.

Hi, is there any possibility of developers being able to keep compatibility mode for a particular device model? I know it is possible for the iPad because it is regarded as a different device family from the iPhone. We wonder if it is possible for us to target just a particular model. Say for example, the iPhone Duo.