App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

Hi, We are facing an issue where Universal Links are working for most users but failing for some of our clients. For affected users: Links open in Safari instead of the app, or Universal link routing does not work as expected For other users: The same links open the app correctly What we verified Associated Domains capability is configured correctly AASA file is valid and accessible App configuration and bundle ID mapping are correct AASA: https://www.gartner.com/apple-app-site-association Issue Since the problem is only affecting a subset of users, we are unable to: Reproduce the issue consistently Identify when or why the association breaks Ask Has anyone experienced: Universal Links failing only for certain users/devices? What are the possible causes and how can we debug or proactively identify the root cause in such cases? Any guidance would be helpful. Thanks!

Hello App Review Team, I'm hoping someone can take a manual look or point me in the right direction. The iOS build of my app has been sitting in "Waiting for Review" with no status change, while the macOS and tvOS builds of the exact same version have already been reviewed and released. App: VixioTV - IPTV & M3U Player App ID: 6763137740 Platform: iOS (iPhone/iPad) Current status: Waiting for Review Most recent submission: [June 24, 2026] Time in queue: ~24 days with no status change Related case IDs: [your expedited review / Developer Support case numbers] Context I'd like to share proactively: This is an update to an app that is ALREADY LIVE on the App Store (current iOS version 1.2). It is not a new app. The macOS and tvOS versions of this same update have already passed review and are live — only the iOS build is stuck. VixioTV is a bring-your-own-content player: it provides no broadcasts or content of its own. Users connect their own IPTV subscription (API credentials or an M3U URL). There is no registration, subscription, or content sale inside the app. I have submitted expedited review requests and contacted Developer Support, but I've only received generic/automated replies with no change in status. I would really appreciate it if someone could: Confirm whether there is any issue with the build, metadata, agreements, or account that requires action on my side. Indicate whether this is queue congestion or a submission-specific hold. If possible, escalate or trigger a manual review. Thank you very much for your help. Selcuk Kaymaz

So I am adding Catalyst support to my iOS app. I went through and updated my code and Build Settings to add Catalyst support. I can build for any iOS build or macOS build. I went into App Store Connect and then added a macOS build. I am not able to do a single build and archive that uploads a build for both macOS and iOS. I can do a build and archive for "Any iOS Device (arm64)" and it shows up in the iOS test flight. I can do a build and archive for "Any Mac (Mac Catalyst, arm64, x86_64) and it shows in the macOS test flight. Maybe I'm making a bad assumption ( I could not find any documentation on it) but I assumed Catalyst was a single build and archive that showed up in BOTH macOS and iOS sections. The build settings seem to imply the build is good for a single build and archive process. I want this to be a universal app and my assumption doing it that way would keep everything in sync when you push to the App Store. You can already download the app through the App Store but it is a version of the iPad app. I was hoping to make it more native and available in the Mac App Store without the iPhone/iPad app option. Am I making bad assumptions? Will I just have to do two Build and Archives for every build? I just want to make sure I'm doing this correctly and the best way.

Hi, I was wondering about Apple's review queues. I have an app that in waiting for review for almost a week now but review time trackers claim average waiting times less than a day: https://www.runway.team/appreviewtimes My previous experience is also quite inconsistent, can you please shed some light on how things work internally? In this time I have done some improvements on the app that I was considering for the next update, should I cancel and re-submit?

Hello everyone, face with the issue after I download the builds it stuck. Delivery tool: Manually via Xcode Organizer. The same issue also appears when uploading via Fastlane 2.233.1. The issue appeared after only a minor change: one localized string was modified. The important point is that this problem is not limited to this specific app. The same processing/delivery issue is currently affecting multiple apps (24). Apple support team knows about it, but, unfortunately more than 2 weeks, no reply. Could you please help with this? Maybe any advise? Thank you.

Heya, I recently submitted two app updates for two apps, one got reviewed within the hour. The other is waiting for 5 days. The second one is more complex, but also changed the name (core name stayed the same, just added some text) and description, does that effect the que or review? As it's kinda weird that one takes 1h and the other is still waiting while both are submitted within 6h of each other.

Hello, I'm looking for advice because my app update appears to be stuck in "Waiting for Review." Submission date: June 11, 2026 Status: Waiting for Review (it has never changed to "In Review") Type: Update to an existing app (not a new app) This update does not introduce: new subscriptions or paywalls, new payment methods, major changes to the app's business model. I've already: Submitted an App Review Support request. Submitted an Expedited Review Request. Waited for a response, but I haven't received any reply. I've also verified that there are no outstanding agreements or obvious issues in App Store Connect. Has anyone experienced a similar situation recently? If so: Did your submission eventually move into review on its own? Did you have to withdraw and resubmit? Is there another way to contact the App Review team when support requests receive no response? If an Apple staff member sees this, I'd appreciate it if you could check whether my submission or support case may be stuck. Thank you.

Hi, I added two new auto-renewable subscriptions to an existing subscription group: 50GB Monthly 50GB Yearly The other subscriptions in the same group (200GB and 500GB monthly/yearly) have already been approved. However, these two new subscriptions have remained "In Review" for over 3 days without any updates. Is this normal, or could the review be stuck? Has anyone experienced the same issue? Thanks!

