Apple Maps Guides

We've tried everything, expedited, contacted, resubmitted, no replies, nothing after review has started, and even after our reply, this is from a large app that's been released monthly for over 5 years. If there is a large influx of new vibe-coded apps, perhaps they can go on the back burner for a bit while existing ones that require URGENT releases can at least be approved? Can someone reply to emails or provide some alt solution or updates of any kind? We've contacted support/replied already to any In Review responses (and been waiting for days/weeks), and the ball is in Apple's court. Maybe let an external company handle reviews/App Store business?

Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.

Hi, My app has been stuck in Waiting for Review since February 3rd - that's 14 days now. I've contacted support multiple times and keep getting generic responses that lead nowhere. This is unacceptable. Is there an actual issue with the review system right now? Has Apple stopped working with review contractors? Is there an internal strike movement ? I need a real answer, not another copy-paste response. What's actually going on? I need transparency on what's causing this delay and an estimated timeline.

Hi everyone, I’m hoping to sanity-check App Store review queue times and see if there’s anything I might be missing. I currently have two iOS apps sitting in “Waiting for Review” with no movement: App 1: Apple ID 6758135741 — submitted Feb 6, 2026 at 5:42 PM (11 days in “Waiting for Review”) App 2: Apple ID 6758885884 — submitted Feb 8, 2026 at 4:33 PM (9 days in “Waiting for Review”) In App Store Connect I don’t see any warnings, messages, or visible account issues. Builds uploaded successfully and metadata looks complete. A couple questions for anyone who’s seen this recently: Are 9–11 day “Waiting for Review” times currently normal due to queue volume? Are there common “silent blockers” that can keep an app in this state even without an obvious warning (e.g., Agreements/Tax/Banking, export compliance/encryption, missing compliance answers, etc.)? If this seems unusual, what’s the best next step—Support ticket, Resolution Center, or an expedite request? Thanks in advance for any insight. I

Description I've encountered a consistent hang/freeze issue in SwiftUI applications when using nested LazyVStack containers with Accessibility Inspector (simulator) or VoiceOver (physical device) enabled. The application becomes completely unresponsive and must be force-quit. Importantly, this hang occurs in a minimal SwiftUI project with no third-party dependencies, suggesting this is a framework-level issue with the interaction between SwiftUI's lazy view lifecycle and the accessibility system. Reproduction Steps I've created a minimal reproduction project available here: https://github.com/pendo-io/SwiftUI_Hang_Reproduction To Reproduce: Create a SwiftUI view with the following nested LazyVStack structure: struct NestedLazyVStackView: View { @State private var outerSections: [Int] = [] @State private var innerRows: [Int: [Int]] = [:] var body: some View { ScrollView { LazyVStack(alignment: .leading, spacing: 24) { ForEach(outerSections, id: .self) { section in VStack(alignment: .leading, spacing: 8) { Text

Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.

Hello, In our game we enforce an age gate before showing Game Center sign‑in. Only after the user passes the age gate do we call GKLocalPlayer.localPlayer.authenticateHandler. The reason I’m asking is that we want to reliably detect if the game was launched from a Game Center activity in the Games app (iOS 26+). If the user prefers to enter via activities, we don’t want to miss that event during cold start. Our current proposal is: Register a GKLocalPlayerListener early in didFinishLaunchingWithOptions: so the app is ready to catch events. Queue any incoming events in our dispatcher. Only process those events after the user passes the age gate and authentication succeeds. My questions are: Does player:wantsToPlayGameActivity:completionHandler: ever fire before authentication, or only after the local player is authenticated? If it only fires after authentication, is our “register early but gate processing” approach the correct way to ensure we don’t miss activity launches? Is there any recommended pattern to d

Hi, I’m facing a consistent simulator boot issue that appears to start after iOS 18.2 simulator runtimes and persists in 18.6, 26.1, and 26.2. Observed behavior iOS 18.2 simulator works fine iOS 18.6 simulator does NOT boot iOS 26.1 / 26.2 simulators do NOT boot Tried everything reinstall/clear cache and all and event formatted the system Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding macOS: Sequoia Xcode: 26.1, 26.2 Machine: Apple Silicon Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = 2025-12-26 02:19:27 +0000; IDERunOperationFailingWorker = _IDEInstalliP.honeSimulatorWorker, Session = com apple CoreSimulator.SimDevice CCDECA56-4A59-491B-A830-0F3928FCD957; } Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or