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.

I'm hoping someone from Apple or another developer has some advice. I have an app update that has been stuck in "Waiting for Review" for 12 days. This is not a new app, it's a small update whose primary purpose is to fix a critical bug that's affecting my users. Here's what I've already tried: Submitted two expedite review requests through the official form (I rarely use this process, so it's not something I've abused). Emailed App Review support twice to explain the situation. So far, I've received no response to either the expedite requests or the emails. At this point, users are continuing to experience a bug that has already been fixed, but I have no way to get the update to them. It's hurting the user experience, causing me to lose users, and is directly impacting my revenue. Has anyone experienced something similar recently? Is there anything else I can do besides waiting? I'd really appreciate any guidance, and if anyone from Apple is reading this, I'd be grateful if someone could look into this situation.

Hello App Review Team, Our iOS app has been stuck in "Waiting for Review" for more than 12 days with no status change and no Resolution Center messages. App name: Express Evaluations Developer: Express Evaluations, Inc Platform: iOS Version: 1.0 Current status: Waiting for Review Submitted: July 30, 2026 at 11:52 AM We opened an App Review Status case on August 10, 2026 and have not received a reply yet. Case ID: 20000133168856 This delay is blocking our planned release and is affecting stakeholder trust in our launch timeline. Could someone from App Review please check whether this submission is stuck in the queue and advise on the current status? Thank you for your help.

I’ve been trying to get this app through App Review for more than two months now. It was rejected a few times before. I changed what Apple asked me to change and submitted it again each time. The current version has now been sitting in Waiting for Review for quite a while and nothing is happening. I’m actually not very familiar with the App Store review process, so I’m not sure how long Waiting for Review is supposed to take. Do I just leave it there and wait? Or should I submit it again? I’m also wondering if I need to create a new submission / new ID at this point. I don’t want to keep changing things if that just sends me back to the beginning of the queue. The whole thing has already been going on for more than two months, so I’m a bit lost on what I’m supposed to do now. Has anyone run into this before?

Hi all, I hope someone from App Review can take a look My situation: QuidProQuote: Memory Keeper (app ID: 6791349683) is a simple cross-platform app where a single purchase unlocks both the macOS and iOS versions. Both versions were submitted from the same build/codebase. The problem is that while my macOS version has been approved and is now pending my release, the iOS version (submission ID: 9fba8d59-d9a7-4a09-bbbe-1d23035adbe1) has been "Waiting for Review" for 12 days now. 2026-07-30, ~4:30pm ET: Both macOS and iOS submissions entered "Waiting for Review" 2026-08-06, ~10am ET: macOS version approved, now Pending Developer Release 2026-08-11 (Today): iOS version still showing "Waiting for Review," 12 days with no status change This ends up being more than a normal wait because the purchase is shared across platforms... releasing the macOS version now would put it in front of customers without the iOS half of what they're paying for. I can't release the approved macOS build until the iOS version clears review, so the delay on one platform is effectively holding both hostage. I did file an expedited review request today (2026-08-11), received confirmation ("we'll expedite this review"). But I read advice that additionally it would be wise to register the problem here. Thanks for any visibility into this!

Our initial release has been in "Waiting for Review" since July 29, 2026. As of today, August 11, it has never progressed to "In Review." App ID: 6771136749 Version: 1.0 Submitted: July 29, 2026 Support Case ID: 20000135031799 Details: Initial release, not an update Build has not been cancelled or resubmitted at any point Free Apps Agreement is active; no paid features or IAP Metadata, screenshots, and App Review Information (including demo credentials) are complete No messages in Resolution Center I filed a support case today but wanted to post here as well in case anyone from App Review can confirm whether the submission is correctly in the queue. Has anyone seen initial submissions sit this long recently without moving? Interested in whether this matches the backlog others have reported this year.

