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 am posting this because I genuinely do not know what else to do. My company is based in Nigeria, and we submitted our app, MyCove, for App Store review. The app was rejected under Guideline 5.6. We responded to the rejection and explained the application, its purpose, its users, and how the functionality works. We also provided the information and access required for Apple to review the app. We have since: Communicated with the App Review team through App Store Connect Raised support cases regarding the rejection Requested clarification about the specific reason for the rejection Escalated the matter Submitted an appeal to the App Review Board Followed up repeatedly And yet, almost one month later, we still have not received a substantive answer to our questions or a meaningful update on the appeal. This is not simply a delay in getting an app reviewed. This is a business that has been unable to move forward for almost a month because we cannot even get a clear answer about what Apple believes is wrong with the application or what we need to do to resolve it. Apple's own documentation states that 90% of submissions are reviewed in less than 24 hours, and Apple's App Review FAQ states that Resolution Center messages are generally answered within 24 hours. Apple also states that developers can appeal when they believe an app was misunderstood or that they were treated unfairly during review. So my question is: If this were a company based in the United States, would the same situation be considered acceptable, almost one month without a substantive response to an App Review dispute or appeal? I am not asking for preferential treatment because we are a Nigerian company. I am asking whether Nigerian developers and companies receive the same level of responsiveness and due process during App Review as developers and companies in the United States and other major markets. If the answer is yes, then I would genuinely like to understand what is happening with our case, because almost a month without a substantive response does not appear consistent with Apple's published App Review communication timelines. I am not looking for someone to approve the app without review. I want Apple to tell us clearly what the problem is, what evidence led to the rejection, and what we need to do to resolve it. Case references: 102953967427 Has anyone else experienced an App Review appeal or rejection being left without a substantive response for this long? And, if so, how was it eventually resolved?

Our app has been in “Waiting for Review” for more than 60 hours, and the review has not started yet. We are working against a critical delivery deadline, as the app is required for committed customer deployment. We have already submitted an expedited review request, but the status has not changed. Normally, our previous submissions have moved to review much faster, so we are concerned about the extended waiting time. Has anyone experienced a similar delay recently, particularly after submitting an expedited review request? If so, how long did it take before the status changed to “In Review”? We would appreciate any guidance from the App Review team, as the delay is now putting our scheduled delivery at risk. Thank you.

Hello App Review team and fellow developers, Our iOS game, Rivalis Academia Nexus (Apple ID: 6793594102), version 3.2.1, has been in "Waiting for Review" since September 16, 2026 and has not yet moved to "In Review." Our public launch is scheduled for September 26, 2026 and has already been announced to our community, so we are hoping the review can begin before then. For transparency: we removed earlier submissions of 3.2.1 (September 6, September 14, and early September 16) to make changes to the build. We now understand this reset our place in the queue, and we will keep the current submission as is. We have also submitted an expedited review request 102973603518. Could the App Review team please check whether anything is needed from our side, or whether anything is holding the submission up? We are happy to provide any additional information. Thank you for your time and help. Jhenell Meneses VIIBYTE Corporation

Hi everyone, I'm posting here because I honestly don't know where else to get answers anymore. I've been trying to release my first app for about 2–3 months now, and the review process has been, frankly, a disaster for us. As a first-time publisher I've genuinely tried to do everything by the book — I've read the guidelines carefully, prepared reviewer notes, a demo account, sign-in instructions, everything that's recommended. But here's the pattern I keep running into: Every submission sits in "Waiting for Review" for around two weeks — currently even longer. I know the official expectation is that most apps are reviewed much faster, but that has never once been our experience. When the review finally happens, it stops at the first issue found. Instead of reviewing the whole app once and giving me a complete list of everything that needs fixing, I get exactly one rejection point, I fix it, resubmit — and then wait another two weeks just to learn about the next issue. If I got all findings in one pass, I could address everything in a single build. This one-issue-per-cycle loop is what turns a fixable week of work into months. Right now I've been waiting 2.5 weeks for a metadata-only change (updated store screenshots). No binary change at all. I've contacted App Review support to ask for a status update and have received no response. For context: the same app has been live on Google Play for several weeks and is doing well there. We're not trying to sneak anything past review — we want to comply. We just need to actually be told what to fix, ideally all at once, and to not lose two-plus weeks per iteration. So my questions: Is there any way to get a complete list of issues in one review pass instead of one rejection per cycle? Is a 2+ week "Waiting for Review" time normal right now, or is there something about our account/app that could be causing this? Is there any effective way to get a status update when support doesn't reply? (Expedited review requests haven't helped either.) I understand App Review has to handle enormous volume, and I'm not looking to bash anyone — but as a small developer, this process has been demoralizing. Any advice from people who've been through this, or any pointers from Apple folks who read here, would be hugely appreciated. Thanks.

