In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Here are some tips from App Review for a smooth review experience. We’ve split them into two categories: Before You Submit and After You Submit. We’ve also made an easy-to-follow Submission Guide you can save and reference at any point on your App Store journey. Before You Submit Tips Enable a complete review. Make sure you’ve provided demo accounts or implemented an account demonstration mode before you submit. We’ll need to review the entire app experience, both with and without an account. Provide up-to-date demo account login credentials in the App Review Information section on the app version page in App Store Connect. If your app has multiple account types (such as admin and general users), use the Notes field to provide additional demo account credentials for each account type. If your app requires an authentication code in addition to the login credentials, provide the code in advance in the Notes field. Otherwise, a call may be required to complete the review. Apps that handle sensitive user information, or operate in highly regulated industries, can implement demonstration modes that exhibit full features and functionality while using demonstration data. Use the Notes field in App Store Connect to provide information to App Review. The App Review Information section of App Store Connect includes a Notes field. Provide any information that could be relevant to your submission’s review: Submitting a new app? Tell us about your app's concept, business model, and if your app is designed to only operate in certain locations. Submitting an update? Tell us about what’s changed and where to locate significant new content or features. Connecting to hardware? Attach a video, not a screen recording, that shows both the hardware and the app running on a physical Apple device as they pair and interact. Test your app on physical devices before submitting for review. Use TestFlight to distribute your app for beta testing. App Review evaluates apps the way your users will use them: installed on real devices and connected to networks with real-world conditions. Make sure your pre-submission testing includes running the app on each device platform where it could be used. Users expect the app to function on all the devices where it’s available. TestFlight will help you do quality assurance and beta testing on real devices. Share your beta app with internal testers on your Apple Developer Program account or to external users via an email invite or public link. Configure In-App Purchases for review in the sandbox environment. App Review assesses In-App Purchases in the same sandbox environment Apple provides for testing them. The sandbox lets us use real product data and server-to-server transactions, without incurring any financial charges. Take these steps to prepare your In-App Purchases for review: Accept the Paid Applications Agreement in App Store Connect. Submit the In-App Purchases in App Store Connect that you’d like reviewed. Follow the steps in TN3186: Troubleshooting In-App Purchases availability in the sandbox if your app fails to display your In-App Purchases. Note: In-App Purchases don’t need prior approval from App Review to function in review. Join a Meet with Apple event if you need assistance before you submit for review. Request an App Review appointment through Meet with Apple to chat with an App Review expert about how to prepare for review, ask questions about specific guidelines, and discuss other topics related to the review process. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays. After You Submit Tips Contact App Review if you need assistance with an ongoing submission. If your submission doesn’t pass review and you have questions, contact App Review directly by clicking Reply to App Review in App Store Connect. You’ll receive a reply from a review specialist who’s familiar with your app. You can also use the Reply to App Review message window to request a call with an Apple representative. Include your preferred time and language for the call and we’ll do our best to accommodate your requests. Use the Bug Fix Submissions process to quickly deliver bug fixes and resolve other issues on the next submission. If an update includes bug fixes and is rejected, you will be given the option to resolve the issues on your next submission, as long as there are no legal or safety concerns. App Review will let you know if your submission is eligible by including this note at the top of the rejection message: Bug Fix Submissions The issues we've identified below are eligible to be resolved on your next update. To accept this offer, simply reply to the rejection message in App Store Connect and let App Review know you’ll resolve the issues on the next submission. Share ideas with Apple about how to improve or clarify the App Review Guidelines by submitting guideline feedback. Just as the App Store is always changing and improving to keep up with the needs of customers, the App Review Guidelines may be revised to provide new and updated guidance. If you have ideas for improving or clarifying our requirements you can suggest guideline changes. If your submission was rejected but you believe it follows the App Review Guidelines, consider submitting an appeal to the App Review Board. If your submission didn’t pass review but you have reason to believe it follows the App Review Guidelines, you can submit an appeal to the App Review Board. You can also file an appeal if you think we misunderstood your app or the review was unfair. The App Review Board will contact you as soon as they complete their investigation.

