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.

My app review has been stuck. The app includes IAP. When displaying purchases, it first needs to retrieve the price list. This price list is hosted on Apple's servers. Retrieving it is handled by the SDK. Possibly due to the sandbox environment, the price list is very difficult to obtain right when Apple's California office starts work. But at other times, it's very fast. Apple's reviewers have never been able to see the prices. I suggested they change their test time to noon or afternoon, but they still couldn't see the prices. This suggests that the network environment used by Apple's review team has poor connectivity to Apple's own sandbox servers. When I received the review start notification, I tested it myself, and it worked perfectly — the price list loaded quickly. I recorded a video and took screenshots to show the reviewers. But they are still testing within their own network environment, so they couldn't see the price list. I suggested they switch to an open network environment for testing, such as cellular mobile data or a coffee shop Wi-Fi. But that doesn't seem to have helped. They still say they cannot retrieve the prices. This has been going on for a week. They test once a day, and I resubmit once a day. I don't understand why they won't test just once in an open network environment — that would allow them to see the price list load quickly, and would also prove that Apple's SDK and sandbox are functional. If the app works fine in the user environment, then there is no problem. If there's an issue in their test environment, it's a network environment issue. Our code has no problem — I can see that it retrieves the price list and purchases work normally. Every day I can only resubmit without uploading a new version. But I can't keep this up forever. I think maybe a supervisor or someone in charge needs to look into this. Our app is com.ayi9.phone.

Hello App Review team, I am an individual developer and I appear to be experiencing a systemic, account-level delay rather than a normal queue wait. My current app "Color Grading App - Gradee" (Apple ID 6778543702) has been in "Waiting for Review" since June 10 - about 10 days - and has not yet entered review. This is a recurring pattern on my account: previous apps also stayed in "Waiting for Review" for an unusually long time (weeks to months) before review even began, regardless of the app's content. Because every submission on this account is affected the same way, I am concerned my account may be under a review hold or flag. Could someone please: Confirm whether my Apple Developer account is under any review hold, enhanced review, or flag. Let me know if anything is required from my side to resolve it. I have open support cases (102914638162, 102918134058) but have not yet received a response. I am not trying to flood support - I just want to understand what is happening so I can fix it. There is also time sensitivity: a marketing video for this app has gone viral and many users are actively searching for it right now. Thank you very much for your help.

So I know apple store connect are strict in term of your app screenshots, you cannot insert some promotional video and you cannot insert any screenshot that does not come from an iphone or official simulator. But I saw earleir someone's app with a screenshot that was like "MOCK" type, it has some 2 sentence description on top and below them the actual screenshot (on a phone simulation mockup lets say). This got me thinking that apple store connect actually tolerate images that are not PURE screenshots? You can actually take screenshots insert them to mockup and then insert that image in app store connect? How to do that and more importantly what to do to make sure it is done in a way apple store connect accepts it? What others things can be done, or best practices?

The owner of the app has cancer & every moment is counting as the situation is getting worse by the hour. It may sound weird, but as you guys know, cancer patients have a lot of requests; he wants to see his app live. I sent the app for review 2 days ago, but it's still in "waiting for review". I will appreciate it if any Apple staff watch this post, will be grateful & begging to review this amazing app faster & make it live. please!

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.

We are experiencing an issue with our iOS application (MotoDealz) distributed through TestFlight. App Details: App Name: MotoDealz Version: 1.4.36 Builds: 48 and 49 Issue: The application installs successfully through TestFlight, but when launched on a physical iOS device it displays only a blank white screen and does not proceed further. Observations: The same build works correctly in the iOS Simulator. Build processing completed successfully in App Store Connect. No crash dialog or error message is displayed. The issue is consistently reproducible after reinstalling the TestFlight build. The application remains on a white screen indefinitely. Environment: Distribution Method: TestFlight Physical Device: iPhone Simulator: Working as expected Has anyone encountered a similar issue where the app works correctly in the simulator but shows only a white screen in TestFlight builds on physical devices? Any guidance regarding diagnostics, device logs, release-build configuration, or TestFlight-specific troubleshooting would be greatly appreciated. Thank you.