Hi Apple App Review Team, I’m looking for some assistance regarding my recent app submission. I submitted the app for App Store review two days ago 24 Sep 2026, and it has remained in “Waiting for Review” status since the submission. It has not moved to “In Review” yet. I also submitted an Expedited Review Request, but I have not received any response or update regarding that request. The app is still showing the same “Waiting for Review” status. Additionally, I have separately submitted an Unlisted App Distribution request for the app. I have not received any email or status update regarding that request either. I understand that App Review timelines can vary depending on submission volume. However, according to Apple’s App Review information, the majority of apps are reviewed within 24 hours. It has now been around two days, and I haven't received any update on either the app review or the expedited review request. I have checked App Store Connect and confirmed that there are no outstanding actions or missing information on my side. The required information, including App Privacy, Export Compliance, Content Rights, and Age Rating, has been completed. Could someone from the Apple App Review team please check whether there is any issue or pending action associated with my submission? It would also be helpful to know whether the Unlisted App Distribution request has been received successfully, as I haven't received any confirmation email or update for that request. App: Jaunt - Experience Navigation App ID: 6765958646 App submitted for review: 24 Sep,2026 Current status: Waiting for Review Expedited Review Request: Submitted on 24 Sep,2026 I would greatly appreciate it if someone could check the status of these requests and let me know if anything is required from my side. Thank you for your time and support.

Hi everyone, I'm facing an issue with App Store Connect → App Store → iOS App Version → App Previews and Screenshots. I'm preparing my first iOS app submission and have uploaded screenshots for the iPhone 6.5" Display. I uploaded multiple screenshots successfully. Currently, 7 screenshots are uploaded successfully, but one additional screenshot became stuck in a processing state. The affected screenshot appears as a pink/white placeholder with a loading spinner and has remained in this state for more than 10–15 minutes. The problem is that I cannot remove the stuck screenshot. What I see The screenshot section shows approximately: iPhone 6.5" Display 7 of 10 Screenshots The problematic screenshot shows a loading/processing spinner There is no Delete (–) button Hovering over the screenshot does not show a delete option Delete All is also unavailable/greyed out while the screenshot is processing What I have already tried I have tried the following: Waited more than 10–15 minutes for processing to complete. Refreshed the App Store Connect page using Safari. Signed out of App Store Connect. Signed back in. Opened Media Manager / View All Sizes. Checked the iPhone 6.5" screenshot section in Media Manager. Tried hovering over the stuck screenshot to find the Delete (–) button. Unfortunately, the screenshot is still stuck and there is no delete option. Important detail The other screenshots are already uploaded successfully, so I don't want to use Delete All, as I don't want to remove the screenshots that are working correctly. The app version is still in: Prepare for Submission so the version should still be editable. Questions Has anyone experienced an App Store Connect screenshot getting permanently stuck in the processing/loading state? If so: Is there a way to force-remove the stuck screenshot? Is there a way to reset the screenshot/media processing state? Can Apple Support remove the stuck asset from the App Store Connect backend? Is there another Media Manager workflow that allows deleting an asset while it is still processing? Is there a recommended way to replace the stuck asset without deleting the other valid screenshots? I'm using Safari on macOS, and the issue persists even after signing out and signing back in. Any help or workaround would be greatly appreciated. Thanks!