Apple platforms make it easy to distribute your app to a variety of compatible devices, so it’s important to maximize your app experience on each platform you support. Here are some tips from App Review to help you understand how device compatibility impacts your app’s distribution — and how to make sure your apps shine on every platform they’re on. Understand device compatibility There are many ways an app built for one Apple device can run on other Apple devices: Apps designed for iPhone can run on iPad devices in compatibility mode if there are no dependencies on iPhone device capabilities. Compatible iPhone and iPad apps can run unmodified on Macs with Apple Silicon. Compatible iPhone and iPad apps can run unmodified on Apple Vision Pro. Xcode provides options to configure settings for apps on multiple platforms. You can specify which platforms your app’s target supports in the Supported Destination field. However, it’s important to note: People may still be able to run your app on a device even if you remove it or don't include it as a Supported Destination in Xcode. For example, as long as an app designed for iPhone doesn’t depend on a capability that’s only available on iPhone, it can be downloaded from the App Store onto iPad. Adding or removing iPad as a Supported Destination in Xcode won’t change that app’s availability on iPad. To view examples of cases where it's appropriate to restrict availability, see Restrict device distribution below. Follow compatibility best practices 1. Plan and test for compatibility modes so your app works on every device where it can be downloaded. Do: Use Xcode simulators to verify basic functionality across different device types. Leverage TestFlight with external testers who have access to a wide range of Apple devices. Don't: Don’t submit for review without testing your app’s behavior in compatibility modes. Don’t assume removing a supported destination in Xcode prevents distribution to that device type. 2. Build adaptive interfaces that work across device variations. Do: Build interfaces that respond to different screen sizes and orientations. Adapt features based on available hardware, providing alternatives for a consistent experience. Don't: Don’t design rigid interfaces that assume only one type of device or input method. Don’t let your app crash or become unusable when optional hardware is unavailable. Restrict device distribution Wherever possible, it’s best to make your app available on multiple platforms to increase its reach and provide people with a consistent experience across devices. But there are cases where it does makes sense to restrict an app’s availability. For example: iPhone apps that rely on iPhone-specific hardware won’t function as expected on iPad. Use the UIRequiredDeviceCapabilities key in the information property list file to specify hardware dependencies. Note: Apps should only use the UIRequiredDeviceCapabilities key for genuine hardware dependencies, not to indicate distribution preferences. Navigation- or camera-based apps are not well suited for visionOS. Learn more about managing availability of iPhone and iPad apps on Apple Vision Pro. Apps that rely heavily on touch inputs that can’t be replicated on a keyboard are not well suited for macOS. Learn more about restricting distribution to Apple Silicon devices. Learn more about how to configure multiplatform apps in Xcode. Support If you need more assistance, explore these support options: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review appointment through Meet with Apple. Appointments are available during local business hours on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board.

Apple is committed to keeping the App Store a safe place for users to get apps and a great opportunity for all developers to be successful. A reliable review process is critical to this commitment, which is why App Review works around the clock to review at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Updates with minor changes and bug fix submissions typically move swiftly through review, while other reviews may take longer because they require additional verification. In this post, we'll explain when that can happen and how you can best prepare your submission for a thorough review. Why some reviews require more time While most submissions are reviewed within 48 hours, some apps may require additional time because the review involves extra verification steps, such as: Documentation review, where App Review requests and verifies supporting materials such as authorizations, licenses, or partnership agreements before approving the submission. Complex or novel issues, including apps with regulated content, new platform capabilities, entitlements enabled, or other sensitive features, may require greater scrutiny and consideration. Common examples may include: Medical apps involving health data, diagnostic or treatment features, or other medical claims often require documentation supporting those claims or demonstrating regulatory approval. (Guideline 1.4.1) Cryptocurrency exchange apps must be offered by an approved exchange and secure the necessary licensing to operate on each storefront where the app is available. (Guideline 3.1.5) Apps operating in highly regulated industries, such as banking and financial services, air travel, healthcare, and similar sectors, must be submitted by authorized legal entities with supporting documentation. (Guideline 5.1.1(ix)) Apps with third-party intellectual property require verifiable permission to use another party's content, branding, or other protected material. (Guideline 5.2.1) Gambling, lotteries, and real-money gaming apps must provide the necessary licensing and permissions for each storefront where the app is available. (Guideline 5.3.4) If your app falls into one of these categories, the most effective way to reduce your review time is to attach all requisite documentation we'll need for review in the App Review Information section of App Store Connect. Why this matters: Incomplete submissions require additional back-and-forth before we can complete the review. Including everything upfront is the fastest path to a decision. Best practices to minimize delays 1. Provide complete information on every submission. Give App Review everything needed for a complete review, especially for apps with regulated, specialized, or otherwise complex content. Do: Include demo accounts, authentication codes, and any required setup steps in the App Review Information section. Use the Notes field to explain your app's concept, business model, or authorization to operate in regulated industries. Attach all relevant supporting documentation before submitting the app for review. If you're unsure what information is needed for review, schedule an App Review appointment through Meet with Apple to discuss your app's concept. Don't: Don't resubmit the app for review until all identified issues are resolved. Why this matters: Resubmitting with unresolved issues will result in the same outcome, meaning the submission spends additional time in the queue without a different result. 2. Only provide authentic and verifiable information on your developer account. Authentic account information and high-quality apps build customer trust and keep your submissions moving smoothly through review. Do: Keep your developer name, Support URL, and account information current. Provide authentic, verifiable documentation whenever it's required. Only submit apps that have been thoroughly tested on physical devices and are ready for distribution. Don't: Don't submit documentation you're not authorized to use, or that can't be independently verified. Don't misrepresent your identity or relationship to other brands or services. Don't submit apps that are low-quality, untested, or include incomplete content or features. When fraud or malicious activity is detected To protect the App Store's high standards for privacy, security, and quality, we have zero tolerance for fraudulent or malicious activity. App Review investigates all reported or identified conduct that falls outside the App Review Guidelines and the Developer Code of Conduct, which requires accurate representation and integrity across the App Store experience. Examples include: Misrepresented developer identity or impersonation, such as providing inauthentic documentation or otherwise pretending to be someone you're not (Guidelines 4.1 and 5.6.2). Manipulation of the App Store experience, including gaming charts, search results, reviews or referrals, or attempting to hide features in review (Guidelines 2.3.1(a) and 5.6.3). Submitting low-quality apps, as indicated by excessive customer reports, such as negative customer reviews, and high-volume refund requests (Guidelines 4.3 and 5.6.4). When these signals appear, we investigate thoroughly, and repeated or serious violations can lead to additional rejections, app removals, and account removal from the Apple Developer Program. Support before or during your review If you have a critical timing issue, such as fixing a critical bug or releasing your app to coincide with an event, you can request an expedited review. If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. You can also reply to request a call with an Apple representative to discuss the outcome of the review. If your app has been rejected and you believe it follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Appeals must include specific, detailed explanations for why your app follows each of the guidelines in question.

