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.

Hi, I am trying to get an app approved. In app purchases say that I need to fix something without saying what needs fixing. I can't add the in-app purchases to the app review and that one does not pass because there are in-app purchases missing. How can I fix this issue? I assume that during review someone could just write whats missing but obviously they won't. The message I received said: One or more of your In-App Purchases has been returned for the following app: Literally nothing else. Regards,

Hello, I submitted an app update (submission ID: 3bbbd08f-6ca9-40a2-bdc1-a2f33061f647) that was rejected for Guideline 4.0 - Design (about ad frequency issues). The rejection message included this option: "The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know." I replied on December 11 at 10:21 PM asking to approve the current version as a bug fix, and that I would address the ad frequency in my next update. It's now been over 35 hours with no response. Should I resubmit my binary for review? Typically, when I reply to the App Review message in such a scenario, my app gets approved in a few hours.

Hi everyone, I’m looking for some help or clarification regarding repeated rejections under Guideline 3.1.3 - Business - Payments - Other Purchase Methods. In earlier versions of our app we did experiment with using in-app purchases for our eSIM-related service (which App Review treats as a physical good/service). After the first rejections, we fully reworked the payment flow. In the current build we have: Completely removed any use of the in-app purchase API / StoreKit and removed all UI elements and wording mention in-app purchases. Detached all in-app purchase products and marked all previously created IAP products as “removed from sale”, so they are no longer available to users. Moved all payments to an external outside of the in-app purchase API, which (as I understand it) is exactly what Guideline 3.1.3 requires for physical goods/services. Despite this, the app is still being rejected with the same 3.1.3 message about using in-app purchases for physical goods, without any new details or updated screenshots that point to the actual problem in the latest build. One thing that might be related: in App Store Connect there are still some legacy in-app purchase products stuck in an “In Review” state. We can’t delete or fully edit them from our side, even after removing the previous builds. They are not attached to the current version and are not referenced anywhere in the code or UI, but I’m worried they might still be confusing the review process. Has anyone run into a similar situation? Can these legacy IAP products in “In Review” status still trigger 3.1.3 rejections, even if they’re not attached to the binary and removed from sale? Is there any way to get App Review or Developer Support to reset or clear these products so we can fully remove them? We’re a small team trying to launch, and at this point we feel a bit stuck in a loop where the feedback doesn’t seem to reflect the current implementation. Thanks in advance for any help or insight.

Hello, I recently was rejected for the following reason: However, your app does not comply with: Legal 5.1.1 We noticed that your app requires users to register with personal information to access the app’s content and purchase in-app purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. To resolve this issue, please revise your app to not require users to register before purchasing in-app purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their iOS devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Resources See guideline 5.1.1(v) - Account Sign-In to learn more about our requirements for apps with account-based content and features. I replied: We require the user to login/sign up because it relates directly to the core functionality of our App. If the user deletes the App and chooses to reinstall it, his data will be saved on our server because the sign up system allows their data to be saved. This allows the User to restore all his in-app purchases and for our database to always keep track of the User’ in-app purchased consumable items. Apple requires a restore feature for in app purchases and we allow the user to restore his in app purchases by tying their account to an email or social media login. The login is required to prevent users from hacking the app. The diamond and coin systems are stored on our back end database servers. Once a user logins in, the back end stores how much coins and diamonds are associated with that account. This prevents users from manually altering how many coins or diamonds they have. It preserves the integrity of the app and the Apple App Store itself. Our servers store all user progression and data. Without the login / sign up system, we cannot sync the back end database. The login / sign up feature is crucial to the functionality of the app to prevent hacking and to keep track of the users database and more importantly, keep account and restore capabilities available for any in app purchases. To which the review board responded with: Although requesting that users register to for tracking users’ purchases and game progresses is acceptable, requiring users to fully register for an account before entering the game is not. Users should be allowed to access none account-based features before registration and login. You may also choose to alert users that accessing game without binding an account may result in losing game progress or in-app purchase items. To resolve this issue, please revise your app to let users freely access your app’s non account-based features, such as accessing the game, prior to registration or login. Once the user decides to use account-based features, the app may present the registration or login feature at that time. My understanding is this... I need to implement a "play as guest" mode where Users do not need to register. This will automatically generate an account for that User. However, am I allowed to require the user to register before conducting any in-app purchases, or other activities on the app?? What is this asking for? Do I need to allow the guest user to be able to purchase and do all the things a registered user can?

