App Review

RSS for tag

App review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.

Posts under App Review tag

200 Posts

Post

Replies

Boosts

Views

Activity

App stuck in "Waiting for Review" for 15 days — Lift Access (6798906865)
My app has been in "Waiting for Review" since August 8, 2026 — 15 days with no status change and no communication. App: Lift Access Apple ID: 6798906865 Platform: iOS, version 1.0, Submitted: August 8, 2026 This is a new, original app, written from scratch. Another app on the same account (iHike, Apple ID 6787736523) was reviewed and published on July 24, 2026, so the account is active and in good standing. I have not cancelled or resubmitted the build, and I am not asking for priority over anyone else. I would simply like to know whether something is blocking this submission, or whether it has not yet been picked up. If there is an issue on my side that I need to resolve, I am happy to address it — I just have no information to act on. Has anyone seen a submission sit this long recently, and did anything move it?
0
0
141
Aug ’26
First iOS submission stuck in “Waiting for Review” for 6+ days
Hello, My app, Pulse Blocks: Block Puzzle, iOS version 1.0, was submitted on August 14, 2026 at 12:52 PM and has remained in Waiting for Review for more than 6 days. It has never moved to “In Review”. I have not received any rejection, request for additional information, or indication that action is required from my side in App Store Connect. I have also contacted Apple Developer Support, but I have not received a response yet. Could someone from App Review please confirm whether this delay is expected or whether the submission may be stuck in the review queue? I’m happy to provide any additional information privately if required. Thank you.
1
0
604
Aug ’26
Expedited Review Request is taking a long time — any advice?
Has anyone experienced Apple App Review being really slow lately? I already submitted an Expedited Review Request through Apple Developer Support, but it still seems to be moving really slowly. My app is still stuck on “Waiting for Review.” How long does it usually take after submitting an expedited review request? If the request has already been submitted through Developer Support, is there anything else I can do to get Apple to take a look at it sooner? Or is App Review just slower than usual right now and I basically just have to wait? 😭 Would really appreciate it if anyone who recently got an expedited review could share how long it took for them! My App ID is 6800172081
0
0
72
Aug ’26
ITMS-91064 persists across 8+ builds despite verified-correct PrivacyInfo.xcprivacy
I'm getting the following error on every submission (Build 1 through 8), even after multiple clean rebuilds and manual verification of the raw manifest content: ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: "PrivacyInfo.xcprivacy" and also "PlugIns/[WidgetName].appex/PrivacyInfo.xcprivacy" NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn't empty. What I've verified locally (via plutil -p and raw cat on both the .xcarchive and the exported .ipa): Main app PrivacyInfo.xcprivacy: NSPrivacyTracking=false, NSPrivacyTrackingDomains=[] (empty) Widget PrivacyInfo.xcprivacy: same, false + empty No duplicate keys found in either file Generated an official "Privacy Report" from Xcode Organizer - no obvious conflict at the app or widget level was shown Updated GoogleMobileAds/UserMessagingPlatform SDKs to the latest version - issue persists Bundle version increments correctly with each build (confirmed via Info.plist inside the actual uploaded archive) Is there a known caching issue on the App Store Connect validation side, or something else I might be missing? Happy to share the Privacy Report PDF and archive details if helpful.
3
0
395
Aug ’26
Waiting for Review for 6 days
Hi, I submitted my app update (app has been approved) 6 days ago and the status has not changed from "Waiting for Review". Since then, I have updated another app, submitted it for review, it was reviewed and approved within 24 hours. I want to make sure there isn't an issue with my app submission that has been stuck in Waiting for Review for 6 days. Please help!
0
1
211
Aug ’26
Vagus Fit stuck in “Waiting for Review” for 9 days — no response from Developer Support
Hello, My iOS app, Vagus Fit, has been stuck in “Waiting for Review” since August 12, 2026 at approximately 3:46 PM. It has now been about 9 days and the submission has still never entered “In Review.” App: Vagus Fit Version: 1.3.0 Platform: iOS Submitted: August 12, 2026 at approximately 3:46 PM Current status: Waiting for Review Developer Support Case ID: 20000142078727 I already contacted Apple Developer Support through the App Review Status contact form several days ago, but I have not received a response or any update. I have also checked App Store Connect and I do not see any messages, missing information, rejection, or action required from my side. I understand that review times can vary, but this delay is significantly longer than the normal review timeframe. Could someone from Apple please check whether my submission and existing Developer Support case are progressing normally, or escalate the case if necessary? Thank you.
0
0
338
Aug ’26
Waiting for review for 11 days
Hi! I submitted my app for review 11 days ago and have been waiting eagerly for my review. Ive noticed some posts about people having long wait times, but cant seem to find out if they were eventually reviewed or if they resubmitted or something else. I have my app live on other platforms currently and my next big patch is approaching release (1.2.0) whilst i am still waiting for 1.1.0 to be reviewed here on the App Store. Is there a chance the app is stuck somehow? Should i maybe just resubmit with the newer version instead? Or would that cost me my spot in line and just lead to further wait times? I appreciate any help i can get! Thanks Carl
0
0
78
Aug ’26
App submission in "Waiting for review" since 9th August (12 days)
Hello, I submitted our app to the App Store on 9th august and it has been stuck in "Waiting for review". We have a very critical launch date timeline. We have to release our app in the first week of September (before 5th); therefore, we submitted it quite early. But seems like the app is stuck indefinitely in the "Waiting for review" state. We even raised a support ticket for this. No response on that too. App ID: 6799395555 Support conversation ID: 20000139951347 What can be done to expedite this as further delays will cause us to miss our timeline?
0
0
208
Aug ’26
App stuck in waiting for review
My app is stuck in waiting for review for the past 12 days (submitted on 9th August 2026). I am running out of timeline and would appreciate any feedback on the reason for the extended hold, do I have to do anything on my end, when do I expect the app to be reviewed. Would appreciate assistance on this. My App Apple ID: 6799715408 Any assistant will be appreciated as the project timeline is fast approaching.
3
1
390
Aug ’26
Guideline 2.3 rejection citing UIRequiredDeviceCapabilities when the only value is arm64
My app was rejected under Guideline 2.3 (Accurate Metadata) with the standard text saying the UIRequiredDeviceCapabilities key is set up so that the app will not install on the review device. The review device was an iPad Air 11-inch (M3) on iPadOS 26.6. I inspected the Info.plist inside the exact archive that was uploaded. Everything relevant: UIRequiredDeviceCapabilities = (arm64) UIDeviceFamily = (1, 2) MinimumOSVersion = 18.0 Binary architectures = arm64 Built with Xcode 26.6, iOS 26.5 SDK An iPad Air 11-inch (M3) is arm64, is device family 2, and runs an OS far above 18.0, so as far as I can tell nothing in that plist can prevent installation. arm64 is the value Xcode injects automatically, and I have never declared the key myself. What I have already checked: There is no UIRequiredDeviceCapabilities in my source Info.plist and no INFOPLIST_KEY build setting for it. The value is injected at build time. I added the key to my own Info.plist as an empty array to try to override the injection. Xcode still writes (arm64) into the built plist, so I cannot remove it. I built the same Release configuration and installed it on an iPad Air 11-inch (M3) simulator running iPadOS 26.2, the highest iPadOS available to me. It installs and launches with no error. There are no app extensions. One target, TARGETED_DEVICE_FAMILY = "1,2". My questions: Is arm64 in UIRequiredDeviceCapabilities known to trigger this rejection on iPadOS 26 review devices, or is something else being reported under this template? Is there any supported way to suppress the value Xcode injects, or will the array always contain arm64 for an arm64-only binary? If the installation failure was real but caused by something other than this key, what else produces an install failure that App Review would attribute to UIRequiredDeviceCapabilities? Context for why I am asking here and not only in App Store Connect: the build sat in Waiting for Review for about a week and a half, I used my expedited request, it was rejected on this, I replied in Resolution Center with the plist contents and received no answer, and the resubmission is back in Waiting for Review. I am not asking anyone here to change a review outcome. I am trying to find out whether this is a known issue with the key so I can stop guessing. Any pointer would be appreciated.
2
0
350
Aug ’26
Waiting for Review 8 days — no response from Contact Us or phone support
Our first submission has been in Waiting for Review since August 12 — 8 days as of today. I've tried both support channels without result: Submitted a Contact Us request through App Store Connect — no reply Called Developer Support and waited on hold about an hour — no resolution The app is a straightforward iOS-only build (iPhone, no iPad). It's a first submission, not an update. Nothing in App Store Connect indicates a problem — no rejection, no metadata rejected state, no message in Resolution Center. It simply hasn't moved out of Waiting for Review. I've seen several recent threads describing the same thing, which is why I'm posting here rather than opening another ticket. Is there anything on my side that commonly causes a first submission to sit in Waiting for Review this long, or is the only option to keep waiting? Any guidance on the right escalation path would be appreciated. Thanks.
1
0
212
Aug ’26
App Under Expedited Review For 6 Weeks — Previous Build Approved, Resubmitted for Bug Fixes, Launch Date 6 Weeks Ago
Hello App Review team, I am requesting urgent assistance with my app review. Our previous build was approved around 5 weeks after our expected launch date, and last week we had to resubmit with a couple bugs that were fixed during the last review process. It has been 6 days since that submission, with an expedited review, and we are now 6 weeks past our launch date which has resulted in financial losses and dozens of media outlets notified weekly of delays. We would really appreciate if our latest build can be approved, as there are only minor bug fixes since the last one. Apple ID: 6748958042 Original Submission Date: 06/30/2026 Latest Submission Date: 08/14/2026 Current Status: Waiting for Review Support Case #: 20000141845140 Given the previous approval and minor changes since that build, we would greatly appreciate any escalation or update on the status of this review as we are incurring daily losses due to the review delay. Thank you!
0
0
340
Aug ’26
App stuck in "Waiting for Review" for 8 days
Hello, My app submission has been waiting for review for 8 days, and there has been no status update or request for additional information. Submission ID: f9cc5319-693b-4809-8bcb-5eb0e8ad28bd I understand that review times can vary, but this is considerably longer than I have experienced before. Could an Apple representative please check whether the submission is progressing normally or if any action is required from my side? Thank you.
3
0
441
Aug ’26
First app, still waiting on review reply — do I need to do anything else?
hi, This is my first app and I'm honestly pretty nervous about the whole review process 😅 sorry if this is a dumb question. My app got rejected for 2.1 (App Completeness), and I already replied twice in the messages under App Review, explaining our business model and giving a test account. Since then... nothing. No response. Just wondering — once I've replied there, is that enough, or do I need to do something else (like resubmit the build) to get things moving again? Kind of worried I'm missing a step somewhere. Also every single submission so far has taken way longer than the 24-48hrs Apple says. Is that normal lately, or should I be worried something's stuck on my end? Would really appreciate any advice from people who've been through this before. Thanks!
1
0
181
Aug ’26
Cannot attach first In-App Purchase to app version after Guideline 2.1(b) rejection: "In-App Purchases and Subscriptions" section missing
Hi everyone, Not sure if this is a known App Store Connect bug but hoping either someone here has a workaround, or an Apple engineer can help push this along. Background: this is my first In-App Purchase submission for my app. My original binary was submitted without the IAP attached (my mistake, first time doing this), so the app was rejected under Guideline 2.1(b) for referencing a paid feature whose IAP wasn't submitted for review. Since then: The IAP (non-consumable, one-time purchase) is fully configured with a review screenshot and notes, and shows status "Ready for Review" after submitting via "Add for Review" My app version is in a rejected state with an "Update Review" button available The problem: I can't get these two linked together anywhere in the UI. Clicking "Update Review" on the version page resubmits it, but never shows any option to attach the IAP Clicking "Add for Review" from the IAP page opens a Draft Submission, but that draft says "Unable to Submit for Review: To submit your items for review, add an app version for the selected platform," with no version selector anywhere in that panel Tried hard refresh, incognito, different browsers, starting a fresh draft submission. Same result every time. Result: resubmitted the app, got the exact same 2.1(b) rejection again, confirming the IAP genuinely never made it into the review package despite showing as correctly configured on my end. I've seen a few other threads describing what sounds like the exact same issue, where the "In-App Purchases and Subscriptions" section disappears from the version page after a first rejection, and the fix ended up requiring an Apple support agent to manually push the IAP status forward on the backend, without needing another binary. Has anyone found a way to trigger this from the developer side, or is direct support/engineering intervention really the only path? Already have a case open with Apple Developer Support as well, happy to share the Case ID via DM if that helps someone from Apple locate it faster. Thanks in advance for any pointers.
4
0
440
Aug ’26
Submission pending 7 days after reviewer-error rejection — case 20000136325596
Our app (Apple ID 6781970154), submission a241932d, v1.0.13 (73), has been Waiting for Review since Aug 13. Timeline: rejected Aug 6 under 2.1(a) — "unable to receive verification code by email" — although our on-file review notes documented that the demo account uses a fixed verification code and requires no inbox. We replied in-thread within minutes; no response in 7 days. Resubmitted Aug 13; no response in 7 days. Support case 20000136325596 opened Aug 13; acknowledged, then silence. An expedite request was also filed. We had a Meet with App Review consultation on Aug 6 and resolved every prior issue raised. We'd be grateful for a status update in App Store Connect.
0
0
76
Aug ’26
Custom-built VPN app repeatedly rejected under 4.3(a), now 5.6
Hi, I’m looking for technical advice on a repeated App Review issue with our app, ASK VPN (Apple ID: 67...). ASK VPN is a simple consumer VPN app for iOS. It uses Apple’s Network Extension / Packet Tunnel APIs. Users sign in, retrieve their assigned VPN profile, view account status/expiry, and connect through a single main connection flow. The app was built specifically for this project. We did not purchase or reuse a VPN template or source code from another developer. I designed the product flow and UI, and used Codex AI as a development assistant. Our rejection history is: Guideline 4.3(a): Apple said the app had a similar binary, metadata, and/or concept to apps submitted by other developers, including one associated with a terminated Developer Program account. We reviewed the app, changed product-specific functionality and UI, added onboarding, privacy/VPN disclosures, localization, support features, diagnostics, and clarified the implementation to App Review. The latest rejection is now Guideline 5.6, stating that the app contains features that appear to have been intentionally hidden during review. We do not intentionally hide any functionality from App Review, and we have not been told which specific feature or behavior is considered hidden. One thing that concerns me is that the app often moves to In Review and is rejected very quickly. My main questions are: What technical factors can cause a custom-built VPN app using Network Extension / Packet Tunnel to be associated with another developer’s app or terminated account? What kinds of implementation or server-side behavior commonly lead App Review to conclude that functionality is being intentionally hidden? We are willing to provide Apple with complete source code, backend/API details, test accounts, and configuration if there is a secure review path for that. I would appreciate advice from anyone who has seen a similar 4.3(a) → 5.6 progression. Thank you.
1
0
158
Aug ’26
Waiting For Review - Longer than usual?
I submitted my first public build (iOS 1.0) on July 30th for my game, Golfer's Pair-A-Dice (Apple ID: 6789222313) and it has been in "Waiting for Review" with no movement since then. I read that 24-48 hours is typical, but could take longer for first builds, but it seems like it hasn't even begun to be reviewed which is frustrating. Has anyone experienced similar wait times in the queue and had any success getting their app reviewed? I was hoping to launch on App Store and Google Play Store at same time and Google approved the app in 2 days so it has just been waiting for me to push, which I am waiting on Apple to approve so I can push both simultaneously.
6
0
595
Aug ’26
App Stuck in Waiting for Review for Nearly a Week — Multiple Support Requests Unanswered
Hello, My app Jewel Coloring Go! (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on July 31, 2026. However, today is Auguse 9, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.
12
4
1.3k
Aug ’26
App stuck in "Waiting for Review" for 15 days — Lift Access (6798906865)
My app has been in "Waiting for Review" since August 8, 2026 — 15 days with no status change and no communication. App: Lift Access Apple ID: 6798906865 Platform: iOS, version 1.0, Submitted: August 8, 2026 This is a new, original app, written from scratch. Another app on the same account (iHike, Apple ID 6787736523) was reviewed and published on July 24, 2026, so the account is active and in good standing. I have not cancelled or resubmitted the build, and I am not asking for priority over anyone else. I would simply like to know whether something is blocking this submission, or whether it has not yet been picked up. If there is an issue on my side that I need to resolve, I am happy to address it — I just have no information to act on. Has anyone seen a submission sit this long recently, and did anything move it?
Replies
0
Boosts
0
Views
141
Activity
Aug ’26
First iOS submission stuck in “Waiting for Review” for 6+ days
Hello, My app, Pulse Blocks: Block Puzzle, iOS version 1.0, was submitted on August 14, 2026 at 12:52 PM and has remained in Waiting for Review for more than 6 days. It has never moved to “In Review”. I have not received any rejection, request for additional information, or indication that action is required from my side in App Store Connect. I have also contacted Apple Developer Support, but I have not received a response yet. Could someone from App Review please confirm whether this delay is expected or whether the submission may be stuck in the review queue? I’m happy to provide any additional information privately if required. Thank you.
Replies
1
Boosts
0
Views
604
Activity
Aug ’26
Expedited Review Request is taking a long time — any advice?
Has anyone experienced Apple App Review being really slow lately? I already submitted an Expedited Review Request through Apple Developer Support, but it still seems to be moving really slowly. My app is still stuck on “Waiting for Review.” How long does it usually take after submitting an expedited review request? If the request has already been submitted through Developer Support, is there anything else I can do to get Apple to take a look at it sooner? Or is App Review just slower than usual right now and I basically just have to wait? 😭 Would really appreciate it if anyone who recently got an expedited review could share how long it took for them! My App ID is 6800172081
Replies
0
Boosts
0
Views
72
Activity
Aug ’26
ITMS-91064 persists across 8+ builds despite verified-correct PrivacyInfo.xcprivacy
I'm getting the following error on every submission (Build 1 through 8), even after multiple clean rebuilds and manual verification of the raw manifest content: ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: "PrivacyInfo.xcprivacy" and also "PlugIns/[WidgetName].appex/PrivacyInfo.xcprivacy" NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn't empty. What I've verified locally (via plutil -p and raw cat on both the .xcarchive and the exported .ipa): Main app PrivacyInfo.xcprivacy: NSPrivacyTracking=false, NSPrivacyTrackingDomains=[] (empty) Widget PrivacyInfo.xcprivacy: same, false + empty No duplicate keys found in either file Generated an official "Privacy Report" from Xcode Organizer - no obvious conflict at the app or widget level was shown Updated GoogleMobileAds/UserMessagingPlatform SDKs to the latest version - issue persists Bundle version increments correctly with each build (confirmed via Info.plist inside the actual uploaded archive) Is there a known caching issue on the App Store Connect validation side, or something else I might be missing? Happy to share the Privacy Report PDF and archive details if helpful.
Replies
3
Boosts
0
Views
395
Activity
Aug ’26
Waiting for Review for 6 days
Hi, I submitted my app update (app has been approved) 6 days ago and the status has not changed from "Waiting for Review". Since then, I have updated another app, submitted it for review, it was reviewed and approved within 24 hours. I want to make sure there isn't an issue with my app submission that has been stuck in Waiting for Review for 6 days. Please help!
Replies
0
Boosts
1
Views
211
Activity
Aug ’26
Vagus Fit stuck in “Waiting for Review” for 9 days — no response from Developer Support
Hello, My iOS app, Vagus Fit, has been stuck in “Waiting for Review” since August 12, 2026 at approximately 3:46 PM. It has now been about 9 days and the submission has still never entered “In Review.” App: Vagus Fit Version: 1.3.0 Platform: iOS Submitted: August 12, 2026 at approximately 3:46 PM Current status: Waiting for Review Developer Support Case ID: 20000142078727 I already contacted Apple Developer Support through the App Review Status contact form several days ago, but I have not received a response or any update. I have also checked App Store Connect and I do not see any messages, missing information, rejection, or action required from my side. I understand that review times can vary, but this delay is significantly longer than the normal review timeframe. Could someone from Apple please check whether my submission and existing Developer Support case are progressing normally, or escalate the case if necessary? Thank you.
Replies
0
Boosts
0
Views
338
Activity
Aug ’26
Waiting for review for 11 days
Hi! I submitted my app for review 11 days ago and have been waiting eagerly for my review. Ive noticed some posts about people having long wait times, but cant seem to find out if they were eventually reviewed or if they resubmitted or something else. I have my app live on other platforms currently and my next big patch is approaching release (1.2.0) whilst i am still waiting for 1.1.0 to be reviewed here on the App Store. Is there a chance the app is stuck somehow? Should i maybe just resubmit with the newer version instead? Or would that cost me my spot in line and just lead to further wait times? I appreciate any help i can get! Thanks Carl
Replies
0
Boosts
0
Views
78
Activity
Aug ’26
App submission in "Waiting for review" since 9th August (12 days)
Hello, I submitted our app to the App Store on 9th august and it has been stuck in "Waiting for review". We have a very critical launch date timeline. We have to release our app in the first week of September (before 5th); therefore, we submitted it quite early. But seems like the app is stuck indefinitely in the "Waiting for review" state. We even raised a support ticket for this. No response on that too. App ID: 6799395555 Support conversation ID: 20000139951347 What can be done to expedite this as further delays will cause us to miss our timeline?
Replies
0
Boosts
0
Views
208
Activity
Aug ’26
App stuck in waiting for review
My app is stuck in waiting for review for the past 12 days (submitted on 9th August 2026). I am running out of timeline and would appreciate any feedback on the reason for the extended hold, do I have to do anything on my end, when do I expect the app to be reviewed. Would appreciate assistance on this. My App Apple ID: 6799715408 Any assistant will be appreciated as the project timeline is fast approaching.
Replies
3
Boosts
1
Views
390
Activity
Aug ’26
Guideline 2.3 rejection citing UIRequiredDeviceCapabilities when the only value is arm64
My app was rejected under Guideline 2.3 (Accurate Metadata) with the standard text saying the UIRequiredDeviceCapabilities key is set up so that the app will not install on the review device. The review device was an iPad Air 11-inch (M3) on iPadOS 26.6. I inspected the Info.plist inside the exact archive that was uploaded. Everything relevant: UIRequiredDeviceCapabilities = (arm64) UIDeviceFamily = (1, 2) MinimumOSVersion = 18.0 Binary architectures = arm64 Built with Xcode 26.6, iOS 26.5 SDK An iPad Air 11-inch (M3) is arm64, is device family 2, and runs an OS far above 18.0, so as far as I can tell nothing in that plist can prevent installation. arm64 is the value Xcode injects automatically, and I have never declared the key myself. What I have already checked: There is no UIRequiredDeviceCapabilities in my source Info.plist and no INFOPLIST_KEY build setting for it. The value is injected at build time. I added the key to my own Info.plist as an empty array to try to override the injection. Xcode still writes (arm64) into the built plist, so I cannot remove it. I built the same Release configuration and installed it on an iPad Air 11-inch (M3) simulator running iPadOS 26.2, the highest iPadOS available to me. It installs and launches with no error. There are no app extensions. One target, TARGETED_DEVICE_FAMILY = "1,2". My questions: Is arm64 in UIRequiredDeviceCapabilities known to trigger this rejection on iPadOS 26 review devices, or is something else being reported under this template? Is there any supported way to suppress the value Xcode injects, or will the array always contain arm64 for an arm64-only binary? If the installation failure was real but caused by something other than this key, what else produces an install failure that App Review would attribute to UIRequiredDeviceCapabilities? Context for why I am asking here and not only in App Store Connect: the build sat in Waiting for Review for about a week and a half, I used my expedited request, it was rejected on this, I replied in Resolution Center with the plist contents and received no answer, and the resubmission is back in Waiting for Review. I am not asking anyone here to change a review outcome. I am trying to find out whether this is a known issue with the key so I can stop guessing. Any pointer would be appreciated.
Replies
2
Boosts
0
Views
350
Activity
Aug ’26
Waiting for Review 8 days — no response from Contact Us or phone support
Our first submission has been in Waiting for Review since August 12 — 8 days as of today. I've tried both support channels without result: Submitted a Contact Us request through App Store Connect — no reply Called Developer Support and waited on hold about an hour — no resolution The app is a straightforward iOS-only build (iPhone, no iPad). It's a first submission, not an update. Nothing in App Store Connect indicates a problem — no rejection, no metadata rejected state, no message in Resolution Center. It simply hasn't moved out of Waiting for Review. I've seen several recent threads describing the same thing, which is why I'm posting here rather than opening another ticket. Is there anything on my side that commonly causes a first submission to sit in Waiting for Review this long, or is the only option to keep waiting? Any guidance on the right escalation path would be appreciated. Thanks.
Replies
1
Boosts
0
Views
212
Activity
Aug ’26
App Under Expedited Review For 6 Weeks — Previous Build Approved, Resubmitted for Bug Fixes, Launch Date 6 Weeks Ago
Hello App Review team, I am requesting urgent assistance with my app review. Our previous build was approved around 5 weeks after our expected launch date, and last week we had to resubmit with a couple bugs that were fixed during the last review process. It has been 6 days since that submission, with an expedited review, and we are now 6 weeks past our launch date which has resulted in financial losses and dozens of media outlets notified weekly of delays. We would really appreciate if our latest build can be approved, as there are only minor bug fixes since the last one. Apple ID: 6748958042 Original Submission Date: 06/30/2026 Latest Submission Date: 08/14/2026 Current Status: Waiting for Review Support Case #: 20000141845140 Given the previous approval and minor changes since that build, we would greatly appreciate any escalation or update on the status of this review as we are incurring daily losses due to the review delay. Thank you!
Replies
0
Boosts
0
Views
340
Activity
Aug ’26
App stuck in "Waiting for Review" for 8 days
Hello, My app submission has been waiting for review for 8 days, and there has been no status update or request for additional information. Submission ID: f9cc5319-693b-4809-8bcb-5eb0e8ad28bd I understand that review times can vary, but this is considerably longer than I have experienced before. Could an Apple representative please check whether the submission is progressing normally or if any action is required from my side? Thank you.
Replies
3
Boosts
0
Views
441
Activity
Aug ’26
First app, still waiting on review reply — do I need to do anything else?
hi, This is my first app and I'm honestly pretty nervous about the whole review process 😅 sorry if this is a dumb question. My app got rejected for 2.1 (App Completeness), and I already replied twice in the messages under App Review, explaining our business model and giving a test account. Since then... nothing. No response. Just wondering — once I've replied there, is that enough, or do I need to do something else (like resubmit the build) to get things moving again? Kind of worried I'm missing a step somewhere. Also every single submission so far has taken way longer than the 24-48hrs Apple says. Is that normal lately, or should I be worried something's stuck on my end? Would really appreciate any advice from people who've been through this before. Thanks!
Replies
1
Boosts
0
Views
181
Activity
Aug ’26
Cannot attach first In-App Purchase to app version after Guideline 2.1(b) rejection: "In-App Purchases and Subscriptions" section missing
Hi everyone, Not sure if this is a known App Store Connect bug but hoping either someone here has a workaround, or an Apple engineer can help push this along. Background: this is my first In-App Purchase submission for my app. My original binary was submitted without the IAP attached (my mistake, first time doing this), so the app was rejected under Guideline 2.1(b) for referencing a paid feature whose IAP wasn't submitted for review. Since then: The IAP (non-consumable, one-time purchase) is fully configured with a review screenshot and notes, and shows status "Ready for Review" after submitting via "Add for Review" My app version is in a rejected state with an "Update Review" button available The problem: I can't get these two linked together anywhere in the UI. Clicking "Update Review" on the version page resubmits it, but never shows any option to attach the IAP Clicking "Add for Review" from the IAP page opens a Draft Submission, but that draft says "Unable to Submit for Review: To submit your items for review, add an app version for the selected platform," with no version selector anywhere in that panel Tried hard refresh, incognito, different browsers, starting a fresh draft submission. Same result every time. Result: resubmitted the app, got the exact same 2.1(b) rejection again, confirming the IAP genuinely never made it into the review package despite showing as correctly configured on my end. I've seen a few other threads describing what sounds like the exact same issue, where the "In-App Purchases and Subscriptions" section disappears from the version page after a first rejection, and the fix ended up requiring an Apple support agent to manually push the IAP status forward on the backend, without needing another binary. Has anyone found a way to trigger this from the developer side, or is direct support/engineering intervention really the only path? Already have a case open with Apple Developer Support as well, happy to share the Case ID via DM if that helps someone from Apple locate it faster. Thanks in advance for any pointers.
Replies
4
Boosts
0
Views
440
Activity
Aug ’26
Submission pending 7 days after reviewer-error rejection — case 20000136325596
Our app (Apple ID 6781970154), submission a241932d, v1.0.13 (73), has been Waiting for Review since Aug 13. Timeline: rejected Aug 6 under 2.1(a) — "unable to receive verification code by email" — although our on-file review notes documented that the demo account uses a fixed verification code and requires no inbox. We replied in-thread within minutes; no response in 7 days. Resubmitted Aug 13; no response in 7 days. Support case 20000136325596 opened Aug 13; acknowledged, then silence. An expedite request was also filed. We had a Meet with App Review consultation on Aug 6 and resolved every prior issue raised. We'd be grateful for a status update in App Store Connect.
Replies
0
Boosts
0
Views
76
Activity
Aug ’26
Custom-built VPN app repeatedly rejected under 4.3(a), now 5.6
Hi, I’m looking for technical advice on a repeated App Review issue with our app, ASK VPN (Apple ID: 67...). ASK VPN is a simple consumer VPN app for iOS. It uses Apple’s Network Extension / Packet Tunnel APIs. Users sign in, retrieve their assigned VPN profile, view account status/expiry, and connect through a single main connection flow. The app was built specifically for this project. We did not purchase or reuse a VPN template or source code from another developer. I designed the product flow and UI, and used Codex AI as a development assistant. Our rejection history is: Guideline 4.3(a): Apple said the app had a similar binary, metadata, and/or concept to apps submitted by other developers, including one associated with a terminated Developer Program account. We reviewed the app, changed product-specific functionality and UI, added onboarding, privacy/VPN disclosures, localization, support features, diagnostics, and clarified the implementation to App Review. The latest rejection is now Guideline 5.6, stating that the app contains features that appear to have been intentionally hidden during review. We do not intentionally hide any functionality from App Review, and we have not been told which specific feature or behavior is considered hidden. One thing that concerns me is that the app often moves to In Review and is rejected very quickly. My main questions are: What technical factors can cause a custom-built VPN app using Network Extension / Packet Tunnel to be associated with another developer’s app or terminated account? What kinds of implementation or server-side behavior commonly lead App Review to conclude that functionality is being intentionally hidden? We are willing to provide Apple with complete source code, backend/API details, test accounts, and configuration if there is a secure review path for that. I would appreciate advice from anyone who has seen a similar 4.3(a) → 5.6 progression. Thank you.
Replies
1
Boosts
0
Views
158
Activity
Aug ’26
Waiting For Review - Longer than usual?
I submitted my first public build (iOS 1.0) on July 30th for my game, Golfer's Pair-A-Dice (Apple ID: 6789222313) and it has been in "Waiting for Review" with no movement since then. I read that 24-48 hours is typical, but could take longer for first builds, but it seems like it hasn't even begun to be reviewed which is frustrating. Has anyone experienced similar wait times in the queue and had any success getting their app reviewed? I was hoping to launch on App Store and Google Play Store at same time and Google approved the app in 2 days so it has just been waiting for me to push, which I am waiting on Apple to approve so I can push both simultaneously.
Replies
6
Boosts
0
Views
595
Activity
Aug ’26
App Stuck in Waiting for Review for Nearly a Week — Multiple Support Requests Unanswered
Hello, My app Jewel Coloring Go! (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on July 31, 2026. However, today is Auguse 9, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.
Replies
12
Boosts
4
Views
1.3k
Activity
Aug ’26
"Waiting for Review"
Hi, re-iterating the previous post regarding the approval wait. It's now been past 48 hours since my new request for the new build, and the app still has not been approved. Would really appreciate the prompt review to avoid any further delays. Thanks in advance!
Replies
0
Boosts
1
Views
211
Activity
Aug ’26