Hi, I am working on integrating In-App Purchases (IAP) into a React Native app using the Expo managed environment. I would appreciate guidance on the complete implementation steps for setting up and handling IAP in this context. Specifically, I am looking for: How to configure In-App Purchases in App Store Connect (product IDs, pricing, etc.) Which libraries or Expo modules are recommended for IAP in a managed Expo workflow (e.g., expo-in-app-purchases or react-native-iap)? Step-by-step integration guide — installing the library, adding necessary permissions/entitlements, and any required app.json / app.config.js configuration. How to fetch available products, initiate a purchase, and handle purchase callbacks/receipts in code. Server-side receipt validation — best practices and recommended approach. Handling edge cases such as purchase restoration, subscription renewals, and failed transactions. Any sandbox testing setup required for testing IAP before going live. Any official documentation, sample code, or recommended resources for React Native Expo managed workflow would be greatly appreciated. Thank you!

Hello, Our app has been in "Waiting for Review" status for more than a week, and our previous submission also took over a week to be reviewed. This delay is affecting our planned release schedule. App details: App name: Nhật Luân Kiếm App ID: 6777269196 We'd really appreciate any guidance on the current review timeline, or whether there is anything on our side we can do to help move the review forward. We're happy to provide any additional information if needed. Thank you very much for your time and support. Best regards.

I had appealed an app (new version) rejection more than 10 days back, but have not heard back Also escalated the issue by using 'contact us' on Apple Developer, but no reply to that email as well (Case ID: 102923097346) Is it normal for Apple to: Take so much time? And give no status updates in the meantime?

Hi everyone, We're experiencing an unusually long App Review delay for our tvOS application and wanted to check if anyone else is seeing the same behaviour or has any suggestions. App Details Platform: tvOS Xcode Version: 26.4.1 Submission Type: App Update Distribution: App Store Status: In Review Issue We submitted an app update last week, and it remained in the "In Review" state for approximately one week with no updates. Since there was no progress, we rejected that submission, uploaded a new build, and submitted it again. The new build has now also been "In Review" for the last 5 days. Apple has not rejected the app or provided any review notes or requests for additional information. The status simply remains "In Review". What we've tried Submitted an Expedited Review Request. Contacted Apple using the App Review "Contact Us" option. We have not received any response to either request. Since there is no rejection or feedback, we don't have any indication that there is an issue with the app itself. Questions Is anyone else currently experiencing unusually long review times for tvOS apps? Is this likely to be an App Review backlog or a known issue on Apple's side? Has anyone had success getting a response through App Review support or Developer Support in a similar situation? Is there anything else we can do besides waiting? Any insights or recent experiences would be greatly appreciated. Thank you!

Details: I'm looking for clarification on how Guideline 1.4.3 is applied to tobacco related apps. My app, The Leaf Cellar, was rejected under 1.4.3 with the reasoning that its "current concept is not appropriate" because it relates to tobacco. The app is a private inventory manager. It has no store, no purchasing, no vendor or affiliate links, no discovery feed, and no content directed at encouraging or using tobacco. its only function is personal record-keeping (logging inventory you already own, aging dates, humidity readings). A 21+ age gate is enforced on launch. What I'm trying to understand is the consistency of the guideline, because functionally identical apps are currently live on the store and receiving updates (which means apple must approve the submitted updates.) Existing Apps (not being enforced by 1.4.3): "My Humidor – Cigar Journal": [https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700] "Humidor Journal Pro": [https://apps.apple.com/us/app/humidor-journal-pro/id6751737114] Questions: Is there a specific feature or distinction that separates an approvable cigar-journal app from one rejected under 1.4.3 as a "concept"? If apps in this category are already approved, what's the correct path to have an inconsistent rejection reviewed beyond the standard Resolution Center reply? I have already submitted to the App Review Board.

Hello, I submitted my first app (MYSKN, Apple ID 6773428050) on June 13th. It moved to "In Review" around June 16th and has been stuck there ever since — now over 9 days with no feedback or status change. I have also submitted two support requests through the "Contact the App Review Team" form and have not received any response to either. The app includes a fully functional demo account, Privacy Policy, and all required metadata. Is this normal for a first submission? Has anyone experienced something similar? Any advice on how to get a response would be greatly appreciated. Thank you.

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hi all, My first app submission appears to be stalled (16+ days) and I’m completely in the dark as to what is going on. Apple ID: 6776835006 Submission ID: 236039a0-1668-448a-aae6-486d52e6c5b9 Timeline: Ready for Review: Jun 10, 2026 at 3:22 AM Waiting for Review: Jun 10, 2026 at 3:23 AM In Review: Jun 15, 2026 at 5:05 PM Current status: still In Review as of Jun 26, 2026 I have also submitted 2 support cases that are past 48 hour SLA and an expedited review request, but I haven’t received a response yet. Our TestFlight external build has also been stuck in Waiting for Review for 5+ days now. There are no visible unresolved issues, App Review messages, or missing compliance warnings in App Store Connect. Review notes and demo/testing information are provided. Thank you.

My app has been stuck in "waiting for review" for over a week now. The previous time it was stuck for a few weeks until I posted here for someone to review it. Can somebody please take a look at my app and review it.

Hello, My app JiuGO (App ID: 6779938845) has been stuck in "Ready for Distribution" status since June 22, 2026. I had set an automatic release scheduled for June 22 at 5:00 PM GMT, but the app has not appeared on the App Store after 3 days. Steps I have already taken: Opened 2 support tickets (Case ID: 102922525686) - no response Called Apple Support - was told to wait due to a conference Posted on Twitter @AppleSupport - no response Tried to manually release - button is not available/greyed out The app was fully approved after review. All previous issues were resolved. Build 17 is the approved build. Is there anything I can do to manually trigger the release, or can an Apple engineer escalate this internally? Thank you, Lucian-Stefan Lacatus

The app publication status is remained as "Ready for Distribution". I've manually published it.