Overview

Title: In-App Purchases Stuck on “Ready for Review” After App Submission I’m running into an issue in App Store Connect with several consumable In-App Purchases. I have four IAPs that currently show Ready for Review: MetaOp 250k Burst (Free Tier) MetaOp 250k Burst (Paid Tier) MetaOp 500k Burst (Free Tier) MetaOp 500k Burst (Paid Tier) I previously added these IAPs to a submission and later removed them. I have now submitted the app version again, and the app itself is showing Waiting for Review, but these four IAPs are still listed under Drafts as Ready for Review. The issue is that I cannot select them from the In-App Purchases list or attach them to the current submission. They also did not move into the submitted review package when I submitted the app. Has anyone seen this behavior before? Is there a way to reset these IAPs back to Prepare for Submission, or otherwise attach/submit them separately without withdrawing the app version that is already Waiting for Review?

Hello, Our first app submission has been in "Waiting for Review" since Aug 4 with no status change (7 days). Submission ID: ff94d9d2-355f-4e9d-80ec-754d2f115a1f We got rejected due to metadata changes required and we are way behind of our release timeline. The App Review Information section includes a demo account for the business panel, and the customer side is usable without login. Any information about the status would be appreciated. Thank you.

Game Center matchmaking fails for all non-default users on Apple TV — no IDS registration for secondary users (FB24156316) On a multi-user Apple TV (tvOS 26.5, Apple TV 4K 3rd gen), Game Center real-time matchmaking fails for every user except the default user, in every app I've tested — including Apple Arcade titles. Filed as FB24156316 with full logs and sysdiagnose; posting here for visibility and in case anyone has shipped multi-user GC multiplayer on tvOS successfully. My game adopts com.apple.developer.user-management (runs-as-current-user-with-user-independent-keychain). The entitlement itself works: on a secondary user's profile the app runs under that user's persona and GKLocalPlayer authenticates as them — the welcome banner shows the right account. But any GKMatchmakerViewController quickmatch hard-fails within ~9 seconds ("Failed to find players"), and accepting an invite fails with GKError 35 ("not signed in to iCloud") even though Settings shows that user's iCloud as signed in. Unified logs show the root cause. When matchmaking starts, gamed can't provision the player's pseudonym because the current user has no identity-services registration: gamed No URI found on any account -- returning nil gamed Failed to fetch pseudonym for local player. Error: GameDaemonCore.PseudonymManagerError.failedToProvision( internalError: Error Domain=com.apple.ids.IDSPseudonymErrorDomain Code=400 "Invalid URI") For the default user, the identical flow succeeds (identityservicesd … resultCode: 0). Across a full day of log capture — profile adds, a remove/re-add, multiple user switches — identityservicesd never once references the secondary users' accounts: registration for them is never attempted, not attempted-and-failed. Meanwhile gamed advertises the nearby-matchmaking Bonjour service with the default user's identity while the foreground app runs as the secondary user. Reproduction matrix: two apps (my shipping game Extreme Violence and Apple Arcade's Crossy Road Castle, which also runs under the correct persona), both sandbox and production Game Center, two unrelated secondary accounts (both healthy elsewhere). Persists across reboot and profile remove/re-add. Default user unaffected. The documentation says the entitlement is all that's needed ("each person who uses your app will have access to… their own Game Center… you don't have to make any code changes" — WWDC20 session 10645). As far as I can tell that promise is currently unfulfillable for online play: there is no API or Settings path that creates the missing IDS registration. Has anyone seen non-default-user matchmaking work on tvOS, on any version? Is there anything an app can do here, or is this purely an OS-side fix? (Related: thread 782163 — a different tvOS matchmaking failure that DTS confirmed as a bug.)

Hello, My app (App ID: 6797305708) was submitted on August 3, 2026, and has been in "[Waiting for Review / In Review]" status for over 9 days with no movement. I understand review times are longer than usual right now, but this is well beyond the typical turnaround. I have made two attempts to contact Apple about this: There are no messages or requests for additional information from the review team in App Store Connect, and I've confirmed the submission is complete with no pending actions on my end. Could someone from the App Review team please check on the status of this submission? If there's an issue I can address to move things forward, I'd be glad to fix it — I just need some communication about what's happening. Thank you.

Hi everyone, I’m looking for advice from anyone who has dealt with an Apple Developer account “Pending Termination” notice. What happened Yesterday I received a Pending Termination notice for my Apple Developer account (not just a single app). This is a huge deal for me because it affects all apps under the account. The notice cites 3.2(f) and 5.6.2 (Developer Identity). It includes language like: Evidence of Dishonest or Fraudulent Activity You provided fraudulent and/or false account information, documentation, or otherwise falsely represented yourself or your submitted app to Apple either during the account enrollment process or after the account was created. What I discovered (my mistake) After the notice, I did a deeper self-audit and found something that looks bad and could be contributing: One of my apps has a supporting website built from an AI template that look like tea app, the app itself have original code. The Privacy Policy page on the website was empty, and the footer copyright name was wrong (not matching my legal entity). What is correct My company is in Good Standing and my Apple enrollment info, Agreements/Tax/Banking, support email, and App Store Connect privacy policy link are real and consistent. Support email is reachable and we have responded to user emails. App context We never intended to mislead customers or represent ourselves as “Tea App.” Our App has different UI/functionality and a different mission. We knew Tea App had privacy issues (data leaking / targeting real people), so our goal was to build a safer dating-stories app where users share experiences only, we warn users at the beginning of the start of the app and warning when upload posts not to target real person or share real person image (so no identifying real people). When we launched, we also noticed some similar tea apps on the store used hard paywalls, so we wanted something transparent and accessible (no IAP, no ads). App Timeline: Dec 2: Our App launched. The first week was normal: few downloads, and the few posts were general experiences without personal info. ~Dec 9: Downloads suddenly spiked. At first we thought the concept was working, but we quickly realized some users were trying to use Green Tea the same way as Tea App — to target real people. Immediately after: Our team disabled sign-up to stop new onboarding/content until we could design a safer system. This led to Dec 12 onward: 1-star reviews complaining they only saw a “green screen,” which was expected since sign-up was disabled. Following weeks: We tried to reduce privacy risk further (e.g., removing photo upload in the latest version), but Apple review still rejected it as “targeting real people.” We explained our intent in the review notes, but a later response said the app was a “copycat.” Late December (near Christmas): We had limited capacity to iterate quickly due to vacations, but we still monitored and replied to support emails. Jan 5: A user emailed asking to remove a personal image because they thought we were Tea App. We replied promptly, clarified they had the wrong app, and explained that Our App does not host real-person photos. I’m not sure whether this is what triggered Apple’s termination notice, but I’m trying to understand what went wrong and how to respond properly. If anyone has been through something similar especially if you successfully appealed. I'd really appreciate any advice. Thanks for reading.

Hello, I first submitted my app for review on roughly July 26th, and after waiting a while, resubmitted on roughly August 6th, I still am stuck waiting on review and have been given no reason as to why this is happening. Does anyone know why?

Hi Team, Requesting urgent attention for our Apple Developer Program enrollment. Requested documents (ID, employment verification, business registration) were submitted on July 23, 2026 via the upload portal. Initially the verification contact form was missed by our legal contact, later it was reviewed and submitted on August 5, 2026. In this regards, I have raised an issue (Case ID: 20000120413793). Requesting your help in expediting our Apple Developer Program enrollment at the earliest as this delay is affecting our development and release timeline. Thank you very much for your understanding and support in helping us move this forward.

It's been over a month since I tried to update our VAT number on my organization info page. I submitted "Update your organization" info 3 times. They literally have a box for updating that information yet 2 times they replied "oh we don't do that, contact finance". I contacted finance team, got "oh we don't do that, try purchases" .. every single support response was not even addressing what I was trying to change, they would tell me "we don't do invoices for subscription purchase" - completely off topic responses with zero help. I called at this point 8 times, every times waited on the line for over 20 minutes, once over 40, no one picks up. I am trying to change such simple thing how is everyone so incompetent over there. it's insane. Am I in the dog house? How is no one picking up the phone at all.

On iOS 26, a nested Menu (a drill-in submenu) visibly jumps and repositions for about a second the first time a submenu is opened, when the menu lives inside a .sheet that is at any partial-height detent — .medium, or a custom .height(...)/.fraction(...) detent. Reopening the same submenu is smooth. The problem does not occur on iPad, does not occur when the sheet is at full height (.large), and does not occur for a flat (single-level) menu. It reproduces with a completely stock Menu, and also with a UIKit UIButton + UIMenu, so it does not appear to be tied to any specific app code. The trigger is purely that the sheet's presentation host is shorter than the screen — the specific detent type does not matter. Minimal reproducible example (stock SwiftUI only) import SwiftUI struct MinimalRepro: View { @State private var showSheet = false var body: some View { Button("Open sheet") { showSheet = true } .sheet(isPresented: $showSheet) { VStack { Menu("Status") { Menu("Category A") { Button("Option 1") {} Button("Option 2") {} Button("Option 3") {} } Menu("Category B") { Button("Option 4") {} Button("Option 5") {} Button("Option 6") {} } Menu("Category C") { Button("Option 7") {} Button("Option 8") {} Button("Option 9") {} } } .padding() Spacer() } .presentationDetents([.medium, .large]) } } } Steps to reproduce Run on an iPhone (or iPhone simulator) on iOS 26. Tap Open sheet. The sheet appears at the .medium (half-height) detent. Tap Status to open the outer menu, then tap Category A to open the submenu. Observe the submenu on this first open. Expected The submenu appears anchored to its parent item and animates in place, exactly as on iPad and exactly as on the second open. Actual On the first open, the submenu appears in the wrong position / at the wrong size and then jumps (snaps) into place over roughly one second. Subsequent opens of the same submenu are smooth. Has anyone found a way to keep drill-in submenus in a partial-height sheet without the first-open jump? So far the only workarounds I've found change the UX (flatten the menu to a single level, present at full height).

Hi Apple Developer Community & Support Team, I am writing to request assistance or guidance regarding a pending Apple Developer Program Organization Enrollment that has been stuck in processing for 10 days. Enrollment ID: H4B43LU86W Submission Date: July 20, 2026 We submitted our organization enrollment (for a governmental entity) on July 20, 2026. However, our designated Verification Contact has not received any email or phone outreach from Apple to verify authority or complete the enrollment process. We have attempted to resolve this through the standard support channels: Submitted multiple support tickets via the official Developer Contact Us channel without resolution. Requested phone calls where we remained on hold for over 30 minutes without reaching an agent. Has anyone been through a similar issue? In my past experience (mostly with regular companies), the verification contact is contacted within 48 hours. Thank you for your assistance.

I’m seeing a device-only lighting discontinuity on PBR entities that intersect a RealityKit portal plane in visionOS 27. A sharp brightness boundary appears exactly where the portal plane cuts through the entity. The portion outside the portal receives a different physical environment-probe contribution from the portion inside. The behavior is reproducible with two independent cases: A completely static blue sphere positioned across the portal plane. An orange sphere moved through the portal using ManipulationComponent and the standard visionOS pinch gesture. Both spheres use: var material = PhysicallyBasedMaterial() material.baseColor = .init(tint: .orange) material.metallic = 0 material.roughness = 1 Each sphere has the crossing and lighting components attached directly: sphere.components.set(PortalCrossingComponent()) sphere.components.set( ImageBasedLightReceiverComponent( imageBasedLight: portalImageBasedLight ) ) var lightingConfiguration = EnvironmentLightingConfigurationComponent() lightingConfiguration.environmentLightingWeight = 0 sphere.components.set(lightingConfiguration) The portal is created using the visionOS 27 factory API: let portal = PortalComponent.makePortal( surfaceStyle: .init(width: 1.2, height: 0.8), boundaryStyle: .infinitePlane(), boundaryMode: .clippingAndCrossing ) if var component = portal.portalEntity.components[PortalComponent.self] { component.lightingBlendDistance = 0.2 portal.portalEntity.components.set(component) } For the moving sphere, environmentLightingWeight stays at 0 for the entire interval in which any part of the sphere intersects the portal. The realtime environment-probe contribution only begins fading from 0 to 1 after the complete sphere has cleared the plane. However, a spatially sharp edge remains: In a bright physical environment, the outside portion is brighter. In a dark physical environment, the outside portion is darker. With UnlitMaterial, the edge disappears completely. With PBR—even metallic 0 and roughness 1—the edge returns. The static sphere reproduces the issue, so it does not appear to be caused by gesture or lighting-update timing. Changing lightingBlendDistance does not soften this remaining edge. The issue is visible on Apple Vision Pro but not in visionOS Simulator. I watched the portal-lighting section of WWDC24 session 10103 and implemented the recommended EnvironmentLightingConfigurationComponent solution. I have also reviewed the documentation for PortalComponent, PortalCrossingComponent, PortalComponent.makePortal, ImageBasedLightReceiverComponent, and environmentLightingWeight. Is there another component or entity-hierarchy requirement needed to fully suppress the physical environment probe on the host-side fragments of a crossing PBR entity? Or is this a RealityKit rendering issue on physical hardware? Environment: Apple Vision Pro (M5) visionOS 27.0 (24M5326g) Xcode 27.0 (27A5228h) visionOS SDK 27.0 (24M5326e) Here is a minimal standalone Xcode reproduction containing both the static and pinch-draggable spheres: https://drive.google.com/file/d/13qqOlDJVCCtlFcMaHCBpDkVJgRzmNjBK/view?usp=sharing

I am unable to attach my In-App purchases and Subscriptions to my only Draft Submission for my app. My IAP and Subs say "Ready For Review" but Im not able to see or select them to submit them for review.

Heating issues on MacOS 27 Beta on normal browser surfing.

Hello everyone, I'm hoping someone from the Apple Developer support team or another developer who's been through this can help. Enrollment ID: 68UYPM637K Organization: CHARRY - INDUSTRIA E COMERCIO DE CONFECCOES LTDA Timeline so far: This enrollment was submitted by our company's owner/founder, who has the legal authority to bind the organization to agreements. We received a request for identity verification documents (government-issued photo ID, Articles of Association, and CNPJ card for the organization). We submitted all requested documents through the secure upload portal on July 29, 2026 (14 days ago). Checking developer.apple.com/account directly, the enrollment still shows as "being processed," with no further update or request since then. At this point we've submitted everything requested and haven't received any update in 14 days. This is delaying a planned app launch for our company. Has anyone else experienced a delay like this after submitting documents? Is there anything else we should try, or can someone from Apple please take a look at enrollment 68UYPM637K? Thank you in advance for any guidance.

Is anyone else seeing Instagram fail to open App Store links tonight? Started for me a few hours ago, iOS only. To rule out my own setup I put a bare App Store URL straight in my bio, and I also tapped the App Store links on a few competitors' sites. Same result every time: nothing happens, no error, no page. Same phone, same moment: Safari works, Facebook and YouTube work, TikTok fails. Has Instagram started blocking store links the way TikTok does? If so, it looks like we're back to telling people to tap the ⋯ menu and "Open in external browser" before they can install anything.

Hi everyone, I’m currently experiencing unusually long review waiting times and wanted to ask if others see the same behavior this week. My situation: • App Store update has been in “Waiting for Review” significantly longer than usual • A newly submitted build also seems stuck • TestFlight processing is slower than I normally see • Expedited review request and contact attempts didn’t change the status so far What confuses me is that I still see other apps receiving updates, so I’m unsure whether this is a broader review delay or something submission-specific. I’m not trying to escalate anything — just looking to understand if this is currently affecting more developers. Would really appreciate hearing about your recent experiences. Thanks and good luck to everyone waiting 🙂

Seems like there is an issue in Xcode 27 beta 4 & 5 where DeviceHub doesn't show iOS 16 devices or simulators. I've checked the filters to ensure I haven't hidden anything and the are listed in the Xcode destination dropdown.

Environment: Xcode 16, iOS 18 Simulator, Objective-C, Debug build. Problem: After upgrading to iOS 18 SDK, BOOL values behave abnormally exclusively on the iOS 18 simulator: BOOL properties assigned with system API return values are truncated to negative numbers; __block BOOL variable logged as 0, but the function returns a huge negative integer after dispatch_sync, leading to wrong if condition judgment. All code runs correctly on physical iOS devices and Mac Catalyst. I temporarily fixed it by replacing BOOL type with int to store only 0 and 1. I just want to confirm: what changes in iOS 18 Simulator runtime or Xcode 16 compiler lead to this signed char BOOL overflow/extension issue?

Hello! I develop a voicemail app service and I use MMI codes to let users enable/disable call forwarding to their voicemail number. For example, the app opens the Phone app with a code such as: **21*<phone number># This is expected behavior and is required for the service to work. However on iOS 27, those links are now blocked with a “Malicious link blocked” warning, saying that the link may forward incoming calls/messages. Is there any supported way for apps with a legitimate use case like this to request an exemption, or otherwise avoid this warning?

We submitted our first iOS app for review on August 4, 2026 (App ID: 6797034989). Today is August 12, and it has now been 8 days in “Waiting for Review”. Apple’s submission confirmation stated that 50% of apps are reviewed within 24 hours and over 90% within 48 hours. We understand that delays can happen, but 8 days is significantly longer than expected. Since August 8, we have also sent 3 emails to Developer Support regarding this issue, but unfortunately received no response. We have deadlines for our app launch and cannot keep waiting indefinitely without any information. Could someone from App Review or Developer Support please take a look at our submission and let us know if everything is OK? We would really appreciate it if the review could begin as soon as possible. Thank you.