Hello everyone, I’m reaching out for some guidance regarding App Store Guideline 3.1.3(c) and an issue we’re facing during the app review process. Here’s the situation: Our app is designed exclusively for organizations (e.g., businesses, schools, etc.) and is not intended for individual users, consumers, or families. Organizations purchase access to our services directly through our website, and we manually onboard them into the app. Individual users cannot register themselves or gain access to the app unless they are part of a pre-approved organization. However, during the app review process, we received the following feedback: We noticed in our review that your app offers enterprise services that are sold directly to organizations or groups of employees or students. However, these same services are also available to be sold to single users, consumers, or for family use without using in-app purchase. We believe this is a misunderstanding because: Our app does not allow individual users or families to register or access the app. All purchases are made outside the App Store via our website, and only organizations can complete these transactions. We manually onboard organizations and their users – there is no way for individuals to sign up or pay for access within the app. We’ve already explained this to the App Review team in App Store Connect, but we’re still facing issues. Has anyone else experienced something similar? If so, how did you resolve it? Here’s what we’ve done so far: Clearly stated in the app description that the app is for organizations only. Ensured that individual users cannot register or pay for access within the app. We’d appreciate any advice or insights from the community on how to better communicate this to the App Review team or if there’s something we might be missing. Thank you in advance for your help! Best regards, Bashar

Hello, I don't understand why Apple states that app reviews typically take 48 hours. In my experience, it has never been completed within 48 hours. It is usually at least 6–7 days, and in some cases I have waited up to two weeks just to receive a response. Another issue is that they never seem to provide all the problems clearly at once. I wait for a response, they point out one issue, I fix it, then after another week or two they identify a different issue that was already present from the beginning. This makes the entire process extremely slow and frustrating. Is there any way to get a faster response from the review team? Has anyone else experienced similar issues with App Review? Thank you.

Hello, My app has been in “Waiting for Review” status since May 28. App ID: 1471317275 The app was transferred to my developer account about two months ago. Since the transfer, previous reviews were completed without any issue, and I have not received any message in the Resolution Center or any indication that something is wrong with this submission. I am not sure if the app transfer could have affected the review queue, but the current submission has now been waiting for an unusually long time. Could someone from Apple please advise what I should do in this situation? Should I continue waiting, contact App Review Support directly, or resubmit the build? Thank you for your help.

Cannot download CSV reports from App Store Connect Analytics. Started this week. When I try to export Analytics data as CSV, the export fails and the page shows this JavaScript error: Cannot read properties of null (reading 'match') The failed request in Chrome DevTools is: POST https://appstoreconnect.apple.com/analytics/api/v1/data/time-series-csv Response: 410 Gone Example Analytics page where it happens: /analytics/metrics?chartType=singleaxis&dateSpec=d7&frequency=day&groupByDimensionKey=campaignId&measureKey=totalDownloads This happens when trying to download/export CSV reports from App Store Connect Analytics. I also tried bypassing the service worker, but the request still returns 410 Gone from the server. Tried Chrome and in Firefox clearing cache and storage and incognito but still failing.

Rejected under Guideline 4.2 - a native crypto wallet + Web3 browser flagged as "just a web browser." Looking for guidance. I'd appreciate the community's and Apple engineers' read on a 4.2 (Minimum Functionality) rejection, because I believe the guideline was misapplied and I want to resolve it correctly. WHAT THE APP IS Everything Black is a native iOS app (SwiftUI, iOS 18+) built to platform Black-owned businesses, history, culture, and content, and to preserve it in one place. There is nothing else like it on the App Store. It combines a community hub, a Web3 layer, and an on-device crypto wallet. Native non-custodial wallet (GuapcoinX / GUAP token). This is core, and none of it is possible on the web. A 12-word recovery phrase is generated on the device with native BIP-39 / BIP-32 key derivation. The private key is stored in the iOS Keychain, so it never leaves the device or touches a server. Every transaction is gated by Face ID via the native LocalAuthentication framework. Transactions are signed on-device (secp256k1) and broadcast to the GuapcoinX network. Web3 and blockchain domains. The app registers and resolves on-chain domain names, .guap and .hbcu, and routes to them. These are real blockchain writes initiated and signed by the user. To my knowledge this is the only iOS browser that resolves these domains natively. Native AI assistant. A native SwiftUI chat that returns tailored Black-owned business recommendations from a ZIP code. Native directory and Discover. A native SwiftUI feed and search over a directory of Black-owned businesses, news, podcasts, wikis, resources, and a community board, preserving Black culture and content in a single app. A browser tab is included so users can open community and Web3 sites and reach their .guap and .hbcu domains. It is one tab among several, not the substance of the app. THE REJECTION Guideline 4.2, Design, Minimum Functionality. The app provides a limited user experience as it is not sufficiently different from a web browsing experience. Including features such as push notifications, Core Location, or sharing do not provide a robust enough experience to be appropriate for the App Store. (Screenshot of the rejection attached.) WHY I THINK 4.2 DOESN'T FIT The rejection says the experience is not sufficiently different from a web browsing experience. But the core of the app is a native crypto wallet doing on-device key generation, Keychain storage, biometric-gated signing, and on-chain transactions, capabilities a website physically cannot provide. The App Store hosts many approved apps that pair an in-app browser with a native wallet and an AI assistant, which is exactly the combination here. I suspect the native functionality was missed because the app opens on the Home and browser tab, so the reviewer may not have reached the Wallet and Assistant tabs. MY QUESTIONS First, for those who've cleared a 4.2 on an app with a genuine native wallet: did a Resolution Center reply work, or did you have to change the app or metadata? Second, is it worth changing the default launch tab to a native screen such as the Wallet, so the native functionality is the first thing a reviewer sees? Third, is there any guidance from Apple on how an in-app browser should be positioned so it isn't read as the whole app? Thanks in advance. G u i

