Hi all, I'm launching my first iOS app (Capacitor/Next.js WebView wrapper) with two auto-renewable subscriptions via RevenueCat, and I'm stuck on a persistent issue across multiple App Store Review rejections. Setup: Bundle ID: no.skaren.app Two auto-renewable subscriptions: no.skaren.app.premium.monthly and no.skaren.app.premium.yearly, both in a single subscription group RevenueCat integrated via @revenuecat/purchases-capacitor App-Specific Shared Secret added to RevenueCat App Store Connect API key (with correct Key ID/Issuer ID) added to RevenueCat Paid Apps Agreement: Active Bundle ID in RevenueCat matches exactly RevenueCat API key in app code matches dashboard exactly The problem: On a physical device (TestFlight build, signed into Sandbox Apple ID), calling Purchases.getOfferings() always returns: {"current":null,"allKeys":[]} No errors are thrown — the offerings object is just empty. This happens consistently across multiple builds, after removing a conflicting limitsNavigationsToAppBoundDomains WebView restriction (which was separately causing a blank-screen bug, now fixed and confirmed working on-device). App Store Connect status: This is our first subscription submission ever. Both subscription products currently show "Developer Action Needed" status in App Store Connect (their localizations were rejected once for vague wording, fixed and resaved, but the products remain in this state). App Review's rejection message explicitly states: "Apple reviews In-App Purchase products in the sandbox and the In-App Purchase products do not need prior approval to function in review." However, our experience suggests otherwise — RevenueCat returns zero offerings, and App Review's own testers also report an "error message displayed on the subscription page" when attempting to test the IAP flow. Question: Is it actually true that subscriptions in "Developer Action Needed" / not-yet-approved status can still be fetched via StoreKit/RevenueCat during sandbox testing? Or does the first-ever subscription submission genuinely need to be approved (i.e., go through the review cycle once) before getOfferings() will return populated data? Has anyone encountered this exact "chicken-and-egg" situation, where the first IAP submission can't be tested until reviewed, but review fails because it can't be tested? Any insight into whether this is expected sandbox behavior for first-time subscription submissions, or whether there's a configuration issue I'm missing, would be hugely appreciated. Thanks!

The app is waiting for review since April 22 (nearly 2 months!) with no sensible outcome. The first review never happened I contacted support several times and after more than 40 days I just deleted the submission and created a new one which was quickly rejected on June 3 with the following reasons: The app contains hidden features. The app provides a limited user experience as it is not sufficiently different from a web browsing experience. The reasons do not reflect the reality and I explained why this fully native app, high performance app can't be considered as it provides a limited user experience nor does it contain any hidden features. I referred to the video and explained the tech stack that could falsely trigger any webview concerns. On June 9 I had a call with Apple representative. Before anything the representative suggested for me to do something else in life and not chase the outcome of the review (!). In the end of the meeting he suggested I submit the appeal and so I did right after the call. 30 minutes later I was contacted via mobile by the same representative and he asked to not submit the appeal as they might have a resolution for my review and should just resubmit the same version. I did as suggested and the app has been waiting for review ever since with no communication whatsoever. Does anyone else have similar experience? Anything I can do at all? Submission ID c37cc165-1f58-435a-a394-35fbbee787f8

Hello Apple Staff, I’m posting again because this issue has not been resolved yet. We currently have two active apps under the same developer account that are still in Waiting for Review. For one of the affected apps, the details are as follows: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 We also tried to submit an expedited review request, but the expedited review form does not complete successfully. The following error message is displayed: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” Could Apple Staff please check the current status of these review submissions and let us know if any additional action is required from our side? We would greatly appreciate your assistance, as the review process has not started and we are currently unable to submit an expedited review request. Thank you for your time and support.