My dating app has now been rejected by Apple under Guideline 4.3(b) for the fourth time. The reason given is that the App Store already contains enough apps in this category. I understand that Apple does not want duplicate or copycat apps. However, my app is not simply another dating app with a different name and design. The app has several core features specifically built around real-life dating: Real Date Score: Users receive a score based on completed real-life dates. This score is displayed on their profile and helps other users understand whether someone actually goes on dates and follows through. Real Date Planner: Users can plan real-life dates through the app. Group Dates: Users can organize dates with groups of up to 10 people. Group Chat: Up to 10 people can participate in a group conversation. Ghosting Protection: Users who repeatedly ghost after matching can be permanently banned. Mandatory Selfie Verification: Users must complete verification to use the platform. Singles & Couples: The app supports both individual and couple profiles. I have searched the App Store for an app that provides the same concept, particularly a dating profile that publicly displays a score based on completed real-life dates. I have not found one. If Apple considers this app substantially equivalent to existing apps under Guideline 4.3(b), I would like to know: Which existing App Store app provides these same core functionalities, particularly the Real Date Score and the system that permanently bans users for repeated ghosting? I am not claiming that no other dating app has any individual feature that overlaps with mine. Of course there are common dating-app features. The question is whether the overall product concept and core functionality are sufficiently different from existing apps to justify its presence on the App Store. This is not only unfair but also an anti-competitive approach. It is certainly not something befitting a giant like Apple. This is now the fourth 4.3(b) rejection, so I would appreciate clarification from developers who have encountered the same situation or from anyone familiar with how Apple evaluates this type of differentiation.

My app has been stuck in “Waiting for Review” for more than five days, without any progress or communication from App Review. Unfortunately, this is not the first time. Some submissions move forward within a few days, while others remain waiting for a week or longer with no explanation or meaningful status update. For developers running an actual business, this is extremely frustrating. App submissions are not simply experiments or hobby projects. Releases, customers, marketing plans, bug fixes, and business commitments can all depend on the review process. I fully understand that Apple needs sufficient time to properly review applications, but leaving a submission sitting at **“Waiting for Review” for an extended period without even beginning the review is difficult to justify—especially without any indication of the expected timeframe. Apple provides developers with strict guidelines, deadlines, and requirements, and developers are expected to comply with them. It is reasonable to expect a similar level of predictability and communication from the review process. Has anyone else recently experienced apps remaining in “Waiting for Review” for 5–7+ days? If so, how long did it eventually take before the review actually started? I would also appreciate clarification from Apple regarding whether these extended waiting times are currently considered normal or whether developers should contact App Review after a certain number of days.

HI, I'm the ceo of Yachtara.com. A boat and cruising navigation app for sailors and cruisers around the world. Yachtara launches publicly tomorrow, Saturday 26 September 2026, at 14:00 CET, on the web and Google Play. We have now been trying since 9 september after spending 3 months in dev/test environments to get our app accepted in Production. We have our global live tomorrow in 15 hours from now. We asked for a response, an expidited review and also have a support ticket open. Can anyone reply and review please ? We would love to not dissapoint all of our apple based users. The review was submitted on wednesday. The App ID is 6763736626 Thanks for your kindness CEO Yachtara.com

Hello, Our first submission was previously reviewed and we received feedback under Guideline 2.1 because the reviewer was unable to access the app due to a forced update issue. We fixed the issue completely, uploaded a new build, and resubmitted on Friday. The submission has now been in Waiting for Review for approximately 4–5 days with no further messages or requests. Could someone please confirm that the submission is correctly queued and that nothing else is required from our side? App: KIBAKI: Persian Community Submission ID: d1f921a3-9001-4ef2-a392-657860c437cd Current status: Waiting for Review Thank you.

Many years ago—back in the Windows 3.0 era and inspired by Michael Jackson’s then-popular "Black or White" music video—I wrote a harmless app that smoothly morphed one face into another. Now, in retirement, I ported the app to various platforms (including iOS) to stave off boredom and supplement my rather meager pension. Everything was going fine; the app received occasional updates without any issues. But yesterday, during a routine update, I received a shocking and terrible message from the App Store team. They claimed that the app or its metadata included content some users might find upsetting, offensive, or otherwise objectionable—meaning the app violated Section 1.1 of the App Review Guidelines. That section lists things I find absolutely horrifying, such as realistic depictions of people or animals being killed, sexual or pornographic material, and the like. In their verdict, the App Store team didn't bother to specify exactly what content was in violation or which specific rule it broke. This situation has left me depressed, wondering if I actually made a mistake and have been offending people with my app for over 30 years. Could anyone advise me on what to do? Apologies for the long-winded post, but this is a truly difficult situation for me. PS: Here is the link to the previous version of the app published on the App Store: https://apps.apple.com/app/face-video-morph-animator-hd/id1551050080