Hi everyone, I am currently completely blocked from submitting my new app for TestFlight Beta Review (External Testing). The App Store Connect web interface fails to submit, and when I try to bypass the UI using the App Store Connect REST API to create a betaAppReviewSubmissions request, Apple's servers return the following 422 error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Here is what I have already checked and verified on my end: Agreements, Tax, and Banking: My "Paid Apps Agreement", "Free Apps Agreement", "U.S. Tax Forms", and "Bank Accounts" all clearly show as "Active" status. There are absolutely no pending banners or unaccepted agreements on developer.apple.com or appstoreconnect.apple.com. Apple Developer App: I logged into the official iOS Apple Developer app with the Account Holder ID, and there are no hidden agreements to accept there either. App Privacy: All data collection questions are answered, and the App Privacy section is fully Published. Test Information: All required Beta App Review details (Name, Email, Phone) are correctly filled. Export Compliance: My Info.plist includes <key>ITSAppUsesNonExemptEncryption</key><false/>, and the build attributes confirm it. It appears that my TestFlight beta contract has somehow become detached, bugged, or failed to provision on Apple's backend. Has anyone experienced this specific API error recently? Is there a way to force the system to re-provision the contract, or does this strictly require manual intervention from an Apple Engineer? Any guidance would be highly appreciated. Thanks!

We are unable to submit a valid build for external TestFlight beta review because App Store Connect reports that the beta contract is missing for the app. App: Nagram App Apple ID: 6781000861 Bundle ID: xyz.nextalone.nagram Version / build: 12.8 (33174) Build ID: ac9516ad-b435-4d2f-ae3f-2d8abaec023d The UI path is App Store Connect > Nagram > TestFlight > External group > Builds > Submit for Review. The UI shows: There was an error processing your request. Please try again later. The underlying POST to /iris/v1/betaAppReviewSubmissions returns: HTTP 422 code: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING title: Beta contract is missing for the app. detail: Beta Contract is missing. error id: 89b6d5d0-194d-4467-a75c-741aa285e1b7 I checked the surrounding state: The build is VALID, expired=false, and externalBuildState=READY_FOR_BETA_SUBMISSION. Beta App Review information exists. Beta app localization exists. Build What to Test exists. Beta license agreement exists. Account-level Free Apps and Paid Apps agreements show Active / InEffect. Bank, tax, DSA, and account compliance entries show Active. The current user has Admin / Legal / CIPS roles and current ASC terms are signed. This same external TestFlight group previously had approved builds, so external testing worked before. I also opened Developer Support cases, but this looks like an Apple-side missing or detached TestFlight beta contract state for this app/account. Recent support case IDs: 102919547161 and 102919547336. Has anyone seen this state repaired without creating a new app record? Is there any App Store Connect action that can re-provision the beta contract state, or does Apple need to repair it server-side?We are unable to submit a valid build for external TestFlight beta review because App Store Connect reports that the beta contract is missing for the app. App: Nagram App Apple ID: 6781000861 Bundle ID: xyz.nextalone.nagram Version / build: 12.8 (33174) Build ID: ac9516ad-b435-4d2f-ae3f-2d8abaec023d The UI path is App Store Connect > Nagram > TestFlight > External group > Builds > Submit for Review. The UI shows: There was an error processing your request. Please try again later. The underlying POST to /iris/v1/betaAppReviewSubmissions returns: HTTP 422 code: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING title: Beta contract is missing for the app. detail: Beta Contract is missing. error id: 89b6d5d0-194d-4467-a75c-741aa285e1b7 I checked the surrounding state: The build is VALID, expired=false, and externalBuildState=READY_FOR_BETA_SUBMISSION. Beta App Review information exists. Beta app localization exists. Build What to Test exists. Beta license agreement exists. Account-level Free Apps and Paid Apps agreements show Active / InEffect. Bank, tax, DSA, and account compliance entries show Active. The current user has Admin / Legal / CIPS roles and current ASC terms are signed. This same external TestFlight group previously had approved builds, so external testing worked before. I also opened Developer Support cases, but this looks like an Apple-side missing or detached TestFlight beta contract state for this app/account. Recent support case IDs: 102919547161 and 102919547336. Has anyone seen this state repaired without creating a new app record? Is there any App Store Connect action that can re-provision the beta contract state, or does Apple need to repair it server-side?

