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've sent out an app update to fix our login issues and even requested for an expedited review. We're now sitting on day 2 of waiting in review and no solution in site. Our users are dropping off and new users just cant login. It's a minor bug fix that we need to push out. Anyone know whats best way to get the review faster apart from expedited app review requests?

Hi Apple Team, i submitted my App for review on the 4/09, got a few questions to which i responded. the last round was on the 7/09 with a single question to which i also responded. Since then radio silence. i sent a few email via the portal, but no answer. Can someone tell me what is happening or why i dont get an answer? thanks

Hi, My non-consumable in-app purchase has been stuck in "Accepted" and never flips to "Approved", even though the app version it was submitted with is live on the App Store. Details: App: Athkari Premium: Prayer Times (Apple ID 6768779584) Product ID: athkar_lifetime (Non-Consumable) Status: Accepted, listed under the "In Review" group Live version: iOS 2.0.10, Ready for Distribution since Sep 4 App Review > Submissions shows no pending submission; every row is "Review Completed" The product's metadata is locked - I can't edit the localization (display name / description), can't edit the review notes, and can't upload a new review screenshot. "Add for Review" is greyed out, so I can't resubmit it either. I contacted Apple support by email and they told me they don't know why this is happening. Could you flip it to Approved, or tell me how to unlock it so I can resubmit? Thanks.

Hello, I’m looking for some advice regarding a TestFlight Beta App Review issue. My app, MyStory, was rejected twice under Guideline 2.1(a) with the same general message: App Review was unable to successfully access all or part of the app. In the first review, Apple specifically asked us to provide a demo account with content demonstrating the app’s functionality. We followed those instructions for Build 3: • Created a dedicated demo account with sample content in all four sections. • Added the username and password under Beta App Review Information. • Added testing instructions. • Replied to App Review with the credentials and instructions. Build 3 was nevertheless rejected again under the same Guideline 2.1(a), without specifying which part of the app was inaccessible. We have tested the app and the demo account ourselves, and everything works as expected on our devices. The app can also be used without an account, and users can create an account directly within the app. We have now replied to App Review asking them to identify the specific screen, step, or functionality they were unable to access. We are currently waiting for a response. Has anyone experienced a similar situation? In particular, I would appreciate advice on how to get a more specific explanation from App Review, or whether there is an appropriate way to escalate the issue if they cannot identify what was inaccessible. I’m also wondering how reliable the 24-hour response timeframe is in practice. It has now been more than a day and a half since I replied to App Review. Should I expect a response within a few days, or can Resolution Center replies sometimes take considerably longer? Thank you.

Hi all, We submitted our app in App Store Connect in August and initially got quick responses from Apple (~2 days). On Aug 22, we were rejected under Guideline 4.3(b) (Design - Spam). Our app is a dating app, so we understand why it can trigger the guideline, but we believe it offers a meaningfully different experience from what's already on the Store and wanted to make our case. The Review team's rejection message invited us to reply with more information, so we did on Aug 24. We haven't heard anything back since. We sent a follow-up on Sep 7, and that's also gone unanswered. It's now been about three weeks of silence after our initial reply. A few questions for anyone who's been through this: Is it common for Resolution Center threads to go quiet like this after a 4.3(b) rejection? Has anyone had success getting a response by escalating, and if so, how (phone support, a fresh submission, something else)? Should we go through the formal Appeal process instead, or does that risk cutting off the conversation we already started in Resolution Center? Any advice from people who've navigated a similar situation would be appreciated. Thanks!

As a 3D artist specializing in spatial installations, I faced the constant risk of designs looking balanced on screen but failing in physical proportions on the production floor. Starting with no traditional coding background, I embraced AI-assisted development and the CORE learning framework to master Swift, ARKit, and RealityKit. Real ini was built out of real practitioner necessity: turning the iPhone and iPad into on-site spatial validation studios that bridge digital art into physical reality. Download my app for free : https://apps.apple.com/id/app/real-ini/id6805716872

Hello, I would like to ask the App Review team to look into a first submission that has not moved for nine days. Apple ID: 6792008109 Platform: iOS Submission: version 1.0, submitted August 30, 2026 Current status: Waiting for Review (has never transitioned to In Review) There is nothing pending on my side: No rejection and no message in the Resolution Center No metadata issue flagged No request for additional information Agreements, Tax and Banking complete App Privacy completed and working demo credentials provided I have also submitted an expedited review request through the Contact Us form. I understand review times vary with submission volume, and I am not asking to skip the queue. I am asking for visibility on whether this submission is queued normally or sitting in an error state, since nine days with no transition is well outside the expected range. Could the App Review team please investigate? Thank you.