Title: Guideline 5.6 and disclosed network fallback routing — how strict is "no concealment"? We received a 5.6 rejection ("features that appear to have been intentionally hidden during review") for a VPN app. After investigation, we identified that some of our servers used SNI-based domain fronting (TLS handshake to a Google hostname, real destination in the HTTP Host header) as their primary connection method in regions where our own infrastructure is blocked at the network level. We disclosed this fully in App Review Information before resubmitting: what it is, why it exists, and that we removed it from all servers. We received the same 5.6 wording again on the next submission. Questions for anyone who has navigated this: Does prior undisclosed use of a technique like this permanently flag the app/account for stricter automated review, even after the technique is removed and disclosed? Is domain fronting for VPN tunnel traffic (not just API calls) treated as inherently disqualifying under 5.6, regardless of disclosure — i.e. is there no version of "explain it" that satisfies this, only "remove it entirely"? For apps serving regions with network-level blocking of VPN protocols, is there a legitimate, App Store-safe way to maintain connectivity without triggering 5.6 — e.g. is Reality-protocol-style obfuscation treated differently from SNI fronting to a real third-party domain like Google's? Any pointers to relevant guideline clarifications or past resolved cases would help. Thanks.

Hi, I have been waiting an insane amount of time for my app to get reviewed. It’s been Waiting for Review forever. I am making this post to see if an App Reviewer can directly review my app, as I have an ongoing competition, which there is an upcoming deadline. If there’s anything you can do, please help. Thanks!

Ops Chat (Apple ID 6804704354, bundle it.opsmobile.chat), iOS 1.5 build 684, was submitted for review on September 9, 2026. An expedited review was requested and granted on September 12 and again on September 15, yet the version is still "Waiting for Review" and has never entered review. This is the first public release of the messaging app of Ops Mobile, an Italian mobile operator, and our customers are waiting for it. Is there anything we can do from our side to move the review forward?

Our first iOS submission has been "In Review" for 8 days with no update, no Resolution Center message, and no request for additional information. App: Lossic Apple ID: 6806576247 Version 0.2.0, build 31 Submitted: 2026-09-06 (In Review since shortly after) Bundle is a universal record (app.lossic.Lossic). The macOS version of the same record was submitted and approved normally during this same period, so this appears to be a procedural stall on the iOS review specifically, not a content issue. I contacted the App Review team (case 102957178109) 3 days ago and have not received a reply. Could App Review please look into why the iOS review has not progressed? Happy to provide any additional information needed. Thank you.

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

