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.

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hello, I am looking for a better understanding of Guideline 1.4.2, which states that "Drug dosage calculators" must be developed by drug manufacturers, hospitals, universities, or other approved entities. My main question is: What is Apple’s exact definition of a "Drug Dosage Calculator"? - Does the term exclusively refer to apps that calculate dosage (dose, interval, and treatment duration)? - Are apps that do not make clinical decisions, but only display bibliographic references based on user-entered data, also considered Drug Dosage Calculators? - If an app only performs basic mathematical operations on a dose value entered by the user, without suggesting medications or treatments, does it still fall under this restriction? I would like to better understand how Apple differentiates a medical support app (which only presents data) from a dosage calculator (which makes clinical decisions). I appreciate any insights from the community!

Details: I'm looking for clarification on how Guideline 1.4.3 is applied to tobacco related apps. My app, The Leaf Cellar, was rejected under 1.4.3 with the reasoning that its "current concept is not appropriate" because it relates to tobacco. The app is a private inventory manager. It has no store, no purchasing, no vendor or affiliate links, no discovery feed, and no content directed at encouraging or using tobacco. its only function is personal record-keeping (logging inventory you already own, aging dates, humidity readings). A 21+ age gate is enforced on launch. What I'm trying to understand is the consistency of the guideline, because functionally identical apps are currently live on the store and receiving updates (which means apple must approve the submitted updates.) Existing Apps (not being enforced by 1.4.3): "My Humidor – Cigar Journal": [https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700] "Humidor Journal Pro": [https://apps.apple.com/us/app/humidor-journal-pro/id6751737114] Questions: Is there a specific feature or distinction that separates an approvable cigar-journal app from one rejected under 1.4.3 as a "concept"? If apps in this category are already approved, what's the correct path to have an inconsistent rejection reviewed beyond the standard Resolution Center reply? I have already submitted to the App Review Board.

Waiting for review - waited for 5 days, decided to resubmit, now waited for another 3 days, it says it takes up to 48 hours

Hello, My app has been stuck in the review pipeline for nearly one month, which seems very unusual to me App ID: 6767853355
 Bundle ID: com.ttm.photocleaner
 Timeline: Submitted, waiting for review: May 28, 2026
 In Review: since June 9

 I also submitted a support request via the Contact Us form on June 15 but have not received any response. 
Could you please verify if this submission is correctly queued or if there is an internal issue blocking the review ?
 Thank you

Hello everyone, I am facing a severe issue with my app's review process and urgently need some guidance or advice on how to resolve this bottleneck. Current Situation: Our latest version has been stuck in the "Waiting for Review" status for the past 10 days. Yesterday, after reading some community advice, I used "Cancel Submission" and re-submitted the build to try and refresh the queue. Unfortunately, it is still completely stuck in the exact same "Waiting for Review" status with no progress. Past History: This seems to be an ongoing issue with our account. For our previous versions, the App Review team took an incredibly long time—between 1 to 1.5 months for each submission—only to ultimately issue a rejection. We have already tried sending 5-6 standard support requests and even requested an expedited review 3 times, but we have received absolutely zero response or feedback from Apple. It feels like our app or account is stuck in some sort of dead-end queue. Has anyone else experienced such extreme delays just waiting for the review to start? Is there any alternative way to escalate this to a human specialist at Apple who can check if there's an account-level glitch? App Store URL: https://apps.apple.com/uz/app/fonus-kids/id6742020368 Thank you in advance for any insights or help!

Hello, My app JiuGO (App ID: 6779938845) has been stuck in "Ready for Distribution" status since June 22, 2026. I had set an automatic release scheduled for June 22 at 5:00 PM GMT, but the app has not appeared on the App Store after 3 days. Steps I have already taken: Opened 2 support tickets (Case ID: 102922525686) - no response Called Apple Support - was told to wait due to a conference Posted on Twitter @AppleSupport - no response Tried to manually release - button is not available/greyed out The app was fully approved after review. All previous issues were resolved. Build 17 is the approved build. Is there anything I can do to manually trigger the release, or can an Apple engineer escalate this internally? Thank you, Lucian-Stefan Lacatus

Hello, I submitted my first app (MYSKN, Apple ID 6773428050) on June 13th. It moved to "In Review" around June 16th and has been stuck there ever since — now over 9 days with no feedback or status change. I have also submitted two support requests through the "Contact the App Review Team" form and have not received any response to either. The app includes a fully functional demo account, Privacy Policy, and all required metadata. Is this normal for a first submission? Has anyone experienced something similar? Any advice on how to get a response would be greatly appreciated. Thank you.

When I was updating the application for release, it was rejected by the Apple 4.3a review team. This update only addressed some crash issues. Our application will only be distributed in specific countries. Our content is protected by copyright and will not appear in other apps; it is unique. id6777977649

My app has been stuck in "waiting for review" for over 2 days now. The previous time it was stuck for a few weeks until I posted here for someone to review it. Can somebody please take a look at my app and review it.

What is the current waiting time for the Review team to submit a app that is in the "waiting for review" status

Hello, What are the restrictions on submitting apps to the mac App Store that use an NETransparentProxy alongside a locally installed and trusted Root-CA to intercept, decrypt and manipulate TLS traffic? To be more specific, I'm not talking about a Safari extension. I'm talking about system-wide traffic. So that the app can detect and block ads and trackers from all apps, not just Safari. I'm aware that such an app can be distributed using an unsandboxed Developer-ID signed app. But I wonder if such an app also breaks Sandbox requirements for AppStore distributed apps? Also, is there a way for a sandboxed app to install and trust a root CA? SecTrustSettingsSetTrustSettings does not work in Sandboxed apps from what I found. Finally, I want to ask about EndpointSecurity. Can this entitlement be used in AppStore-ditributed apps? Is doing any of these things possible on AppStore-distributed apps? Thanks in advance for your reply.

We've got our first app developed currently stuck in a loop with AppStore Review. And we are getting no where. After no shows from calls with the team someone finally got back to me but after they had the team really try we have made no progress. We have subscriptions to use the app and then a further subscription to turn on a local web server. We have been able to purchase both (in each of their modes, monthly,annually, annually-monthly, outright) via test flight THOUSANDS of times. App Store Review have never been able to see the purchases. They keep sending general 'you need to turn on StoreKit' 'you need to configure AppStore API' But I dont think that we do? Its very strange that we can ue the IAP's perfectly but when we submit they cannot be seen. We keep going through this cycle: Create IAPS. set them up in our app Test them locally (using sandbox from Xcode) Deploy via test flight to other machines. Do in app purchases absolutely no problem. Submit binary+add IAPS (this sets them into awaiting or pending review) Get rejected due to IAP's not being configured. We get pointed to the same resource over and over and they say 'configure StoreKit' Well how can store kit not be configured and in app purchases work in the TestFlight sandbox? We see many reports on places saying 'I submit my app and they cant review it I create the same again and the 5th time it works' I spoke on the phone with someone from apple who said she had the engineers try multiple times and they just get the attached image saying 'currently unavailable', weve never seen this, we cant reproduce it and it doesnt seem to be anything we have control over. I guess the question is what is the difference between the 'sandbox' we use and the sandbox reviewers use? I cant see anything about any differences and we have no idea what we possible could have missed.

Several people I know that have tried posting ratings and reviews on my apps have not been able to successuflly submit their reviews. They took the time to write up a meaningful review, and their reviews have evaporated into thin air. The two apps are: SnapSpots: https://apps.apple.com/us/app/snapspots-save-your-spots/id6781947475 SMPLNVST: https://apps.apple.com/us/app/smplnvst/id6776138290

Hi everyone, I'm hoping someone from Apple or a senior community member can help escalate my situation. About four weeks ago, I received a termination warning on my developer account related to an app called Checklist Buddy (originally named Cessna Checklist Buddy). I renamed it after realizing I didn't have formal written permission from Textron Aviation, even though I had verbal approval. I believe that name change — or possibly code similarity between apps — may have triggered a flag. I have three apps on the store: WIB 26, Checklist Buddy, and Pure International 2026. WIB 26 is live and functioning fine. Pure International 2026 is the critical one — it's an event app for a pageant happening next week and delegates are counting on it. I have submitted multiple appeals and tickets over the past four weeks with zero acknowledgment from Apple. Last week I called Apple Support and spoke with a representative. He pulled up my account and confirmed there were notes showing an appeal on file, but no reason whatsoever was documented for the termination warning — even he couldn't see why. He escalated my case to a senior advisor and told me I would hear back within 3 business days. It has now been 7 days with no contact. I understand Apple has a high volume of cases, but this is affecting my livelihood. I have a real event with real attendees next week who need this app, and I cannot distribute it or push updates because my account is in a restricted state pending this appeal. If any Apple staff reads this — my case has been escalated to the senior advisor team and is sitting in an email queue. I just need a resolution or at minimum a reason for the original warning so I can address it properly. Any advice or help from the community is also appreciated. Thank you.

I'm a solo developer rejected 2 tiems times under Guideline 4.3(a). I've appealed and revised, but keep getting the same result. My app is nonogram puzzle game with various theme and multi color logic. Key facts: First and only developer account, with another app already live and approved on it — so this isn't account association. A multi-color nonogram/picross puzzle game, hand-coded from scratch in Cocos Creator (TypeScript). No app template, no third-party ad/analytics/mediation SDKs, no shared source code. 1,100+ original solver-verified puzzles, custom multi-color engine. I've already revised all metadata, removed a placeholder feature, and tightened the build. Still rejected. Questions: Since my account is not associated with other account, is this truly design issue or because there are many nonogram apps on app store? if it's design issue. the match usually on shared assets (art/audio from a common pack), the binary, or the concept/metadata — and how do I tell which? Can I get App Review to name the specific app/element mine is compared to, so I can fix it directly? Best channel for a genuinely original app in a saturated genre — Resolution Center, App Review Board appeal, or a phone call? i kept getting same answers

Hello, My app (Gezo Gündem, a Turkish news app) has been rejected twice under Guideline 4.2.2 (Minimum Functionality), both times with the same generic template: "the app only includes links, images, or content aggregated from the Internet with limited or no native functionality." For the second submission, I provided detailed App Review Notes listing 8 distinct native iOS features with step-by-step testing instructions for each: A native AI summary modal with native favoriting A native theming engine (5 modes) + dynamic "Club Mode" theming via native state management Native offline article storage using the device's file system (fully functional in airplane mode) A native Text-to-Speech engine reading article content aloud Native push notifications when followed authors publish new content A native source/favorites aggregation dashboard A native pinch-to-zoom newspaper cover gallery WebView is used only to render the body text of individual articles — nothing else in the app relies on it. Despite this, the second rejection used the exact same template language, with no reference to any of the listed features. I've since replied via Resolution Center asking the reviewer to re-test following the specific steps in the notes, but I'm unsure if this is the right channel to get a reviewer to actually engage with documented native functionality rather than reissue a template rejection. Has anyone successfully gotten a reviewer to revisit a 4.2.2 rejection by providing this level of detail? Is there a more effective way to ensure the review notes are actually read before a decision is made? Any guidance would be appreciated. Thanks.

Hi there, Our app 6757310595 has multiple IAP's that are all stuck in "waiting for review" since February 9th. I can't release our app as I can't attach the IAP's to the build when they are in this state. Please could you investigate, Thanks.

I am experiencing a critical and frustrating delay with an internal business application review. I would highly appreciate any insights or advice from the community or the Apple team on how to move forward, as our business operations are heavily impacted. Here is the exact timeline of our submission process: May 14 & May 19: Submitted the initial builds. On both occasions, the app transitioned to In Review within 4 hours but was rejected due to specific metadata/compliance deficiencies. Resolution: We thoroughly addressed all the points mentioned in the rejection notes, completed the missing requirements, and prepared a fully compliant build. May 22: Resubmitted the corrected build. Unlike the previous quick turnarounds, the app became completely stuck in the queue (Waiting for Review) with zero communication or updates for over a week. June 1: Out of concern that the submission was caught in a system glitch, I canceled the review and resubmitted it. It is currently still waiting with no status change. Expedited Review: I submitted an Expedited Review request detailing our urgent operational needs, but we have received no response or acknowledgment yet. Business Impact & Context: This is an essential internal tool for our business operations. We currently have 20 employees utilizing it via Ad Hoc distribution, but we are actively onboarding new personnel who need immediate access to the app to perform their daily duties. The limitations and manual management of Ad Hoc distribution are now causing a severe bottleneck in our daily workflows. Given that the first two reviews started within hours, it feels like the app has been flagged or placed into a different administrative review queue after the rejections, but the complete silence is hurting our business. Has anyone dealt with a similar sudden freeze after fixing rejection points? Are there any alternative communication channels available when both App Store Connect and Expedited Review forms go completely unanswered? Thank you in advance for your time and help.

Hello, We are seeking guidance regarding our developer account, which is under a Pending Termination Notice under Section 3.2(f). We deeply respect the App Store Review Guidelines and the standards Apple sets to keep the ecosystem safe and trustworthy. We take these rules seriously and submitted an appeal to the App Review Board and, following our correspondence on May 29, provided a full set of additional corrective actions to address the issues identified and bring our products into full compliance — including a mandatory internal compliance process to ensure we meet Apple's standards going forward. It has now been about two weeks, and we have not yet received a response on these latest materials. We have an 8-year history as an Apple Developer Program member, and we want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Reference details: Case ID: 102900026351 Appeal Ticket: APL444296