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

Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
0
0
8.2k
Mar ’25
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
1
0
31
53m
All 4 of My Original Native Games Rejected Under Guideline 4.3 & 4.2.6 – No Reply to Appeal/Expedite Request
Hello everyone, After waiting over a week in review, all of my recently submitted apps were rejected under Guideline 4.3 (Spam) and Guideline 4.2.6 (App Generation Services). The rejection messages are generic and do not specify which components, assets, or metadata triggered the flags. To clarify, these are original native apps built from scratch in Xcode/Swift—not commercialized templates, web wrappers, or third-party app generation builds—and each has distinct mechanics, custom assets, and functionality. I have already replied in the Resolution Center, submitted an official appeal/support inquiry, and requested an expedited review, but it has been 3 days with no response. Has anyone experienced false-positive 4.3/4.2.6 flags across multiple distinct apps on the same developer account, or can an Apple representative advise on what specific areas I should audit to get these resolved? Thank you in advance for your guidance.
1
0
126
53m
New App Rejected Under Guideline 4.3(a) on Both iOS and tvOS — Seeking Clarification
Hi everyone, I’d like to share my experience with the first release of my app and ask for some guidance. Submission details App ID: 6829444660 Platforms: iOS and tvOS (Apple TV) Initially submitted: November 1, 2026, at 7:17 PM Rejection received: November 13, 2026, at 9:30 PM Rejection reason: Guideline 4.3(a) — Design — Spam Both the iOS and Apple TV submissions received the same rejection at the same time. How the app was built I personally developed the app using UIKit, with some parts built in SwiftUI. I also created the visual assets myself using Canva. AI was not involved in writing or designing the app; its involvement was limited to testing-related assistance. Having personally worked on the implementation and visual design, it was discouraging to see the app classified as spam. I believe there may be a misunderstanding about my submission, and I would appreciate an opportunity to clarify it. What I’m asking for Could an Apple representative help identify the specific elements or duplication concerns that led to this rejection? Clear, actionable feedback would help me understand: Which aspects of the app raised concerns under Guideline 4.3(a). What changes, if any, are needed to address those concerns. What supporting information I can provide to help clarify the situation. This project means a lot to me. I respect the review process and want to meet Apple’s requirements. I would sincerely appreciate a reconsideration of my submission and clear guidance on how to move forward. Has anyone experienced a simultaneous 4.3(a) rejection on iOS and tvOS and successfully resolved it? Thank you for taking the time to read this. Any guidance would mean a great deal to me.
2
0
166
54m
Account flagged under 4.3: five unrelated apps rejected the same minute, replies unanswered for 9 days, rebuilt app rejected again as "similar"
Hi, I am a solo developer with an individual account since 2024. I would appreciate guidance from App Review, because I do not know what else I can do from my side. On October 13 at 00:06 all five apps I had in review were rejected within the same minute under 4.3 and 4.2.6, each with the same nine questions about the app, its audience, beta testing, shared code and templates. The apps are not related: a voice recorder with on-device transcription, a dice roguelike, a tile based dungeon game, a studio simulation game and a Safari extension for cookie banners. I built them myself in Xcode over several weeks and submitted each one when it was finished, which is why they arrived in the same week. No template, no generation service, no client, no third party SDKs, no other accounts. The same day I answered all nine questions in full for four of the apps and withdrew the fifth, the cookie banner extension, to rebuild it. Nine days later there is no response on any of the four threads. On October 21 I submitted the rebuilt extension as version 2.0. It now has consent receipts decoded from each site's TCF record, a public page listing the 100 sites tested before every release with the result for each, a separate mode for subscribe-or-consent walls, Global Privacy Control, Shortcuts and a Mac app. A review video and a public test page were attached. It was rejected within a day under 4.3(a) as sharing "a similar binary, metadata and/or concept" with apps submitted by me or others, with an Extended Review note. The only earlier app with this name is my own withdrawn 1.0. I have stopped submitting anything. My questions: Is there anything more I can provide for the four open threads so a reviewer can look at the apps themselves? I can send screen recordings, source code or demo builds the same day. For the 4.3(a) rejection: what was the app matched against, and what counts as a sufficient difference in this category, given that several cookie banner blockers for Safari were approved in 2026? App IDs: 6821429432 (Voice Notes: Local Transcribe), 6821423492 (Lampfall), 6821275353 (Bone Caster), 6819040142 (Vibe Coder), 6818993189 (Cookie Hide, version 2.0). Thank you for your time. Armen Ter-Oganezov
3
0
167
57m
Review submission stuck in "Canceling" for 12 days: version locked, can't cancel or resubmit
Our iOS review submission has been stuck in CANCELING since 10 Nov 2026. Every action on it is refused, so we haven't been able to ship an update for 12 days. App ID: 6809173786 Stuck submission: 0c25955e-e5d8-4835-8605-79f8115c9992 Developer Support cases: 103018649498, 103018648320 App Review case: 30000012887740 The submission has 4 items, all still "Ready for Review": iOS App 1.0.14 (app version) Lifetime-Flybud (our first non-consumable IAP) retention-3840x2160.png (Asset Library image) Flybud_Orbit_Header_3840x164… (Asset Library video) What the App Store Connect API returns (22 Nov): Cancel the submission: "Resource state is invalid – Resource cannot be canceled at the moment, please try again later." Remove an item: "Resource state is invalid – Item was already submitted." Add 1.0.14 to a new submission: "Asset Library validation error – Asset is locked by a standalone review submission." Submit the IAP on its own: "The first Non-Consumable In-App Purchase for this app must be submitted for review at the same time that you submit an app version." The version is locked by the stuck submission, and the IAP can only ship with a version, so everything is blocked. New builds upload and process normally. Given error 3, I suspect the Asset Library items are what's preventing the cancellation from completing. Since 10 Nov I've written to App Review four times, opened two Developer Support cases, filed a bug report and emailed the App Store team. Phone support has been unavailable, and App Review can't see the submission in their queue. Could someone at Apple escalate this to App Store Connect engineering to clear or complete the cancellation? Thank you.
0
0
7
1h
Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe
I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.
5
0
208
2h
Asked to resubmit after being offered bug fix approval, now 7 days in "Waiting for Review" with no response
Hello, We'd appreciate help from the App Review team with our app update. App: AI Video Generator - Bunsy (Apple ID 6762499422) Version: 1.0.13 (build 350) Submission ID: 644c0463-bcb1-44c5-a0bb-b91ccf1860c2 Timeline: Nov 4: submitted version 1.0.13. Nov 12: App Review identified a Guideline 4 issue (Sign in with Apple logo artwork) under Bug Fix Submissions. The message said the issue could be resolved in our next update, and that if we replied, the submission could be approved without resubmitting. Nov 12: we replied the same day and asked to approve the submission as a bug fix, committing to address the issue in the next update. Nov 13: App Review asked us to resubmit anyway. Nov 14: we resubmitted with build 350, which already includes the fix (native Sign in with Apple button). It has been in "Waiting for Review" since then. Nov 16: we requested an expedited review. Nov 19: we contacted App Review about the status (Case ID 103018616391) and have received only the automated confirmation. We followed every instruction we received, and this version has now been waiting for 17 days in total. It fixes a crash on first launch that affects users of the current version. Could you please check whether anything is holding this submission or whether anything else is needed from us? Thank you.
1
0
155
15h
First app stuck in "Waiting for Review" since Nov 13, after Guideline 2.1 info response
Hello App Review team, My first app, Rental Records, has been in "Waiting for Review" since November 13, 2026, and I'd appreciate it if someone could check whether it needs any action from me. App: Rental Records (iOS 1.0) Apple ID: 6832051224 Platform: iOS, Organization account Timeline: Nov 7: First submission Nov 8: Rejected under Guideline 2.1 (Information Needed) Nov 13: I added everything requested to the App Review Notes (app description, demo logins for both account types, list of external services, regional statement, and a screen recording) and resubmitted. Status has been "Waiting for Review" ever since. What I have already done: Submitted an Expedited App Review request days ago Called Developer Support twice and was told there is no fixed timeline Sent an App Review status inquiry (Case ID: [30000019474998]) The demo accounts work and the notes are complete. I'm happy to provide anything else you need. Thank you for your time.
1
0
144
15h
Concern Regarding App Review Timeline After Months of Organization Enrollment Delays – Fixit Employee Portal
Hello Apple Developer Community, I am reaching out to seek guidance and express our concern regarding our iOS application, Fixit Employee Portal, which is currently showing "Waiting for Review" in App Store Connect. Application Details: • App Name: Fixit Employee Portal • App Apple ID: 6834282511 • Version: 1.0.4 (Build 2) • Submission Date: November 13, 2026 • Current Status: Waiting for Review Before reaching this stage, our company had already spent several months completing the verification and approval process for our Apple Developer Program organization enrollment. We appreciate Apple's commitment to security, compliance, and quality throughout the enrollment and application review processes. However, after experiencing such an extended enrollment process, we are concerned about the possibility of further significant delays before our application becomes available to our employees. Our application is intended to provide essential employee services to our manpower workforce, including access to employment-related information and company resources. Many of our employees are awaiting its availability on iOS, and timely deployment is important to our daily operations. While we understand that our application was only recently submitted for review, we would sincerely appreciate clarification on the following: Is the current waiting period normal for a newly submitted application under a recently approved organization account? After several months of organization enrollment delays, should we anticipate another extended waiting period for the application review process? Is there a way to confirm that our application has no outstanding requirements that could delay its review? Given our employees' operational need for this application, would an expedited review request be appropriate? We are not requesting that Apple bypass its standard review requirements. We simply hope to understand the expected process and avoid further unnecessary delays after the lengthy organization enrollment experience. We sincerely appreciate the efforts of the Apple Developer and App Review teams and would be grateful for any guidance or assistance. Thank you for your understanding and support. Best regards, Fixit Development Team
2
0
131
15h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
1
0
145
15h
New app waiting for review since Nov 19: could App Review take a look?
Hello, I'm launching a new app, PlaPlu: Baby Development (Apple ID 6747391897). Its first version, 1.0.0 (build 202611191717), has been "Waiting for Review" since November 19 at 17:25 UTC. The status hasn't changed and App Review hasn't sent any message since then. Before that, the same version waited from November 16 to November 19. I took it out of the queue to swap in a build with a few fixes and resubmitted right away. So this first launch has now been waiting about five days in total. Everything for this version was submitted together: the build, the metadata and its in-app purchases. Could someone from App Review check whether the submission is stuck in the queue, or tell me if anything on my side is missing? I'll answer any questions right away. Thank you for your help.
0
0
94
17h
App Review Delayed for Over a Week – Anyone Experiencing the Same Issue?
Hi everyone, Is anyone else experiencing unusually long App Review delays recently? We have been waiting for our app to be reviewed since Thursday, November 12. Due to an issue with the previous submission, our developer resubmitted the app on Monday, November 16. Today is Friday, November 20, and our app is still waiting for review, with no visible progress. We have already submitted an Expedited Review Request, but we have not received any updates or confirmation that the review is progressing. This is becoming a serious concern because our game is scheduled to launch on November 25, and the continued delay is putting our launch schedule at risk. I would really appreciate hearing from other developers: Has anyone experienced similar App Review delays recently? How long did it take for your app to be reviewed? Is there any other effective way to contact Apple or escalate an urgent review issue, especially when an Expedited Review Request has already been submitted? Any advice or shared experiences would be greatly appreciated. Thank you!
10
4
527
1d
App Rejected Due to an Account Restriction, Not a Bug – No Response from Apple After Fixing the Issue
Hello everyone, I'm an independent developer, and I'm currently stuck in the App Review process. I'm hoping someone who has experienced something similar can offer some advice. My app was rejected because the reviewer encountered an error message when attempting to make an in-app purchase. However, this was not a technical bug or a StoreKit issue. It was an intentional account protection rule in my app. Here's what happened: My app has a rule that one Apple ID subscription can only be linked to one app account at a time. This prevents other accounts from taking over someone's paid subscription or sharing a single subscription across multiple accounts. During Apple's review, the sandbox Apple ID used by the reviewer had apparently already been linked to another test account. When the reviewer attempted to purchase a subscription using a different account, the app correctly triggered this restriction. Apple interpreted this behavior as a purchase failure and rejected the app. What I've done to resolve it: Although this rule is intentional and designed to protect users, I wanted to make the review process as easy as possible. I updated our server to remove this restriction specifically for sandbox subscriptions. Reviewers can now complete purchases and restore subscriptions even if their sandbox Apple ID was previously linked to another test account. The restriction remains unchanged for real production subscriptions. On November 17, I explained the situation to the App Review team and informed them that the sandbox issue had already been resolved. I asked them to test the purchase flow again. On November 18, I also requested a phone call to clarify the situation. The problem is that nobody has responded. I have not received any acknowledgment of my explanation, no response to my request for another review, and no phone call. I have also tried contacting Apple through the appeal process, but I still haven't received a response. At this point, I don't know what else I can do. The issue encountered during review has already been addressed, and no new app binary is required because the change was made entirely on our server. Has anyone experienced a similar situation where an app was rejected because an intentional business rule was mistaken for a bug? How did you get the App Review team to respond after explaining and resolving the issue? Is there any effective way to escalate this situation when both review messages and appeal requests go unanswered? submission ID 78b8dd94-fd4c-4951-959b-4fdb57a659d7 I would really appreciate any advice. Thank you!
0
0
106
1d
App stuck in "Waiting for Review" after resubmission + pending individual-to-organization conversion
Hi everyone, I'm hoping someone (or someone from Apple) can help or share their experience. My first iOS app was rejected under Guideline 2.3.6 for an Age Rating answer. I corrected the Age Rating as instructed, replied in App Store Connect, and resubmitted on 18 November. It has been in "Waiting for Review" since then. Everything on my side appears complete: Agreements, tax forms and banking are all Active App Compliance items are all Active App Privacy is published No new messages from App Review I have also requested to convert my developer account from Individual to Organization (I've received my D-U-N-S number), but haven't heard back from Membership support yet. A few questions: Can a pending Individual-to-Organization conversion hold up an app review? Is anyone else seeing longer than usual "Waiting for Review" times at the moment? How long did your account conversion take, and is there a faster way to reach Membership support? Any advice would be really appreciated. Thank you!
0
0
83
1d
App stuck in "Waiting for Review" since October 13 – anyone else?
Hi everyone, I submitted my iOS app (Hatırlatıcım) for review on October 13, and it's still showing "Waiting for Review" today, October 26. It's been almost two weeks now, and the status hasn't changed at all. I haven't received any emails or requests for additional information from Apple either. I contacted Developer Support on October 19, but haven't heard back from them yet. I've seen a few other developers mentioning similar delays recently, so I'm wondering if this is a general issue with App Store reviews right now. Has anyone who submitted an app around October 13–14 had theirs reviewed yet? I'm also not sure if I should just keep waiting or if there's anything else I can do at this point. Thanks!
5
1
207
1d
First app stuck in "Waiting for Review" since October 13
Hello, Our first app, "Pizza Virus - Food Delivery" (Apple ID 6612290745), has been in "Waiting for Review" since October 13, 2026. Submission ID: ebbda6e3-893f-42b5-8398-0d7ee377695a Version 2.1.0, build 2.1.2 (3) This is a resubmission that fixes the launch crash App Review reported on October 6 (Guideline 2.1(a)). We added a UIApplicationSceneManifest and a SceneDelegate. We later found that the updated Program License Agreement (issued October 14) and our Free Apps Agreement were only accepted on October 23, which may have held the submission. Both are now active, and the Digital Services Act declaration is completed. We requested an expedited review and opened support case 103008067614, but have not received a response. Could App Review please confirm whether the submission is now in the review queue, or whether anything else is needed from us? Thank you.
3
0
285
1d
First release waiting two weeks after resubmission
Hi, our app Flipped (Apple ID 6778089894) has had no update since we resubmitted build 20 on Nov 6. The Nov 4 review flagged Guidelines 2.1 and 1.2. We fixed both in build 20, replied in App Store Connect with the details, and attached a screen recording, but haven’t heard anything since. This is our first release and we’ve been in review since September, so any update would really help. Submission ID: 4d2b40e3-2413-4c02-9e66-8ee58282f147. Thanks.
4
1
81
1d
App Stuck in "Waiting for Review" for 7 Days After Guideline 2.1 Resubmission
Hello everyone, I am looking for advice regarding a delay on my first iOS app submission. It has been continuously in "Waiting for Review" for 7 days, well beyond the typical 24-48 hour window, with no status update. Submission Details: App Apple ID: 6834147398 Version (Build): 1.0 (17) Submission ID: bd2a5346-79a6-4c72-a268-ad797cb9de95 Date Resubmitted: November 13, 2026, 6:48 PM Context & Steps Already Completed: This is a resubmission following a Guideline 2.1 (Information Needed) request. I attached the requested iPhone screen recording demonstrating the app in use and updated the review notes. The app requires no sign-in or account credentials to test. All App Compliance declarations are completed. Agreements, Tax, and Banking show Active. Digital Services Act (DSA) trader compliance and verification documents have been submitted. I have already submitted an Expedited App Review request and an App Store Connect support inquiry, with no response yet. Could anyone, or an Apple team member, advise whether anything might be holding up a Guideline 2.1 resubmission like this, and what I can do to help get the review moving? Thank you in advance for your help. Thank you in advance for your help!
0
0
54
2d
App Stuck in "Waiting for Review" for 7 Days – No Response from Apple Support
Hello Apple Developer Community, I am looking for guidance regarding an unusually long delay in the App Review process. We submitted our app on 13 November 2026, and as of today (20 November 2026), the app has been continuously showing Waiting for Review for 7 days. We have already taken the following steps: Submitted an expedited App Review request. Raised two separate support cases with Apple Developer Support. Provided valid test credentials and all the necessary review information. Followed up through the available support channels. Unfortunately, we have not received any response from Apple apart from the automated case reference numbers. There has been no movement in the App Review status. We understand that Apple needs sufficient time to review apps and that all apps must comply with its guidelines. However, waiting for seven days without any update, despite multiple escalation attempts, is becoming a concern. I would appreciate guidance on the following: Is a 7-day wait in "Waiting for Review" normal for a first-time submission? Is there any additional escalation channel apart from the standard App Review support process? Can someone from Apple App Review Support help investigate why the submission has not yet been picked up? Any suggestions or assistance from developers who have experienced a similar situation would be greatly appreciated. Thank you.
1
1
68
2d
Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
Replies
0
Boosts
0
Views
8.2k
Activity
Mar ’25
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
Replies
1
Boosts
0
Views
31
Activity
53m
All 4 of My Original Native Games Rejected Under Guideline 4.3 & 4.2.6 – No Reply to Appeal/Expedite Request
Hello everyone, After waiting over a week in review, all of my recently submitted apps were rejected under Guideline 4.3 (Spam) and Guideline 4.2.6 (App Generation Services). The rejection messages are generic and do not specify which components, assets, or metadata triggered the flags. To clarify, these are original native apps built from scratch in Xcode/Swift—not commercialized templates, web wrappers, or third-party app generation builds—and each has distinct mechanics, custom assets, and functionality. I have already replied in the Resolution Center, submitted an official appeal/support inquiry, and requested an expedited review, but it has been 3 days with no response. Has anyone experienced false-positive 4.3/4.2.6 flags across multiple distinct apps on the same developer account, or can an Apple representative advise on what specific areas I should audit to get these resolved? Thank you in advance for your guidance.
Replies
1
Boosts
0
Views
126
Activity
53m
New App Rejected Under Guideline 4.3(a) on Both iOS and tvOS — Seeking Clarification
Hi everyone, I’d like to share my experience with the first release of my app and ask for some guidance. Submission details App ID: 6829444660 Platforms: iOS and tvOS (Apple TV) Initially submitted: November 1, 2026, at 7:17 PM Rejection received: November 13, 2026, at 9:30 PM Rejection reason: Guideline 4.3(a) — Design — Spam Both the iOS and Apple TV submissions received the same rejection at the same time. How the app was built I personally developed the app using UIKit, with some parts built in SwiftUI. I also created the visual assets myself using Canva. AI was not involved in writing or designing the app; its involvement was limited to testing-related assistance. Having personally worked on the implementation and visual design, it was discouraging to see the app classified as spam. I believe there may be a misunderstanding about my submission, and I would appreciate an opportunity to clarify it. What I’m asking for Could an Apple representative help identify the specific elements or duplication concerns that led to this rejection? Clear, actionable feedback would help me understand: Which aspects of the app raised concerns under Guideline 4.3(a). What changes, if any, are needed to address those concerns. What supporting information I can provide to help clarify the situation. This project means a lot to me. I respect the review process and want to meet Apple’s requirements. I would sincerely appreciate a reconsideration of my submission and clear guidance on how to move forward. Has anyone experienced a simultaneous 4.3(a) rejection on iOS and tvOS and successfully resolved it? Thank you for taking the time to read this. Any guidance would mean a great deal to me.
Replies
2
Boosts
0
Views
166
Activity
54m
Account flagged under 4.3: five unrelated apps rejected the same minute, replies unanswered for 9 days, rebuilt app rejected again as "similar"
Hi, I am a solo developer with an individual account since 2024. I would appreciate guidance from App Review, because I do not know what else I can do from my side. On October 13 at 00:06 all five apps I had in review were rejected within the same minute under 4.3 and 4.2.6, each with the same nine questions about the app, its audience, beta testing, shared code and templates. The apps are not related: a voice recorder with on-device transcription, a dice roguelike, a tile based dungeon game, a studio simulation game and a Safari extension for cookie banners. I built them myself in Xcode over several weeks and submitted each one when it was finished, which is why they arrived in the same week. No template, no generation service, no client, no third party SDKs, no other accounts. The same day I answered all nine questions in full for four of the apps and withdrew the fifth, the cookie banner extension, to rebuild it. Nine days later there is no response on any of the four threads. On October 21 I submitted the rebuilt extension as version 2.0. It now has consent receipts decoded from each site's TCF record, a public page listing the 100 sites tested before every release with the result for each, a separate mode for subscribe-or-consent walls, Global Privacy Control, Shortcuts and a Mac app. A review video and a public test page were attached. It was rejected within a day under 4.3(a) as sharing "a similar binary, metadata and/or concept" with apps submitted by me or others, with an Extended Review note. The only earlier app with this name is my own withdrawn 1.0. I have stopped submitting anything. My questions: Is there anything more I can provide for the four open threads so a reviewer can look at the apps themselves? I can send screen recordings, source code or demo builds the same day. For the 4.3(a) rejection: what was the app matched against, and what counts as a sufficient difference in this category, given that several cookie banner blockers for Safari were approved in 2026? App IDs: 6821429432 (Voice Notes: Local Transcribe), 6821423492 (Lampfall), 6821275353 (Bone Caster), 6819040142 (Vibe Coder), 6818993189 (Cookie Hide, version 2.0). Thank you for your time. Armen Ter-Oganezov
Replies
3
Boosts
0
Views
167
Activity
57m
Review submission stuck in "Canceling" for 12 days: version locked, can't cancel or resubmit
Our iOS review submission has been stuck in CANCELING since 10 Nov 2026. Every action on it is refused, so we haven't been able to ship an update for 12 days. App ID: 6809173786 Stuck submission: 0c25955e-e5d8-4835-8605-79f8115c9992 Developer Support cases: 103018649498, 103018648320 App Review case: 30000012887740 The submission has 4 items, all still "Ready for Review": iOS App 1.0.14 (app version) Lifetime-Flybud (our first non-consumable IAP) retention-3840x2160.png (Asset Library image) Flybud_Orbit_Header_3840x164… (Asset Library video) What the App Store Connect API returns (22 Nov): Cancel the submission: "Resource state is invalid – Resource cannot be canceled at the moment, please try again later." Remove an item: "Resource state is invalid – Item was already submitted." Add 1.0.14 to a new submission: "Asset Library validation error – Asset is locked by a standalone review submission." Submit the IAP on its own: "The first Non-Consumable In-App Purchase for this app must be submitted for review at the same time that you submit an app version." The version is locked by the stuck submission, and the IAP can only ship with a version, so everything is blocked. New builds upload and process normally. Given error 3, I suspect the Asset Library items are what's preventing the cancellation from completing. Since 10 Nov I've written to App Review four times, opened two Developer Support cases, filed a bug report and emailed the App Store team. Phone support has been unavailable, and App Review can't see the submission in their queue. Could someone at Apple escalate this to App Store Connect engineering to clear or complete the cancellation? Thank you.
Replies
0
Boosts
0
Views
7
Activity
1h
Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe
I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.
Replies
5
Boosts
0
Views
208
Activity
2h
Asked to resubmit after being offered bug fix approval, now 7 days in "Waiting for Review" with no response
Hello, We'd appreciate help from the App Review team with our app update. App: AI Video Generator - Bunsy (Apple ID 6762499422) Version: 1.0.13 (build 350) Submission ID: 644c0463-bcb1-44c5-a0bb-b91ccf1860c2 Timeline: Nov 4: submitted version 1.0.13. Nov 12: App Review identified a Guideline 4 issue (Sign in with Apple logo artwork) under Bug Fix Submissions. The message said the issue could be resolved in our next update, and that if we replied, the submission could be approved without resubmitting. Nov 12: we replied the same day and asked to approve the submission as a bug fix, committing to address the issue in the next update. Nov 13: App Review asked us to resubmit anyway. Nov 14: we resubmitted with build 350, which already includes the fix (native Sign in with Apple button). It has been in "Waiting for Review" since then. Nov 16: we requested an expedited review. Nov 19: we contacted App Review about the status (Case ID 103018616391) and have received only the automated confirmation. We followed every instruction we received, and this version has now been waiting for 17 days in total. It fixes a crash on first launch that affects users of the current version. Could you please check whether anything is holding this submission or whether anything else is needed from us? Thank you.
Replies
1
Boosts
0
Views
155
Activity
15h
First app stuck in "Waiting for Review" since Nov 13, after Guideline 2.1 info response
Hello App Review team, My first app, Rental Records, has been in "Waiting for Review" since November 13, 2026, and I'd appreciate it if someone could check whether it needs any action from me. App: Rental Records (iOS 1.0) Apple ID: 6832051224 Platform: iOS, Organization account Timeline: Nov 7: First submission Nov 8: Rejected under Guideline 2.1 (Information Needed) Nov 13: I added everything requested to the App Review Notes (app description, demo logins for both account types, list of external services, regional statement, and a screen recording) and resubmitted. Status has been "Waiting for Review" ever since. What I have already done: Submitted an Expedited App Review request days ago Called Developer Support twice and was told there is no fixed timeline Sent an App Review status inquiry (Case ID: [30000019474998]) The demo accounts work and the notes are complete. I'm happy to provide anything else you need. Thank you for your time.
Replies
1
Boosts
0
Views
144
Activity
15h
Concern Regarding App Review Timeline After Months of Organization Enrollment Delays – Fixit Employee Portal
Hello Apple Developer Community, I am reaching out to seek guidance and express our concern regarding our iOS application, Fixit Employee Portal, which is currently showing "Waiting for Review" in App Store Connect. Application Details: • App Name: Fixit Employee Portal • App Apple ID: 6834282511 • Version: 1.0.4 (Build 2) • Submission Date: November 13, 2026 • Current Status: Waiting for Review Before reaching this stage, our company had already spent several months completing the verification and approval process for our Apple Developer Program organization enrollment. We appreciate Apple's commitment to security, compliance, and quality throughout the enrollment and application review processes. However, after experiencing such an extended enrollment process, we are concerned about the possibility of further significant delays before our application becomes available to our employees. Our application is intended to provide essential employee services to our manpower workforce, including access to employment-related information and company resources. Many of our employees are awaiting its availability on iOS, and timely deployment is important to our daily operations. While we understand that our application was only recently submitted for review, we would sincerely appreciate clarification on the following: Is the current waiting period normal for a newly submitted application under a recently approved organization account? After several months of organization enrollment delays, should we anticipate another extended waiting period for the application review process? Is there a way to confirm that our application has no outstanding requirements that could delay its review? Given our employees' operational need for this application, would an expedited review request be appropriate? We are not requesting that Apple bypass its standard review requirements. We simply hope to understand the expected process and avoid further unnecessary delays after the lengthy organization enrollment experience. We sincerely appreciate the efforts of the Apple Developer and App Review teams and would be grateful for any guidance or assistance. Thank you for your understanding and support. Best regards, Fixit Development Team
Replies
2
Boosts
0
Views
131
Activity
15h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
Replies
1
Boosts
0
Views
145
Activity
15h
New app waiting for review since Nov 19: could App Review take a look?
Hello, I'm launching a new app, PlaPlu: Baby Development (Apple ID 6747391897). Its first version, 1.0.0 (build 202611191717), has been "Waiting for Review" since November 19 at 17:25 UTC. The status hasn't changed and App Review hasn't sent any message since then. Before that, the same version waited from November 16 to November 19. I took it out of the queue to swap in a build with a few fixes and resubmitted right away. So this first launch has now been waiting about five days in total. Everything for this version was submitted together: the build, the metadata and its in-app purchases. Could someone from App Review check whether the submission is stuck in the queue, or tell me if anything on my side is missing? I'll answer any questions right away. Thank you for your help.
Replies
0
Boosts
0
Views
94
Activity
17h
App Review Delayed for Over a Week – Anyone Experiencing the Same Issue?
Hi everyone, Is anyone else experiencing unusually long App Review delays recently? We have been waiting for our app to be reviewed since Thursday, November 12. Due to an issue with the previous submission, our developer resubmitted the app on Monday, November 16. Today is Friday, November 20, and our app is still waiting for review, with no visible progress. We have already submitted an Expedited Review Request, but we have not received any updates or confirmation that the review is progressing. This is becoming a serious concern because our game is scheduled to launch on November 25, and the continued delay is putting our launch schedule at risk. I would really appreciate hearing from other developers: Has anyone experienced similar App Review delays recently? How long did it take for your app to be reviewed? Is there any other effective way to contact Apple or escalate an urgent review issue, especially when an Expedited Review Request has already been submitted? Any advice or shared experiences would be greatly appreciated. Thank you!
Replies
10
Boosts
4
Views
527
Activity
1d
App Rejected Due to an Account Restriction, Not a Bug – No Response from Apple After Fixing the Issue
Hello everyone, I'm an independent developer, and I'm currently stuck in the App Review process. I'm hoping someone who has experienced something similar can offer some advice. My app was rejected because the reviewer encountered an error message when attempting to make an in-app purchase. However, this was not a technical bug or a StoreKit issue. It was an intentional account protection rule in my app. Here's what happened: My app has a rule that one Apple ID subscription can only be linked to one app account at a time. This prevents other accounts from taking over someone's paid subscription or sharing a single subscription across multiple accounts. During Apple's review, the sandbox Apple ID used by the reviewer had apparently already been linked to another test account. When the reviewer attempted to purchase a subscription using a different account, the app correctly triggered this restriction. Apple interpreted this behavior as a purchase failure and rejected the app. What I've done to resolve it: Although this rule is intentional and designed to protect users, I wanted to make the review process as easy as possible. I updated our server to remove this restriction specifically for sandbox subscriptions. Reviewers can now complete purchases and restore subscriptions even if their sandbox Apple ID was previously linked to another test account. The restriction remains unchanged for real production subscriptions. On November 17, I explained the situation to the App Review team and informed them that the sandbox issue had already been resolved. I asked them to test the purchase flow again. On November 18, I also requested a phone call to clarify the situation. The problem is that nobody has responded. I have not received any acknowledgment of my explanation, no response to my request for another review, and no phone call. I have also tried contacting Apple through the appeal process, but I still haven't received a response. At this point, I don't know what else I can do. The issue encountered during review has already been addressed, and no new app binary is required because the change was made entirely on our server. Has anyone experienced a similar situation where an app was rejected because an intentional business rule was mistaken for a bug? How did you get the App Review team to respond after explaining and resolving the issue? Is there any effective way to escalate this situation when both review messages and appeal requests go unanswered? submission ID 78b8dd94-fd4c-4951-959b-4fdb57a659d7 I would really appreciate any advice. Thank you!
Replies
0
Boosts
0
Views
106
Activity
1d
App stuck in "Waiting for Review" after resubmission + pending individual-to-organization conversion
Hi everyone, I'm hoping someone (or someone from Apple) can help or share their experience. My first iOS app was rejected under Guideline 2.3.6 for an Age Rating answer. I corrected the Age Rating as instructed, replied in App Store Connect, and resubmitted on 18 November. It has been in "Waiting for Review" since then. Everything on my side appears complete: Agreements, tax forms and banking are all Active App Compliance items are all Active App Privacy is published No new messages from App Review I have also requested to convert my developer account from Individual to Organization (I've received my D-U-N-S number), but haven't heard back from Membership support yet. A few questions: Can a pending Individual-to-Organization conversion hold up an app review? Is anyone else seeing longer than usual "Waiting for Review" times at the moment? How long did your account conversion take, and is there a faster way to reach Membership support? Any advice would be really appreciated. Thank you!
Replies
0
Boosts
0
Views
83
Activity
1d
App stuck in "Waiting for Review" since October 13 – anyone else?
Hi everyone, I submitted my iOS app (Hatırlatıcım) for review on October 13, and it's still showing "Waiting for Review" today, October 26. It's been almost two weeks now, and the status hasn't changed at all. I haven't received any emails or requests for additional information from Apple either. I contacted Developer Support on October 19, but haven't heard back from them yet. I've seen a few other developers mentioning similar delays recently, so I'm wondering if this is a general issue with App Store reviews right now. Has anyone who submitted an app around October 13–14 had theirs reviewed yet? I'm also not sure if I should just keep waiting or if there's anything else I can do at this point. Thanks!
Replies
5
Boosts
1
Views
207
Activity
1d
First app stuck in "Waiting for Review" since October 13
Hello, Our first app, "Pizza Virus - Food Delivery" (Apple ID 6612290745), has been in "Waiting for Review" since October 13, 2026. Submission ID: ebbda6e3-893f-42b5-8398-0d7ee377695a Version 2.1.0, build 2.1.2 (3) This is a resubmission that fixes the launch crash App Review reported on October 6 (Guideline 2.1(a)). We added a UIApplicationSceneManifest and a SceneDelegate. We later found that the updated Program License Agreement (issued October 14) and our Free Apps Agreement were only accepted on October 23, which may have held the submission. Both are now active, and the Digital Services Act declaration is completed. We requested an expedited review and opened support case 103008067614, but have not received a response. Could App Review please confirm whether the submission is now in the review queue, or whether anything else is needed from us? Thank you.
Replies
3
Boosts
0
Views
285
Activity
1d
First release waiting two weeks after resubmission
Hi, our app Flipped (Apple ID 6778089894) has had no update since we resubmitted build 20 on Nov 6. The Nov 4 review flagged Guidelines 2.1 and 1.2. We fixed both in build 20, replied in App Store Connect with the details, and attached a screen recording, but haven’t heard anything since. This is our first release and we’ve been in review since September, so any update would really help. Submission ID: 4d2b40e3-2413-4c02-9e66-8ee58282f147. Thanks.
Replies
4
Boosts
1
Views
81
Activity
1d
App Stuck in "Waiting for Review" for 7 Days After Guideline 2.1 Resubmission
Hello everyone, I am looking for advice regarding a delay on my first iOS app submission. It has been continuously in "Waiting for Review" for 7 days, well beyond the typical 24-48 hour window, with no status update. Submission Details: App Apple ID: 6834147398 Version (Build): 1.0 (17) Submission ID: bd2a5346-79a6-4c72-a268-ad797cb9de95 Date Resubmitted: November 13, 2026, 6:48 PM Context & Steps Already Completed: This is a resubmission following a Guideline 2.1 (Information Needed) request. I attached the requested iPhone screen recording demonstrating the app in use and updated the review notes. The app requires no sign-in or account credentials to test. All App Compliance declarations are completed. Agreements, Tax, and Banking show Active. Digital Services Act (DSA) trader compliance and verification documents have been submitted. I have already submitted an Expedited App Review request and an App Store Connect support inquiry, with no response yet. Could anyone, or an Apple team member, advise whether anything might be holding up a Guideline 2.1 resubmission like this, and what I can do to help get the review moving? Thank you in advance for your help. Thank you in advance for your help!
Replies
0
Boosts
0
Views
54
Activity
2d
App Stuck in "Waiting for Review" for 7 Days – No Response from Apple Support
Hello Apple Developer Community, I am looking for guidance regarding an unusually long delay in the App Review process. We submitted our app on 13 November 2026, and as of today (20 November 2026), the app has been continuously showing Waiting for Review for 7 days. We have already taken the following steps: Submitted an expedited App Review request. Raised two separate support cases with Apple Developer Support. Provided valid test credentials and all the necessary review information. Followed up through the available support channels. Unfortunately, we have not received any response from Apple apart from the automated case reference numbers. There has been no movement in the App Review status. We understand that Apple needs sufficient time to review apps and that all apps must comply with its guidelines. However, waiting for seven days without any update, despite multiple escalation attempts, is becoming a concern. I would appreciate guidance on the following: Is a 7-day wait in "Waiting for Review" normal for a first-time submission? Is there any additional escalation channel apart from the standard App Review support process? Can someone from Apple App Review Support help investigate why the submission has not yet been picked up? Any suggestions or assistance from developers who have experienced a similar situation would be greatly appreciated. Thank you.
Replies
1
Boosts
1
Views
68
Activity
2d