This is our second App Store submission for Rex, a social entertainment discovery app whose core features depend on account-based personalization, saved history, and social/group functionality. Rex’s core features include Rex AI, which provides personalized movie and TV recommendations, along with social watchlists and Party Mode for group recommendations. These features do not function in any meaningful way without an account because they rely on user preferences, saved history, social connections, and persistent recommendation data to deliver the intended experience. Our app is being rejected under Guideline 5.1.1(v), even though account-based functionality is central to the premise of the product. Sign-in is not being used as a gate in front of otherwise accessible content. It is required because the product itself depends on an account-based experience. We have now received the same generic rejection message twice, with no indication that our previous responses were reviewed or considered. We submitted detailed explanations of how Rex works and why sign-in is foundational to the experience, but those points have not been acknowledged or addressed. The responses we have received do not engage with the specific nature of our app, do not address the 5.1.1(v) exception for apps whose core functionality is account-dependent, and appear to repeat the same form language without responding to the context we provided. This is a significant investment of time and resources, and we are trying to understand what Apple is specifically asking us to change. We are not trying to gate free content behind a login. We are trying to ship a product that, by design, requires an account for its core functionality to work. Can someone from Apple or the developer community help clarify how Guideline 5.1.1(v) should be applied to apps where personalization, social features, saved history, and group recommendations are the core product experience?

Hi everyone, App Name: StAIle Build: 6 (Version 1.0.0) I submitted this build for TestFlight external testing on June 12, 2026. It has been stuck in "Waiting for Review" status ever since (6+ days now), well beyond the typical 24-48 hour window. What I've tried so far: Sent an email to App Store Connect support — no response after 2+ days Submitted an expedited review request via the official form — still waiting on that too No message in the Resolution Center, no compliance flag I'm a solo developer trying to run external beta tests before submitting the app for full App Store review, and this delay is blocking that step entirely. Has anyone else experienced something similar recently, or found a way to get this moving? Any advice appreciated. Thanks!

I’ve been using the Age Assurance support page and related Developer News posts as the source of truth for understanding Apple’s expectations around Age Assurance on Apple platforms: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/news/?id=sg176nne Can anyone from Apple clarify whether anything has recently changed with App Review expectations related to Age Assurance? Specifically, are there any new requirements or updated guidance around implementing technologies like DeclaredAgeRange or PermissionKit? I didn’t see any sessions or announcements that indicated these frameworks are now required but with all of the new child safety announcements I thought I'd ask and document for the developer community. I did see the new sample code for implementing Age Assurance and permissions, but nothing suggesting their use is mandatory for App Store approval. https://developer.apple.com/documentation/declaredagerange/implementing-age-assurance-and-permissions Just trying to confirm whether current guidance remains the same, or if App Review expectations are evolving.

I have been waiting for 18 days for review my app. I don't know why or because many app AI Slop is waiting for review?

Body We are currently evaluating an architecture approach for an iOS application and are looking for guidance on App Store Review expectations and platform limitations. Context We are modernizing an existing healthcare application that handles regulated data (PHI). The application is intended for use by internal staff and authorized third-party contractors (not a consumer-facing app, and no monetization). To support iOS distribution, we are evaluating packaging an Angular-based Progressive Web App (PWA) using a lightweight native wrapper (e.g., via PWABuilder), resulting in a WebView-hosted application. Proposed Architecture Angular PWA hosted remotely and loaded via HTTPS Packaged inside a native iOS container (WKWebView-based) Authentication via Passkeys (WebAuthn / FIDO2) Backend APIs implemented in .NET Limited offline functionality using IndexedDB (non-sensitive data only) No persistent storage of sensitive data on-device The native wrapper primarily provides distribution and lifecycle management; most functionality is delivered via the hosted PWA. Key Consideration This application is not intended to function as a general-purpose browser, but rather as a purpose-built, workflow-specific experience for healthcare operations. Questions 1. App Review / Guideline 4.2 Have developers had success getting WebView-hosted applications (primarily PWA-driven) approved when they provide a complete and production-grade user experience? How does Apple typically evaluate whether such an app meets the “minimum functionality” requirement versus being considered a repackaged website? 2. Dynamic Content / Updates Are there specific restrictions on delivering functionality dynamically via server-hosted content after app approval? At what point would backend-driven changes require a new App Store submission? 3. Data Storage & WebView Behavior Are there notable differences in how iOS handles storage (e.g., IndexedDB, local storage) in: Safari-installed PWAs WebView-based apps distributed via the App Store? Are there known limitations or caveats when relying on IndexedDB within WKWebView? 4. Platform Capabilities Are there practical limitations for WebView-based apps related to: Offline functionality File handling Long-term platform support 5. Healthcare / Regulated Data For apps handling regulated healthcare data (PHI), are there additional expectations or best practices (beyond standard guidelines) that Apple reviewers typically look for? Goal We are trying to determine whether this architecture is viable for App Store distribution before proceeding further with implementation. Any insights, experiences, or pointers to relevant documentation would be greatly appreciated.