My app has been waiting for review for over 7 days. I know it's nearing the holidays but at most I think it should take 5d. Should I maybe developer reject my app and resubmit it? I have already tried expedited review.

Hi there. I work for a company that develops a SaaS service. Users have to register before using the SaaS as all the data they save in the application must be linked to their account. Why that? Because it is a multi-platform SaaS currently running on web and Android, so, the user must have access to his/her contents on every platform he/she intends to use. Also, some features depend on our back-end system to process the data and return an analysis based on them. That said, Apple is rejecting our app claiming that we should not require the user to register an account before purchasing a subscription. The problem is: how can the user store their data in our servers without an account? We do offer a free tier account, but the users must be logged in to have access to their data and have the analysis performed by the back-end service. Does anybody have gone through a similar issue? I need clarifications on how to solve this. Thanks in advance.

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

Hi Apple Staff / App Review Team, We’re following up because we haven’t received a substantive reply to our previous forum post or our messages in App Store Connect. Context (unchanged): Our last update focused on performance/stability, bug fixes, and numeric balance tuning (difficulty/rewards). We also added a small, user-initiated News panel (globe icon in the main menu) that displays one static announcement image and can be closed at any time. There are no links, no navigation, no login/UGC/ads, and no executable content in that panel. We don’t collect personal data (no IDFA/ATT). Safeguards already in place: Post-release changes are restricted to numeric balance values only (no feature toggles, no navigation changes). The announcement is strictly read-only (one static asset from our own domain) with an offline fallback. Internal release policy forbids any post-review feature switches or concept changes. What we’re asking for: Specific guidance on what observation(s) led to the 3.2(f) determination. Whether a resubmission under the constraints above is acceptable (we can tighten further if preferred). We’re ready to provide any materials immediately and submit a new build as soon as we receive direction. Thank you for your help—could you please escalate or advise on next steps?

Hi everyone, We just received another App Store rejection under Guideline 3.1.3 - Business - Payments - Other Purchase Methods, stating that we are using in-app purchases to sell physical goods — specifically, a physical QR code sent to the user. However, in our latest build, this issue was already addressed: All physical QR code purchases are now handled entirely through Stripe Checkout, outside of the app. No consumable IAPs are used for physical goods. The purchase flow is completely optional - users can tap “Continue” to skip it and still use the app without ever engaging with Stripe or purchasing anything physical. We’re a small team trying to launch and are stuck in a loop where it seems like the rejection feedback might not reflect the latest build with not clear feedback from Apple. Has anyone experienced something similar? Would really appreciate any guidance or insight — or if anyone from Apple is here, we’re happy to jump on a call to clarify. Thanks in advance!

Hello, I submitted a small update to my app two days ago, and the update got rejected early yesterday because of a small issue in the metadata. I promptly fixed the issue and replied to app review saying so. It has now been a little less than a day since then, and the update still hasn't gotten processed. Ordinarily, I wouldn't be in such a rush, but I have a really important app-related event tomorrow. Is there anything else I have to do for the update, or is it good to go now that I've fixed the metadata?

Hello, I need clarification about the correct and allowed way to use Stripe inside my mobile app for subscription purchases. My mobile app is for real estate agents. An agent can create an account and gets unlimited property uploads for the first 3 months. After 3 months, they must choose a subscription plan: Basic Plan: 3 property uploads per month Premium Plan: 15 property uploads per month The same agent can also log in on my website, where I am using Stripe to handle subscription payments. From the website, they can upgrade or downgrade their subscription. Now the main question: I want the agent to be able to upgrade their subscription directly from the mobile app as well, using Stripe. What is the allowed and compliant method to let the user purchase or manage their subscription inside the mobile app, considering that Stripe is used on my website? Specifically: Can I open a Stripe Checkout page in a WebView? Or must I open it in the device’s external browser (Safari)? Or does Apple require a different approach? Is there any officially allowed workaround so that I can safely use Stripe in the mobile app for subscription updates without risking App Store rejection? I simply want to follow the guidelines correctly and avoid any issues during review. Thank you