Hello App Review team, We urgently need help with our iOS app (Apple ID 6810751660), which has been in Waiting for Review since September 15, 2026. This is the official app for an event that begins this evening, September 15. Thousands of attendees rely on it for schedules, results, and on-site services from the very first day. If it is not available on the App Store in the next few hours, they will not be able to use it when the event opens. We have submitted an expedited review request, and the submission will stay unchanged. Our team is standing by and will respond immediately to any question from App Review. We would be very grateful if this submission could be reviewed today. Thank you for your help.

Title: macOS app in Waiting for Review after replying to a Guideline 2.1 information request Hello, My first macOS app (App ID 6811325879, version 1.0) was submitted on 12 September 2026. On 13 September I received a Guideline 2.1 – Information Needed message regarding the limited App Review history of my account. The same day I replied in the Resolution Center with all six requested items, and I also copied the same information into the Notes field of the App Review Information section, as the message instructed. Since then the submission has been in Waiting for Review with no further messages. The app is a simple offline PDF utility: no account, no login, no in-app purchases, no network connections. Is there anything else I should provide, or is this simply normal queue time for a new developer account? Thank you.

Apple ID: [6768179663] First submitted for review: 2026-08-31 Status changed to "In Review": 2026-09-02 Current status: In Review — 14 days with no status change Submission contents: app version + 6 in-app purchase / subscription items Resolution Center: no messages from App Review App Review Status case: opened [2026-09-09], Case ID 102957220208, no reply yet Context: this is our first submission. The app includes UGC (community posts, comments, and user reporting) and AIGC, which we understand may require additional review time. Question for the App Review team: is this submission currently assigned to a reviewer and being processed, or is it sitting in the queue? And is there anything on our side — review notes, demo account access, or a specific guideline item — that we should provide in order to unblock it? We are not requesting an expedited review. Demo credentials, screenshots, or a walkthrough video can be supplied on request. Curious whether other developers are seeing similar In Review wait times this month.

Hi, I am creating this post because my app has been "Waiting for Review" for centuries, without change. I completely understand that review times may vary; however, this amount of time is beginning to get absurd. If there's anything anyone at Apple can do, I would greatly appreciate it. Thank you so much!

Uploaded my first App for the app store! Apple said they have a very fast response time but despite their very quick response (only 8hrs after filling out all the paper work), their response felt very generic... basically saying "your a first time app creator we need more information" I responded to all questions and submitted a screen recording of the app and resubmitted for review. It's now been 4 days and no response to my resubmitted review! no email, no notice it was seen... Apple has all these stats about how fast they are to respond but if its just a quick fast initial generic response thats not really a response and its just a way for them to claim a high efficiency. Has anyone else encountered this? How long and how much back and forth should I expect publishing a basic app?

Hi everyone, I am seeking urgent advice or attention from the App Review team regarding a Pending Termination Notice I received for Section 3.2(f). The Situation: I recently acquired a portfolio of apps from another developer to start my business on the App Store. Three months after the transfer, my account was flagged for removal because one of these acquired apps "repeatedly violated guidelines to evade the review process." The Problem: I am being punished for the previous owner's actions. I have never submitted a new build, metadata update, or review request for this specific app since acquiring it. The Timeline (Proof of Innocence): August 4, 2025: Last update submitted by the Previous Owner. September 6, 2025: I signed the Purchase Agreement to start my business. September 9, 2025: App Transferred to my account. December 11, 2025: Termination Notice received. As the timeline proves, the alleged "evasion attempts" via submissions occurred before I even owned the app. Regarding "Unresolved Issues": I am aware the app had an old "Unresolved Issue" flag from September 2024. However, the previous owner successfully released multiple updates throughout late 2024 and 2025 despite this flag. As a newcomer to the App Store, I reasonably interpreted this as a system glitch in App Store Connect, given that Apple continued to approve new versions for a whole year. My Appeal: I have submitted an appeal via the Contact Us form, stating: I am a bona fide purchaser with legal proof (Purchase Contract & Bank Transfer records). I have never touched the code or submitted a build for this app. I am willing to immediately remove the problematic app to save my account and the other legitimate apps I am operating. Request: If an Apple Staff member sees this. Please review the transfer logs. I am a victim of the seller's hidden violations, not a participant in fraud. Has anyone else faced a termination for an acquired app they never updated? Thank you.