I’m developing a sandboxed macOS application intended for distribution through the Mac App Store. The app integrates with Claude Desktop using Anthropic’s official Desktop Extension format (.mcpb). Anthropic supports installing a Desktop Extension by opening the .mcpb file, after which Claude Desktop presents its own installation and user-consent UI. I’m trying to clarify one Mac App Store distribution point before we commit to the final onboarding flow. Would a Mac App Store application be permitted to: include its own pre-signed .mcpb Desktop Extension as a resource inside the application bundle; and after an explicit user action, open that bundled resource using standard macOS APIs so that Claude Desktop presents its installation dialog? The Mac App Store application would not: silently install software; modify Claude Desktop configuration; automate Claude Desktop’s UI; download or modify executable code after App Review; bypass Claude’s installation or tool-consent prompts. The .mcpb and the helper executable it contains would already be included and code signed before App Store submission. My question is specifically whether this would be considered using the Mac App Store app as an impermissible software-distribution mechanism, or whether this explicit handoff to another installed macOS application is acceptable. If bundling/opening the .mcpb is not acceptable, is there an Apple-recommended pattern for this kind of handoff to another installed application? I’m not asking for implementation help; the technical flow already works in development. I’m trying to qualify the Mac App Store distribution model before productizing the installation UX.

Hello App Review team, We resubmitted Tecnoaccess: notizie e giochi (Apple ID 6792506220), version 1.7, build 54, on September 22, 2026 at 13:45 UTC. As of September 25, the submission is still Waiting for Review. Our expedited review request was accepted on September 23. On September 24, we contacted Apple Developer Support about the review status and received an acknowledgement for case 102974478783. We have not yet received a response about the status of the submission. Could you please check whether the submission is queued for expedited review and whether any further information or action is needed from us? We would appreciate your help understanding whether anything is preventing the review from starting. Thank you, Alessandro Calabrò

Hello App Review Team, I’m following up regarding our latest submission, which is currently in Waiting for Review. We have addressed the issues identified in the previous review and submitted a new build with the necessary fixes. We also submitted an expedited review request because we are hoping to make the updated version available to our users as soon as possible. Could you please check the status of our submission and let us know if anything else is required from our side? Thank you very much for your time and consideration. Best regards, Ninja Rift Team

Hi there, Recently I've created a beautiful drink logging app, Abvy. You log what you drink and it shows an estimate and a possible range of the alcohol in your system over the evening. It has plenty of disclaimers that the measurements are only estimates and to never use them for driving decisions Since 26 August I've had the same rejection six times: "marketed as a blood alcohol content calculator but does not have associated hardware... apps that rely solely on software... are not appropriate." Meanwhile Beta App Review approved all the builds submitted. I had an App Review appointment today. The rep read the same paragraph back to me and said to appeal, which I've done. It was really frustrating. The published 1.4 doesn't mention blood alcohol at all, and university and public-health apps with the same kind of estimate are on the store today (Stay in the Blue from the University of Michigan, Virtual Bar from the Foundation for Advancing Alcohol Responsibility). Not to mention dozens of other, apps who do the exact same thing but are approved. Has anyone actually got past this on the App Store side? What changed for you? What can I do to fix this? Really care about Abvy and think it's an amazing app.

Hello, my app Bolzplatz – Fußball Manager (App ID: 6747684577) has not received any App Review approval since September 12. The current build has been stuck in “Waiting for Review” since Friday, September 18, despite an expedited review request. There are no messages or requests for additional information in App Store Connect. Could someone from the App Review team please check whether the submission is stuck in the review queue? Thank you very much.