Hello, I’m preparing a macOS app for App Store submission, and I have a question regarding whether including an extra executable inside the app bundle is permitted under the App Store Review Guidelines. My app would include a command-line tool placed inside the bundle, such as: MyApp.app/Contents/MacOS/ or MyApp.app/Contents/Resources/ The purpose of this tool is to help users collect hardware/system information for troubleshooting or error reporting. Importantly: The app never launches this executable automatically. It never runs in the background. It is intended to run only when the user chooses to run it manually. The intended workflow is: The executable is shipped inside the app bundle. When needed, the app simply informs the user where the tool is located. The user manually executes it—either by double-clicking in Finder or by running it from Terminal. The executable runs independently, and the app does not trigger, spawn, or control the process. My questions are: Is this approach allowed under the macOS App Store Review Guidelines? Could this be considered “executing external code,” a sandbox violation, or otherwise lead to rejection during App Review? Does App Review allow a tool that is bundled with the app but executed manually by the user outside of the app itself? Additionally, if there is any official documentation or guideline from Apple that specifically addresses this scenario—or similar restrictions around including executables inside a macOS App Store app bundle—I would greatly appreciate a link. If anyone has experience with this or knows how App Review typically handles this type of setup, I’d be grateful for any insight. Thank you!

Dear Reviewers/Apple Team/Community, We have trying to submit our app continuously for review and being rejected continuously by Apple. Our app works perfectly fine in TestFlight using the same ID apple is using. We have also provided recorded video of the testing in TestFlight to Apple reviewer. However, despite our requests below things are not done: Before testing the in-app purchase subscription are not being approved, despite us requesting the same every time during submissions. At times we are getting snapshots under error category, where everything is correct even from Apple testing. We have no other way but to explain, give snapshots, give videos to Apple to help them understand how to test the app. We have requested the reviewers multiple times for a call, but we got a call only 1 time. We are not sure what is the way we can get to talk with the reviewer and understand from them the issue they are facing. Can anyone please help us out? Below is one example, it was given it us under error category, where even with apple standard, the purchase is successful. Can someone help us out plz.

In iOS 26.2, PermissionKit allows apps to request parental consent when a minor attempts to initiate a chat function. I believe this feature would be extremely useful when a minor tries to access other features in an application. For instance, in a real-time streaming service, when a minor attempts to access certain content, I would like to require parental permission. Is it acceptable to use the currently provided PermissionKit to send a request to the parent in this scenario? I am considering providing arbitrary values or nil for the action and PersonInformation parameters in this case. I would appreciate it if a fellow developer or an Apple staff member could confirm the intended scope of PermissionKit and if this kind of non-chat-related use case is permissible.

A month ago, a company filed a false complaint against one of my apps. I contacted Apple and informed them that this was untrue, uploading videos and screenshots proving that my account and apps comply with Apple's policies and that the complaint was baseless. Despite this, I was surprised to find all my apps deleted and my account flagged for deletion in the following days. What should I do? I've been wronged, and I've submitted numerous complaints and contacted technical support by phone and email, but so far, I haven't received any response or attention.

Hello! I added a subscription that has been in "In Review" status for five weeks. During this time, I've released two approved updates to my app.

It's been a week waiting for the review Despite requesting a quick review and contacting technical support via email, there has been no change so far. What can I do? Apple ID: 6756184295