Hello, My app Longhaul Packing (App ID 6756682312) has been in "Waiting for Review" since September 5, 2026 — nine days with no status change. This is the first release for the app: version 2.1.1. There are no messages in Resolution Center, the status has not moved to Developer Action Needed or Metadata Rejected, and I have not received any communication from App Review. Agreements, Tax, and Banking are current, and export compliance information was provided with the submission. Could someone from the App Review team check whether this submission is stuck in the queue, or let me know if anything is needed on my end? Thank you, David

This is a Universal App supporting iOS, macOS, iPadOS, and visionOS under a single App Record with shared in-app purchases and subscriptions. While previous iOS and visionOS submissions were approved using these shared records, today's visionOS update was rejected under Guideline 2.1 for allegedly missing visionOS-specific in-app purchase records. Unless the policy has recently changed, a separate set of records for visionOS should not be required for a Universal App. Additionally, the system only allows one screenshot per in-app purchase, making it impossible to provide separate paywall images for each platform. Two weeks and counting, the macOS In Reviews have been going into blackhole while iOS and visionOS submissions are approved in less than 24 hours.

Hello App Review team, could you help check the App Store submission of Omen : Daily Intentions (Apple ID 6787705843), iOS 1.0.0, build 91? Developer Support accepted expedited review on September 3 and said it would carry over after resubmission. We resubmitted on September 8; App Store Connect still shows Waiting for Review on September 14. We have followed up in the existing support case and replied separately about TestFlight in App Store Connect. Could you confirm whether any action is needed from us or route the existing case to the right team? I can provide the case reference and correspondence privately through Developer Support. Thank you, Louis

Hello, Our app Kadoz has been in "Waiting for Review" for 8 days with no status change. Apple ID: 6807392986 Version: 1.0 (build 9) Submitted: September 6, 2026 Current status: Waiting for Review This is our first submission. App Review Information is complete, including demo account credentials for the passwordless sign-in flow. All agreements are signed and the privacy questionnaire is published. We contacted Developer Support but have not received a reply. Could you check whether anything is missing on our side? Thank you.

My first and only app, tower defense game (App ID 6802129713), was rejected under Guideline 4.3(a) Design – Spam. I'm a solo developer; the game is built on the open-source Godot 4 engine, with all code written from scratch and all art generated by my own tools in the same repository. The core of the game is a custom simulation running up to hundreds of thousands enemies on-device, which I believe no other App Store game does. I replied in the review thread with a point-by-point response to each 4.3(a) factor and asked which app mine is believed to resemble, but received only the standard template in return, so I don't know what to change. I've filed an appeal with the App Review Board. Has anyone successfully resolved a 4.3(a) flag in a similar situation? Is there anything else I can provide to demonstrate originality?

Hi everyone, My app update has been stuck in “Waiting for Review” for an unusually long time, and I’m hoping someone from Apple may be able to look into the submission or provide some guidance. I understand that App Review times can vary and that some submissions take longer than others. However, this submission has now been waiting significantly longer than I would normally expect, and I’m concerned there may be an issue preventing it from entering review. I’ve already checked App Store Connect and there doesn’t appear to be anything requiring action on my end. If someone from the Apple Developer or App Review team sees this, would it be possible to check whether there is an issue with my submission or help move it forward for review? I’d really appreciate any assistance. Thank you!

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

Hello App Review Team, I’m reaching out regarding Whispry, which has been submitted for App Store review and has been waiting longer than expected. The latest version is still showing as In Review / Waiting for Review, and I would appreciate it if you could confirm whether there is any issue with the submission or if any action is required from my side. App Name: Whispry Version: 2.0 Build: 3

I received a Pending Termination Notice under ADPLA 3.2(f) on September 1. The identical notice was posted into the message thread of every app on my account, so it's account-level rather than tied to one app. The stated evidence was repeated submissions attempting to evade review. I filed an appeal admitting the conduct rather than disputing it, and set out the remediation with dates. That was two days ago, no response yet. Since filing, I audited the rest of my apps and found competitor app names in some keyword fields. I hadn't connected that to the termination, but 3.2(f) does mention unfair competition and consumer confusion, and I had a naming complaint from another developer resolved through Apple earlier this year. My questions: Has anyone filed a second appeal while the first was still pending? I've read about a second appeal succeeding after the first missed the real cause, but mine already admits the main issue. Unsure whether adding this strengthens the case or just muddies it. Is competitor keywords the kind of thing that contributes to an account-level action, or is it normally just a 2.3.7 rejection? For anyone who has been through a 3.2(f) termination - roughly how long did the App Review Board take to respond? Happy to share how it turns out either way, since there isn't much written about this process.