Summary I am unable to link my In-App Purchases and Subscriptions to my app version in App Store Connect. The "In-App Purchases and Subscriptions" section described in Apple's documentation is not visible on my version preparation page, making it impossible to associate IAPs with my build before submission. Steps to Reproduce Open App Store Connect → My Apps → [App Name] Navigate to the app version in "Prepare for Submission" state Scroll through the entire version page The "In-App Purchases and Subscriptions" section is not present anywhere on the page Expected Behavior According to Apple's documentation and the note shown on the Subscriptions page itself: ▎ "Your first subscription must be submitted with a new app version. Create your subscription, then select it in the 'In-App Purchases or Subscriptions' section of the app's version page before submitting the version for review." The section should be visible and allow me to select my configured subscriptions. Actual Behavior The section does not appear on the version page at all. My subscriptions (monthly, yearly, lifetime) are all in "Ready to Submit" state and correctly configured, but there is no way to link them to the build. Account & Contracts Status All prerequisites are in place: All contracts (Paid Apps Agreement) are signed and active — nothing pending under "Business" / "Agreements, Tax, and Banking" Banking and tax information is fully set up No open items or warnings under the Business section in App Store Connect Despite all account requirements being fulfilled, the IAP linking section remains absent from the version page. Impact This is blocking my app from being approved. Apple's reviewer rejected my submission with Guideline 2.1(a) stating the subscription screen showed no available plans. The reviewer cannot see the IAPs because they were never linked to the version — which I cannot do due to this missing UI section. Environment App Store Connect via browser (Safari + Chrome, both tested) App status: "Prepare for Submission" IAP status: All three products "Ready to Submit" First-time submission (new app, never been approved before) Workaround None found. This appears to be a UI bug in the current version of App Store Connect. Has anyone else encountered this? Is there a way to link IAPs to a build via the API or any other workaround?

My iOS app, Marketplace Guardian, was submitted to App Review on August 4, 2026 at approximately 2:27 PM and has now remained “In Review” for approximately seven days. Submission ID: c331b8f0-86ec-4511-8263-3c97b71a8382 There has been no rejection, request for additional information, or other communication from App Review. I understand that review times can vary, but Apple states that 90% of submissions are reviewed in less than 24 hours. I am therefore trying to determine whether this delay is normal or whether there may be an issue preventing my submission from progressing. I have contacted Apple Developer Support twice without receiving a response. Today I also contacted Apple Support and spent approximately one and a half hours on hold attempting to reach Developer Support. During my support interaction, I was transferred to a supervisor. I asked for clarification regarding the support process and requested documentation of the policy and procedure concerning the inability of consumer Apple Support to escalate or contact Developer Support. Before all of my questions were answered, the supervisor ended the chat. The issue was therefore not resolved, and I was left without an answer regarding the status of my App Review submission or a clear path to obtain assistance. I am extremely frustrated with this experience. I am currently in the process of documenting the matter for submission to the Better Business Bureau and the appropriate consumer protection agency because I have been unable to obtain a timely response or meaningful assistance through Apple's available support channels. I am not asking for preferential treatment or guaranteed approval. I simply want someone with access to App Review to confirm that my submission is properly progressing, determine whether anything is preventing the review from moving forward, and let me know whether anything is required from me. Has anyone else experienced a similar “In Review” delay recently? Any information from other developers or Apple regarding unusually long App Review delays would be appreciated.

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

I understand that they/you are probably being flooded by a lot of AI slop apps or other excuses, but submitting an app 3 weeks ago and it being stuck in Waiting for Review (not first app live on app store either) is beyond a joke. Lodge a support request (not expedited review request) and to get back a generic you will be notified when it changes to In review is not the sort of support help you would expect either. This sort of delay impacts businesses (time and money) and needs to be fixed by either putting more reviewers on - OR better still move more towards the Automated review process Google uses. meantime it still sits there in waiting for review.

