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.

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!

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.

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!

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.

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.

App Review Appeal Pending for More Than 10 Days — Is This Normal? Hi everyone, I’m looking for advice regarding an App Review appeal that has now been pending for more than 10 days without a decision or meaningful status update. Before submitting the appeal, our app had already been waiting for App Review for approximately 5 days. It was then reviewed and rejected, after which we submitted an appeal to the App Review Board. We understand that appeals may require additional investigation, but it has now been over 10 days since the appeal was submitted, and we still have no estimated timeline for a decision. This is significantly delaying our app release and making it difficult for us to plan updates and operations. Has anyone recently experienced a similar wait time with the App Review Board? Also, is there an official way to follow up or escalate an appeal when it has been pending for this long? We have already followed the normal appeal process and are simply trying to understand whether this timeframe is expected. Any recent experience or advice would be greatly appreciated. Thank you.

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.

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.

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.

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!

This is my first app and my first App Store submission, after a substantial amount of work preparing Rendr Markdown for release and making sure that everything was ready for Apple’s review process. I submitted Rendr Markdown 3.3.10 for macOS on August 13, 2026 at approximately 04:00 CEST. More than six days later, it is still in Waiting for Review. As a new Apple developer, I have to admit that I am surprised by this experience, particularly by the lack of any indication of what is causing the delay or when the submission might be reviewed. I previously spoke with Apple Developer Support regarding another App Store Connect matter. During that call, the representative also checked the app submission and confirmed that it appeared to be correctly submitted and in the review queue. As the delay continued, I contacted App Review through the App Review Status support form. I have not received a response or any indication that the case is being investigated. There have been no status changes, review messages, rejections, or requests for additional information. I therefore do not know whether this is simply an unusually long review queue or whether the submission requires intervention from Apple. Could someone from App Review please check whether this submission is progressing normally, or escalate the existing support case if necessary? App: Rendr Markdown Platform: macOS Version: 3.3.10 Apple ID: 6799048174 Submission ID: 020fe5c8-7db6-4432-969f-bb0a49d1efdc Support case: 20000140663217 Thank you.

Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice on May 29, 2026, for my account (Developer: Bushra Malik) related to Section 3.2(f), regarding app submissions for Dress Up Fashion: Styling Game. I submitted a formal appeal 10 days ago but have not yet received a response or case number confirmation. I want to provide brief context: Our original Clothing Store Simulator received repeated rejections. Rather than continuing to resubmit the same app, we made the decision to build a completely new game from scratch — new code, new assets, new UI, and a fully revised App Store listing. Nothing from the original submission was carried forward. This was a deliberate good faith effort to achieve compliance, not an attempt to evade review. We also believe an older binary may have been reviewed rather than our latest build — a technical issue we have experienced previously on this account. Our account has 4+ years of publishing history and 25+ live games currently on the App Store. Not a single other app is in rejection or under any violation. We have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation that my appeal is actively under review A status update or case reference number Any additional information Apple needs from our side We are fully cooperative and have all source code, assets, and submission history available immediately upon request. Thank you sincerely for your time. Bushra Malik Apple Developer Account: Bushra Malik

Repeated Guideline 4.1(a) rejection for my game Hello, I’m looking for some advice regarding a repeated App Review rejection. My game is Pet Shop Owner Simulator. It was originally developed and published by me under Tri Creations on Google Play. I’m now submitting it to the App Store, but it has been rejected multiple times under Guideline 4.1(a) – Design – Copycats. The latest rejection states: “The app’s description, name, and icons includes references to Pet Shop Owner Simulator 3D.” The confusing part is that Pet Shop Owner Simulator 3D is the name of my own Android game. I have already explained this to App Review and provided documentation showing my ownership, but I continue to receive the same rejection. Could someone please advise how I can clarify this with App Review? In particular, I would like to understand whether Apple is referring to a specific third-party app or developer, or if there is something specific in my App Store metadata that I should change. Thank you.