Hello App Review team, My external TestFlight build has been in "Waiting for Review" for Beta App Review for about 2 days (~46 hours) with no status change. App: GlazingTime Version: 1.1.0 (build 13) This is the first external-testing (Beta App Review) submission of this build. I've checked and there are no "Missing Compliance" or action-required flags on the build — export compliance is set (ITSAppUsesNonExemptEncryption = false) — so as far as I can tell nothing is pending on my side. Could you let me know if anything is holding it up, or check on its place in the queue? Happy to provide any additional details. Thank you.

Hello App Review Team, My team's first app submission has been in "Waiting for Review" status for 17 days with no movement, and I would appreciate any visibility you can provide on its current state. Submission details: App name: Motor İzleme Submission ID: fb2151a2-969e-458b-b57b-9fc7a982e168 Submitted: May 20, 2026 at 10:24 PM Version: 1.0 (build 2) Current status: Waiting for Review (17 days) Account type: Organization (first submission under this account) About the app: Motor İzleme is a hardware companion app that communicates with our physical device over Bluetooth Low Energy. Because reviewers cannot physically test the device without the hardware, we have provided the following materials with the submission to support the review: A demonstration video showing the full app-to-hardware interaction (linked in App Review Notes) Detailed App Review Notes explaining the BLE communication flow App screenshots covering all primary screens Clear handling of the no-device state (the app does not crash or hang — it shows appropriate prompts when Bluetooth is off or no device is found) I want to be transparent: I am not requesting expedited review and I understand the team is operating under heavy submission volume in 2026. I am simply asking whether this submission may have been overlooked, or whether there is anything additional I can provide to help the review proceed. This launch is tied to a commitment with our business partner, and the extended delay is beginning to impact business obligations on our end. Any update would be greatly appreciated. Thank you for your time. Best regards, Saadettin Yıldırım

I am using CI/CD method to build my apps, i dont have xcode simulator, so I cannot produce 13'' screenshots And I have an ipad that is NOT 13'' what can I do? I am locked out from releasing on ipads?

Expedited review requested 24h ago but no response, missed launch date

Hi there, this is my first app, so please be gentle. I submitted it on 6/16 (3 days ago) and I saw somewhere that it took 24-48 hours to be reviewed, and I believe that's when the people I invited to test it would start getting their email invitations. It's still at "Waiting for Review" on the Test Flight tab. Is this the same as THE "app review"? Or is it some "mini-review" for Test Flight? Either way, when should I start following up?

Hello, I am reaching out regarding a critical review delay affecting Summer Rockz (App ID: 6763247379), a European festival discovery app. Version 2.0.0 has been in "Waiting for Review" since June 16, 2026 at 17:30 CET with no movement. Review history for v2.0.0: June 3 — Submitted for review June 4 — Rejected (Guideline 1.1) June 4 — Addressed and resubmitted same day June 16 — Rejected again (Guideline 1.1) June 16, 17:30 — All issues addressed and resubmitted Today, June 19 — Still "Waiting for Review", 3 days with no status change What I have already done: Submitted an Expedited Review request with a documented business justification (summer festival season, time-critical launch window) Opened multiple support tickets Responded in detail to both rejection notices via the Resolution Center Why this is urgent: Summer Rockz serves a seasonal audience tied to the European festival calendar. June and July are the peak months. Every day of delay directly impacts active users and partner festivals that depend on the app being live. The app has no unresolved guideline issues. Both rejection points were addressed immediately and documented in the Resolution Center. Could someone from the App Review team investigate whether this submission is stuck or flagged? I am not asking to bypass the process — I am asking for visibility on a submission that appears frozen with no review activity after 3 days. Thank you.