Relatively new to development for Apple, first submission followed the general guidance of timeframes for review (around 48 hrs but probably a little more) , but WOW have had a follow up release sitting there for almost a week and no movement - got too the point that had to pull it and replace it to fix some critical issues being reported through the "other app distribution platform" and now same problem with the revised submission. Not only that have submitted two non-related development support enquiries (you know where they say they will get back to you in 24 hrs) - umm 4 days and no response. Should we be all submitting for expedited reviews - has Apple sacked 3/4 of it review team ? What is going on with Apple Support and App Review timelines??

I received a Pending Termination Notice on my Apple Developer account citing sections 3.2(f) (fraudulent conduct) and 5.6.2 (Developer Identity - falsely represented yourself). The problem is that Apple has not told me what information is allegedly false or fraudulent. Everything on my account is my real legal name, real identity, real address, and real documents. I have never submitted false documentation. I have never misrepresented who I am. Earlier this year, I received a copyright complaint from a competitor. Apple's legal team investigated it for a full month. I cooperated with every request. I changed the app name, changed the icon, changed the tagline, removed the app from sale in every country. Apple closed the case and sent me an email stating: "We trust this resolves your concerns and consider this matter closed." Now, months later, I have received a pending termination notice without any explanation of what specific information is false. I have submitted an appeal through the official form. I have also emailed Apple Developer support and executive contacts. But I have no way to defend myself when I do not know what the accusation actually is. My questions for the community and any Apple staff who may see this: Has anyone received a 3.2(f) / 5.6.2 notice and successfully resolved it? What did you do? Is there any way to get Apple to specify what information they believe is false? How long does the App Review Board typically take to respond to termination appeals? Is there any escalation path beyond the appeal form and developer support emails? There is a significant amount in earned proceeds frozen in the account. This is my livelihood. I am a legitimate developer with a real business, a real app with real users, and I have never done anything dishonest. I am willing to provide any document Apple asks for. I just need someone to tell me what the issue is so I can address it. Any advice or shared experiences would be greatly appreciated. Apple ID: 6777752146 Team ID: XJR63P2754

Hi everyone, My app has been sitting in "Waiting for Review" since July 16 — 18 days now, and it has never moved to "In Review". • App name: Tepa: Remote Reader • Apple ID: 6770857002 • Submission ID: 290281f3-f98c-4bc1-a6d0-07efe16eda39 • Type: new app There's nothing on my end to act on: Resolution Center is empty, no rejection, no requests for more info. I emailed App Review support 5 days ago (case 20000120461790) and haven't heard back. I'd rather not push with expedited review requests - I know the team is swamped and I don't think my case is more urgent than anyone else's here. But we have two large trade shows in September where we planned to present the app, and what worries me isn't approval itself so much as the time after it. If the review comes back with issues, I want enough runway to fix them properly and go through another round, rather than scrambling days before the events. Thanks.

Hi all, I submitted an update on 8/4/26 and it has been sitting in “Waiting for Review” with no movement. App ID: 6758522939 Version: 2.0.0 Platform: iOS Status: Waiting for Review since August 4th, 2026 There are no messages in Resolution Center or outstanding metadata requests, and nothing flagged on my end. My previous submissions have moved much faster than this. Especially updates, which have all taken less than a day… I have already contacted App Review through the contact form. I am mainly trying to understand whether this is the broader issue people have been seeing through 2026, or something specific to my submission that I should be looking at. If you have submitted in the last week or two, how long did yours sit in the queue before moving to In Review? Any patterns you have noticed around app category or routing would be helpful too. Thanks.

Hi everyone, My app just received a rejection citing Guideline 3.1.2(c) - Business - Payments - Subscriptions: "The auto-renewable subscription promotes the free trial, introductory pricing, or introductory period for the subscription more clearly and conspicuously than the billed amount." Does anyone have advice on how to resolve this? I am currently using "Try for Free" as the main CTA button to activate the trial, which seems to be a common industry practice. Any insights would be greatly appreciated!

Hello, This is my first app submission to the App Store. The version has been in "Waiting for Review" for several days and has not yet moved to "In Review". I did replace the build once (to fix a config issue), which I understand restarts the wait. Everything on my side is complete and ready. Is this waiting time normal for a first submission, or should I contact App Review directly? Any guidance on expected timelines would be appreciated. Thank you.