Hi everyone, I’m looking for advice from developers who may have experienced a similar App Review situation. Our app, ASK VPN (Apple ID: 679*****), has been rejected multiple times, and I’m struggling to understand exactly what Apple is detecting. Initially, the app was rejected under Guideline 4.3(a) - Design - Spam. Apple first stated that the app shared a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. After we asked for clarification, Apple later stated that the app shared a similar binary, metadata, and/or concept with apps submitted by other developers, with only minor differences. To clarify an important point: we did not purchase this VPN source code from another developer, and we did not use a commercial VPN template, cloned project, or repackaged source code. ASK VPN was developed specifically for this project. I defined the product strategy, required functionality, user flow, and design direction myself, and used Codex AI as a development assistant to help implement the application. The codebase was created for ASK VPN rather than acquired from another developer or reused from an existing App Store application. Because of that, the earlier Guideline 4.3(a) rejection mentioning similarity to apps associated with other developers, including a terminated developer account, is particularly confusing to us. After the earlier rejection, we carefully reviewed and updated the application and added or improved product-specific functionality, including: Native iOS VPN implementation using Network Extension / Packet Tunnel ASK VPN account and profile integration Account status and expiry information First-use onboarding Terms and Conditions acceptance Privacy and VPN disclosure screens English and Myanmar localization In-app support and guided help Support diagnostic / Profile ID functionality Secure handling and redaction of sensitive VPN configuration data Updated app-specific UI and functionality We explained these changes to App Review and repeatedly asked which specific part was considered similar — source code, VPN implementation, framework, metadata, screenshots, assets, certificates, signing history, bundle identifier, backend behavior, or app functionality — but we did not receive a specific technical explanation. Now, on our latest submission, the rejection has changed to: Guideline 5.6 - Developer Code of Conduct Apple states: “The app contains features that appear to have been intentionally hidden during the review process.” This is especially confusing and concerning because we are not intentionally hiding any features from App Review. Another thing I have noticed is that the app enters “In Review” and then gets rejected very quickly, sometimes almost immediately. This has happened repeatedly. Because the rejection happens so quickly, I am wondering whether an automated or internal detection system may be flagging something related to the binary, code structure, Network Extension, account association, signing history, backend behavior, configuration, or another technical characteristic. At this point, we are willing to provide Apple with the complete source code of the application for technical review. We are also willing to provide: Complete iOS source code Network Extension / Packet Tunnel implementation Backend and API implementation Server-side configuration relevant to app behavior Feature flags and remote configuration Environment-specific configuration Authentication and account logic Source-control history Design and implementation records Complete feature documentation Test accounts and credentials Any other technical information Apple may require We would also be willing to provide access to a private source-code repository if Apple has an approved secure method for doing so. We are not looking for a way around App Review. We genuinely want to understand the exact issue, correct it properly, and fully comply with the App Store Review Guidelines. I would really appreciate advice from anyone who has experienced something similar. In particular: What can cause Apple to associate a newly developed app with apps from a terminated Developer Program account? Can common Network Extension / Packet Tunnel implementation patterns trigger similarity detection? Can AI-assisted code, standard iOS architecture, common libraries, or generated implementation patterns contribute to binary or source-code similarity? What can cause Apple to believe functionality is intentionally hidden during review? Could API responses, server-side behavior, feature flags, account states, device region, IP address, or review-environment differences cause this? Could signing history, certificates, bundle history, provisioning, or backend infrastructure create an association with another developer? Is there a way to request a deeper technical investigation or provide Apple with the complete source code? What is the best escalation path when repeated App Review replies do not identify the specific feature, code path, or behavior causing the rejection? Has anyone experienced a similar progression from Guideline 4.3(a) → Guideline 5.6? I’m honestly very discouraged after going through repeated rejections without being able to identify the root cause, but I want to resolve this correctly rather than keep making speculative changes and resubmitting. Any technical guidance or experience from developers who have dealt with a similar case would be greatly appreciated. Thank you.

Hi everyone, Running into not really sure if it's 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.

Hello, Our app has been in "Waiting for Review" since August 11, 2026, with no status change and no messages in App Store Connect. App Name: Voxen AI Apple ID: 6790147633 Version: 1.0.0 (139) Submission ID: bd9db3ca-72f9-46ad-ace5-6fdfc873e59f Date Submitted: Aug 11, 2026 at 9:55 AM Could someone from App Review check whether this submission is stuck in the queue, or let us know if any action is needed on our side? Thank you.

Hi, just want to make sure that my app is approved within the 48-hour period. It's nearing the tail end of it, and I would like to confirm that the app is good to go after a few iterations with App Review team and avoid further delays like before. Thanks!

It’s not only a normal review it’s an expedited review . We’re literally desperate to get this app approved yet it’s literally been a week to review the app . What do you do ? It says 90% of apps get reviewed in a day so how can we be waiting a week ? this is so horrible

After waiting on the phone for 3 hours, a rep answered and claimed headset issues and then just hung up and hasn’t bothered to call back. Not sure what sort of service I can expect here bust can anyone tell me why App Reviews take so long? They claim they are completed in 24-48 hours. It’s been nearly a week and nothing… Any help here will be greatly appreciated.