Hi everyone, I am really not sure where else to go for a piece of mind because our recent review experience has been far from clear (and probably fair). We are a photo editing app developers who deal with AI models, effects and transformations on a constant basis. I believe last year we (like many other apps in the category) introduced effects that get two people in different photos and unite them in one cute/fun/cozy/emotional picture. Be it a couple, a mother and daughter - you name it. Of course all the templates are pre-set, there is no option for users to generate any scene by text-to-image or image-to-image model. Otherwise it would be unsafe. When submitting our app to review in May, 2025 we first faced the situation that this kind of effects are not welcome because of: Guideline 1.1 - Safety - Objectionable Content The app references or includes features that some users may find objectionable or could be used to create objectionable content. Specifically: The app includes templates for generating content showing people making intimate contact with each other, such as hugging, kissing, or other intimate templates. While these templates alone may not be objectionable, they could be used to create objectionable content. Apps on the App Store should be safe, appropriate for a general audience, and should not include features that are objectionable or could be used to create objectionable content. At that first time we saw it as new general requirement and rule and complied. It took us about a month to delete the "objectionable" content and finally get approved. Time passed and what we saw in the middle of summer was ALL the huge players in the market kept providing these "objectionable content" freely, both inside apps and as store graphics. So we re-added the content, submitted, and get approved like immediately. Was it a miracle or a matter of a particular reviewer, I cannot say, however after that we didn't get any reject for months. Then around October we submitted our app for another review and history repeated itself - same reject as in May for the same reason. Nothing helps us to get through. Nothing. 5-6 appeals about the review and 1-2 about unfair treatment, no response. Did I mention that all the huge players (like 5-6 apps) keep posting the same content freely? All of them released updates for Christmas last week with Group Photos / Shared shots / Photobooth Lab featuring exactly the same 1+1=united pic concept. Our latest appeal gets reply however, all the same: We understand your position and consideration of your app's compliance with Guideline 1.1. However, we found that the app references or includes features that some users may find objectionable or could be used to create objectionable content. The app includes templates for generating content showing people making intimate contact with each other, such as hugging, kissing, or other intimate templates. While these templates alone may not be objectionable, they could be used to create objectionable content. The strange thing is the screenshot attached wasn't even connected to the case itself, it was of a filter that was applied to photo that already contained two people. I don't see any logic in the responses any more: Not only the Guideline 1.1 - Safety - Objectionable Content quotes anything about the mentioned reasons for rejection. We have carefully reviewed the entire text of Guideline 1.1, including sections 1.1.1 through 1.1.7, and we are still unable to determine which specific part of the guideline the rejected templates violate. The note states that our “couple effects” (hugging, close poses, romantic themes) could be used to create objectionable content. However, when mapped against the text of Guideline 1.1, none of the listed categories appear to apply: The effects are not defamatory, discriminatory, or mean-spirited (1.1.1) They do not depict violence, harm, or abuse (1.1.2) They do not involve weapons or illegal activity (1.1.3) They do not contain sexual or pornographic material, nor explicit activity (1.1.4) They do not involve inflammatory religious commentary (1.1.5) They do not supply false information or trick functionality (1.1.6) They do not capitalize on harmful current events (1.1.7) And so on. As reply for our "Why other apps are allowed to have this content while we don't?" they returned with this: On occasion, there may be apps on the App Store that don't appear to be in compliance with the App Store Review Guidelines. We work hard to ensure that the apps on the App Store are in compliance, and we try to identify any apps currently on the App Store that may not be. It takes time to identify these occurrences, but another app being out of compliance is not a reason for your app to be. It has been 6 months since our first instance on the matter. None of the competitors removed such content from their apps while we are constantly being forced to do so. Does this imply them having another review experience? Or do they hide the mentioned features before review and get them back right after? It's a mystery... I will really appreciate any advice on how we should deal with this matter. Thank you in advance

Hi everyone, I’m currently stuck with repeated App Store rejections under Guideline 3.1.2 (Subscriptions) and I honestly don’t know what else I can change. Apple keeps stating that the Privacy Policy link and Terms of Use (EULA) are missing from the app metadata. However, to the best of my knowledge, everything is already in place: The Privacy Policy link is: ✅ added in the Privacy Policy field in App Store Connect ✅ shown on the paywall ✅ accessible inside the app ✅ included in the app description The Terms of Use (Apple Standard EULA) are: ✅ linked in the app description ✅ shown on the paywall ✅ accessible inside the app This setup has been in place for multiple submissions, yet the app continues to be rejected with the same message saying these links are missing. At this point, I’m unsure: whether Apple expects the links in a very specific field or screen whether the reviewer is checking a different location or if I’m misunderstanding where exactly Apple requires these links to be present Has anyone experienced something similar or knows the exact place Apple checks for Privacy Policy and EULA links for auto-renewable subscriptions? Any clarification would be greatly appreciated, as I’m currently completely stuck. Thanks in advance!

Hi all, It has been >30 days since my app was removed, and I was served with the pending account termination notice. Similar to others, I was flagged for section 3.2(f). Submitted an appeal, explicitly addressing every possible violation, offered to show source code with entire history, and also have all the email threads of me providing customer support to my users, and also multiple 5 star reviews. However, I was met with the rejection and the confirmation that the account would be terminated. Fast forward more than 30 days, my account is still here, but no closure or clarification at all regarding what I can do moving forward. Understandably, the team deals with millions of submissions and apps, but isn’t it reasonable (given that we pay $100/yr) to at least get some clarification on what went wrong? Currently, all I want to know is, Can I create a new account and develop other apps? Or will I risk getting banned again, hence wasting another $100? If I am able to proceed, what do I need to do to make sure my app doesn’t get randomly terminated again? Why aren’t there any signs or warnings? If anyone is able to assist me on this, I would greatly appreciate it. Thank you so much!