Hello, Our app was submitted on August 7 and has remained in “Waiting for Review” with no status change. This is now a launch-blocking issue for a scheduled enterprise customer rollout on August 13. Hundreds of participants are already scheduled for mobile user testing and are unable to proceed without the iOS app. We have submitted an expedited review request and contacted Developer Support, but have not received a response or any update from either channel. At this point, the App Review delay is directly blocking a committed enterprise launch and participant testing schedule. We would greatly appreciate any urgent assistance in getting this case reviewed or escalated to the appropriate App Review team. App Name: Satellica App Apple ID: 6797731123 Submission ID: b7105850-5a17-489d-907d-550febe3895a Thank you.

Hello, my app was rejected with this reason - Guideline 2.1 - Performance - App Completeness. Bug description: Sign in with Apple requests the Apple ID password rather than entering a code. The issue is that I'm using Clerk inside Expo and they don't support native Apple signIn, only web based. But when users open signIn for the first time - they need to login for appleId via web. I already submitted rejection appeal with explanation. Did someone encounter similar problems? The flow works correctly. In fact even apple testers went through and created accounts.

Hi Everyone, I really hate to be that guy but I was wondering if anyone else has been waiting as long as I have to get their app reviewed? I have an app that I put up for review July 30th and now we're on the 12th day waiting. (By the way, if you are an apple employee and you happen to see this message and want to help, the app is called Sudoku Every Day - Paper & Pen and the submission ID is f6750769-9018-4236-b413-ea07bc05d907). I know they are experiencing a backlog right now, and I've been patient understanding that. I guess I'm just a little frustrated because I see people on social media who supposedly put their app in after me that have already been approved, although I get that that's just random luck of the draw probably. Do you all think it's possible my app is stuck though? Should I request an expedited review? I kind of don't want to do that just because I bet everyone is doing that with the backlog and I don't believe I qualify for it. I do have a big update ready since I've added a lot of variants to my app in the last few weeks. That's ready to go but that's not really time critical ..... Another thing I was wondering is could this have something to do with the fact that I first tried to submit it after building in Xcode 27 beta? The beta builds kept getting auto-rejected so I had to eventually submit a build that I made on another computer (MacOS 26.6/Xcode 26.6) to get it to be accepted into review but that was the 6th build. Is there a chance my previous builds getting auto-rejected put me on some slow train to app review? Just curious to hear others experiences. If you made it all the way to the end of this, thanks for reading! -E

Hello, I am experiencing an unusually long wait for the first submission of my iOS app. App Store Connect details: Platform: iOS Version: 1.0 First submission for this app First submission for my developer account Current submission date: July 30, 2026 at 21:11 Current status: “Waiting for Review” Apple ID: 1413120388 The submission has now been in “Waiting for Review” for 12 days and has never moved to “In Review”. There are no messages in the Resolution Center and I have not received any request for additional information. The previous submission, made on July 28, was removed by me. The current submission is the new submission from July 30. The app is a fairly complex collaborative social application centered around maps, including shared geo-organizers and collaborative elements. I understand that review times can vary, especially for a first submission and for a more complex application. I am not requesting an expedited review. I would simply like to ask whether the current submission is correctly queued for App Review, or whether there might be an issue preventing the review from starting. Any guidance would be greatly appreciated. Thank you.

I submitted my first public build (iOS 1.0) on July 30th for my game, Golfer's Pair-A-Dice (Apple ID: 6789222313) and it has been in "Waiting for Review" with no movement since then. I read that 24-48 hours is typical, but could take longer for first builds, but it seems like it hasn't even begun to be reviewed which is frustrating. Has anyone experienced similar wait times in the queue and had any success getting their app reviewed? I was hoping to launch on App Store and Google Play Store at same time and Google approved the app in 2 days so it has just been waiting for me to push, which I am waiting on Apple to approve so I can push both simultaneously.