Hi everyone, I'm hoping someone from Apple or another developer has seen this before because I'm completely blocked from submitting my first auto-renewable subscription. Setup First app submission App version: 1.0 (Build 34) One auto-renewable subscription Five consumable IAPs Everything configured in App Store Connect StoreKit works correctly in TestFlight Subscription purchases complete successfully in TestFlight RevenueCat configuration has been verified Subscription review screenshot is uploaded and processed successfully Problem App Store Connect shows: "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." The draft contains: App Version 5 Consumable IAPs 1 Subscription When I submit through the App Store Connect API I receive: STATE_ERROR.SUBSCRIPTION_SUBMISSION_REQUIRES_GROUP_VERSION A subscription must be submitted with its subscription group version when the group has no prior approved version. That makes sense because this is my first subscription. However, when I attempt to create a subscription group version I receive: STATE_ERROR.ALREADY_EXISTS Version already exists. There is already an inflight version with id: bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a So I then attempted to add that existing SubscriptionGroupVersion to the review submission. Apple responds with: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a is using an older format that is not supported for review submission. Please update before submitting. and also: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_INVALID_STATE Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a cannot be submitted. Only versions in Prepare for Submission or Developer Rejected can be submitted. The issue I'm now stuck because: Apple says I must submit a SubscriptionGroupVersion. Apple says one already exists. Apple will not allow me to create a replacement. Apple will not allow me to submit the existing one. Apple says the existing one is using an older format. I cannot find any way in App Store Connect to update, replace or delete this SubscriptionGroupVersion. Things I've already verified Build 34 is attached correctly. Subscription Product ID is correct. RevenueCat configuration is correct. StoreKit loads the subscription successfully. Purchases work in TestFlight. Subscription review screenshot exists and is COMPLETE. Localizations, pricing and availability are all configured. The issue occurs both in App Store Connect and when submitting via the App Store Connect API. Question Has anyone encountered this before? Is there a way to regenerate or migrate a SubscriptionGroupVersion into the new format from App Store Connect, or is this something Apple Developer Support has to reset on the backend? Any advice would be greatly appreciated. Thanks!

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 Apple Developer Support Team and Developer Community, We are seeking assistance regarding our app review status. App ID: 6758329405 Our updated version was submitted for App Review, but it has remained in “Waiting for Review” status without any progress or feedback. We have also contacted Apple through the available support channel to request assistance, but unfortunately, we have not received a response or status update so far. This has become increasingly urgent because our app is planned to support an offline bicycle exhibition and promotional event around October 1, 2026 (China’s National Day holiday). We have already completed significant preparations for the event, and the updated app is an important part of our overall launch and exhibition plan. We fully understand that Apple needs time to review every submission, and we are not asking for preferential treatment. Our main concern is that we currently have no information about the status or expected progress of the review. Could an Apple representative please help check the status of App ID 6758329405 or advise us on the appropriate way to obtain an update from the App Review team? As October 1 is approaching, any assistance or status information would be greatly appreciated. Thank you very much for your help.

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.

Hello, Thank you for your efforts to follow our guidelines. There are some outstanding issues that still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: 3a8aadf3-5812-4cc0-ab68-74e1f635f764 Review date: September 08, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (28) App Version Guideline 2.1(b) - Information Needed We have started the review of the app, but we are not able to continue because we cannot locate the In-App Purchases within the app at this time. Next Steps To help us proceed with the review of the app, please reply to this message providing the steps for locating the In-App Purchases in the app. Note that In-App Purchases are reviewed in an Apple-provided sandbox environment. Make sure they have been appropriately configured for review in the Apple-provided sandbox environment. If you are restricting access to In-App Purchases based on factors such as storefront or device configurations, please include this information in your reply along with steps to enable the In-App Purchases for our review. Additionally, note that the Account Holder must accept the Paid Apps Agreement in the Business section of App Store Connect before paid In-App Purchases will function. Resources Learn more about offering In-App Purchases. Learn more about testing in sandbox. Learn more about submitting In-App Purchases and subscriptions to App Review. Guideline 2.3.2 - Performance - Accurate Metadata Issue Description We noticed that your promotional image to be displayed on the App Store does not sufficiently represent the associated promoted In-App Purchase and/or win back offer. Specifically, we found the following issue with your promotional image: – Your promotional image includes text that is small or otherwise hard to read. Next Steps To resolve this issue, please revise your promotional image to ensure it is unique and accurately represents the associated promoted In-App Purchase and/or win back offer. If you have no future plans on promoting this In-App Purchase product, you can delete the associated promotional image in App Store Connect. Resources Learn how to view and edit In-App Purchase information in App Store Connect. Discover more best practices for promoting your In-App Purchases on the App Store. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey. Test on the latest betas Betas of iOS 27, iPadOS 27, macOS 27, tvOS 27 and visionOS 27 are now available. Download the latest betas to prepare your app for upcoming software releases. Learn more about installing and using Apple beta software.

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?