I submitted my app to App Review on June 5, 2026, and it has remained in the "Waiting for Review" status ever since. As of today, it has been waiting for review for 16 days without any updates from Apple. This is my first time experiencing such a long delay, and I wanted to ask if anyone else is facing similar review times recently or if there is anything I can do to expedite the process. App Details: Submission Date: June 5, 2026 Current Status: Waiting for Review Waiting Time: 16 Days Any guidance or shared experiences would be greatly appreciated. Thank you.

Hi everyone, My TestFlight build has been stuck in 'Waiting for Review' for over 32 hours and I'm hoping someone can help or share their experience. The situation: I have an External Testing group with a Public Link set up. The build was submitted for Beta App Review on March 19th but it's been over 32 hours with no update. I have 25+ testers waiting to install the app. What I've tried: Waited patiently Checked App Store Connect multiple times No rejection emails received No issues flagged by Apple Questions: Is anyone else experiencing unusually long review times for TestFlight external builds right now? Is there anything I can do to speed up the process or check if something is wrong? Has anyone successfully resolved this by contacting Apple Developer Support directly? Any advice would be greatly appreciated. Thank you! Apple Support Case ID: 102846633409

Hello, I am posting here because I have exhausted the normal support channels and I am seeking clarification from Apple engineers or the App Review team regarding an unusually prolonged review process. Current situation Application submitted on May 28, 2026 Status has remained "Waiting for Review" since submission (20 days). An expedited review request was submitted and approved by Apple but the status remains unchanged. Case reference: case IDs (102907712466 and 102915319049) If any Apple engineer or App Review representative is able to provide help or guidance, I would be extremely grateful. Thank you for your time and assistance.

Hello, I noticed the webhook event BUILD_BETA_DETAIL_EXTERNAL_BUILD_STATE_UPDATED does not fire when a build is submitted for external beta review. It is only fired when the review completes. It would be great if we can get notified when an external beta review has started, similar to how we do get notified when a review gets started for the App Store build. Thank you for your time and consideration.

Hi, I'm the founder of a small independent mobile app company based in Istanbul, Turkey. I'm sharing this because I'm trying to understand whether anyone else has experienced something similar and whether there are any realistic paths forward after a final Apple Developer Program termination. In April 2026, our app received several App Review rejections. We addressed the issues raised by Apple and submitted updated versions of the app as requested. On April 27, 2026, we received a Pending Termination Notice alleging App Review circumvention. We submitted a formal appeal on April 28 and followed up with additional information and documentation on May 15. On June 2, Apple informed us that our appeal was insufficient and that our membership would be terminated. What caught my attention was that the same communication also stated that submitting a reinstatement request could potentially lead to reconsideration. I took that seriously. We immediately shifted our focus toward a complete compliance review of the app, brought in outside assistance, and reviewed everything we could think of: app metadata, screenshots and marketing assets, user flows, source code, business logic, and third-party integrations. The changes were not cosmetic. Entire features were removed, workflows were redesigned, and significant parts of the application's architecture were revised. Our goal was to address every concern we could identify and submit a comprehensive reinstatement request. Then, on June 6, before we were able to complete and submit that request, we received the final termination notice. To be clear, I'm not claiming Apple made the wrong decision, nor am I posting this to generate outrage. What I found difficult to understand was being told that reinstatement could be considered, investing significant time and resources into preparing that submission, and then receiving a final termination before having the opportunity to submit it. For context: We never used external payment systems. We never purchased or manipulated ratings or reviews. We never distributed binaries hidden from App Review. We never intentionally attempted to deceive Apple or bypass review procedures. I'm 24 years old and this is my first company. Looking back, I can see that some of my decisions came down to inexperience. That's exactly why I took the reinstatement process seriously. I wanted to fix what I could. A few questions: Has anyone received reconsideration after a final Apple Developer Program termination? Has anyone experienced receiving a final termination while actively preparing a reinstatement request? Are there any official communication channels available once App Store Connect access has been removed? Thank you for reading. Batuhan Özdemir Founder, Liquid Apps Team ID: 7K3Z69D85W

Hi everyone, Thanks in advance to anyone who shares their experience.

We are stuck in AppStoreConnect limbo. We have a new subscription group + two Subscriptions in Ready To Review state in appstoreconnect, but Apple Review rejected our latest app version because they weren't included with the version. Our app version has been rejected for a few issues before this which maybe broke something. When I go to edit the version, there is no Subscriptions & Purchases section to add them for review. I tried editing the subscriptions and subscription group localization to see if that got it out of Waiting For Review state or showed the version section but no luck. So we can't add the Subscriptions for review and we are rejected from App Review if we don't. I submitted an Apple support email 8 days ago and haven't received any response. Does anyone know of a way to get this unblocked?

Hi everyone, I’m trying to understand if what I’m seeing in App Store Connect is normal, or if there’s something I should check on my side. I submitted an iOS 1.2 app version for App Review and I also submitted a TestFlight beta build around the same time. Both are still showing as Waiting for Review. The app version was submitted Thursday at around 10:59 PM, and the beta build was submitted Thursday at around 6:48 PM. Usually my beta builds have moved much faster than this, so I’m not sure if this is just current review backlog or if having both the app version and beta build waiting at the same time can slow things down. A few details: App: Mossly: Plant Care Journal Platform: iOS Version: iOS 1.2 Beta build: iOS 1.2 (40) Both currently show: Waiting for Review I haven’t received any message from App Review asking for more information. Has anyone else seen TestFlight beta review and App Review sit in “Waiting for Review” for several days at the same time? Is there anything I can do besides wait, or any setting/submission state I should double-check? Thanks.

Hi Apple, I'm reaching out because my app Lynup (Bundle ID: ai.lynup.app, Apple ID: 6766385801) has been stuck in "Waiting for Review" since May 6, 2026 — that's now over 19 days with no movement. Here's what I've already tried: Submitted an expedited review request — twice Opened a support ticket with App Review (Case ID: 102892962160) on May 18, 2026 Despite both actions, the status hasn't changed and I haven't received any meaningful update beyond the initial acknowledgment. This is a first submission and the delay is significantly impacting our launch timeline. Any help, advice, or update would be greatly appreciated. Thanks in advance.

Hello, Our app Hook — Smart Message Assistant has been stuck in “Waiting for Review” since June 9, 2026 — 8 days after resubmission addressing all issues raised under Guideline 3.1.2(c) (Subscriptions). Timeline: • June 8: Rejected under Guideline 3.1.2(c) • June 9: Resubmitted with all issues resolved June 9 onwards: Stuck in “Waiting for Review” with no movement We have submitted 3 expedited review requests, all approved. We contacted Developer Support via email and through App Store Connect messages with no response. We are a small team with an active marketing campaign dependent on this launch. Every day of delay has direct business impact. Could the App Review team please investigate this submission? Thank you, Eden

I am writing to follow up regarding the reactivation of our Apple Developer account. We paid the amount requested for the reactivation of the account on the 6 of July and have not yet received any green light to go ahead, please can anyone tell me what to do?

Hello. We have recently submitted for review an app, which has in it Shopify Customer Account API, which allows users to login using a OTP (currently a 6 digit code) received in their email. The login itself uses OAuth and that API provides access to customer data like orders and addresses. The app was not approved and the reasons cited by the reviewer were: The app uses a third-party login service, but does not appear to offer as an equivalent login option another login service with all of the following features: The login option limits data collection to the user’s name and email address. The login option allows users to keep their email address private from all parties as part of setting up their account. The login option does not collect interactions with the app for advertising purposes without consent. Note that Sign in with Apple is a login service that meets all the requirements specified in guideline 4.8. I would like to receive a confirmation that Shopify's new login system is considered a third party login and that it requires the provision of Apple Login as an alternative. The issue with that is that Shopify Customer Account login differs from other 3rd party providers, where you can use them to authenticate, but store data in your own platform afterwards. In Shopify's case, the data that the app needs resides in their platform. We have currently disabled the Shopify login and we could provide Sign in with Apple, if that's needed for compliance, but it would serve no purpose as it wouldn't provide anything more to the users, than our current guest account. Looking forward for a clarification on that issue.