Hi. After a few attempts to submit my game, it is still rejected with the following reason: Guideline 4.1 - Design - Copycats The submitted app is designed and developed 100% from the scratch, and I don't know the reason of the issue, as I can’t identify which part of the metadata is the issue. After sending a messages to moderation team asking to specify which exactly part of the metadata is the issue, and which other app do they mean, I’m still getting the same template reply, referring to the “Guideline 4.1 - Design - Copycats”. I have even updated the icon, believing that it was the reason of issue, but it was not a solution. Now I don’t really know what to do? Here is the full warning message: —————— “Guideline 4.1 - Design - Copycats This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform. Apps should be unique and should not attempt to deceive users into thinking they are downloading something they are not.” Next Steps Learn more about requirements to prevent apps from impersonating other apps or services in guideline 4.1. Revise the app to comply with these requirements. Once the app is fully compliant, resubmit the app for review. —————— Thanks.

I have implemented auto-renew subscription in my app and I have also tested it on physical device by implementing storekit. The subscription is bought successfully and is working fine. But when I add the app for review to appstore along with the subscription they reject it because they could not find the subscription in the app.

It's a brand new app that hasn't got its first approval yet. I am including IAP subscriptions with it and after each rejection, I am unable to clear the Developer Action Needed status of the Subscriptions and re-include in the binary for review. To clarify, after I created the Subscriptions I was able to include them in the binary, but after each rejection the Developer Action Needed status is not cleared, even though I edit the descriptions and save. If I update the Localization on each Subscription, they do change status to Prepare for Submission, but the Subscription itself remains on Developer Action Needed. I am having to create a new Subscription Group and Subscription with each rejection from the Review Team, because otherwise I cannot submit them with the binary for review. Can anyone shed some light here? It seems there's a ton of other topics with the same issue that suggest to edit a description, which would then update the status to Ready to Submit but no matter what I try, it won't clear the Developer Action Needed. Thank you

Hello, My company is developing an interactive story game (or a visual novel with multiple ongoing and updated stories). We've added a few unique features to add value to our proposal, but we have been rejected due to Design 4.3 (0) Spam two times now. When trying to get more information from the message from the App Review team, we're only getting what we believe are automated responses Here's the message to our first submission: Guideline 4.3(a) - Design - Spam We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality After the first rejection, we looked into the game and make substantial changes to the core interfaces and gameplay of the game. In particular, we modified the way users access the stories and introduced new added value by linking storylines to unique, unlockable and collectible outfits. We've also invested in voice over feature for the storylines, which we plan on expanding on in the future. With this new revision, we submitted the new bundle. This was the response: Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. it seems that our assumption was incorrect, and now we're puzzled. Is it the interactive story game market that is saturated? Are we not allowed to do visual novels on the App Store any longer? Is it something in our UX/UI that is triggering this rejection? We have no answers. Please note that the game has been fully and entirely developed by us, and there isn't any part of the game that has been stolen or duplicated. That includes, images, stories, audio, metadata, and, of course, the binary and source code. Does anyone have any insight or suggestion on how to proceed? We have tried to schedule a "One-on-one App Review consultation" with a specialist, but our requests have also been rejected. Any help or guidance will be immensely appreciated. Thank you all in advance.

Regarding Performance - Accurate Metadata i.e. Screenshots in Distribution/Product profile (Guideline 2.3.3): Our e-learning app has been rejected in App Review regarding compliance with Guideline 2.3.3 Performance - Accurate Metadata i.e. Screenshots in Distribution/Product profile. The following is our query: Our app is designed exclusively for iPhone users and will not be distributed for iPad devices. Is it mandatory to include iPad screenshots on the App Store, even if we do not have an iPad version? If not, why is the field requesting iPad App Store screenshots indicated as mandatory? Is this for marketing purposes only? The above query is based on the following instruction provided by the Apple Support/review team: Your iPad Pro (2nd Gen) and 13-inch iPad screenshots show an iPhone device frame scale. Upload new screenshots that accurately reflect the app in use on iPad. Some or all of the provided screenshots do not sufficiently show the app in use. Screenshots should highlight the app's core concept to help users understand the app’s functionality and value. Follow these requirements when adding or updating screenshots: Marketing or promotional materials that do not reflect the UI of the app are not appropriate for screenshots. The majority of the screenshots should highlight the app's main features and functionality. Confirm that the app looks and behaves identically in all languages and on all supported devices. Make sure that the screenshots show the app in use on the correct device, unless they are included to demonstrate that the app can be used on multiple Apple platforms. For example, iPhone screenshots should be taken on iPhone, not on iPad. Next Steps The iPad Pro (2nd Gen) and 13-inch iPad screenshots show an iPhone device frame. Upload new screenshots that accurately reflect the app in use on each of the supported devices. Looking forward to anyone's kind response that can help us resolve this issue. Thanks!

Regarding Account Deletion (Guideline 5.1.1(v)): Our e-learning app has been rejected in App Review regarding compliance with guideline 5.1.1 (v) Account Deletion. The following is our query: We are including a button that links to the account data deletion request page on our website. This will be placed on the Profile Tab/Page of the app. Will this be sufficient to meet Apple’s guidelines for data deletion requests? The above query is based on the following instruction provided by the Apple Support/review team: The app supports account creation but does not include an option to initiate account deletion. Apps that support account creation must also offer account deletion to give users more control of the data they've shared while using an app. Apps that support account creation must also offer account deletion to give users more control of the data they've shared while using an app. If users need to visit a website to finish deleting their account, include a link directly to the website page where they can complete the process. Follow these requirements when updating an app to support account deletion: Only offering to temporarily deactivate or disable an account is insufficient. If users need to visit a website to finish deleting their account, include a link directly to the website page where they can complete the process. Apps may include confirmation steps to prevent users from accidentally deleting their account. However, only apps in highly-regulated industries may require users to use customer service resources, such as making a phone call or sending an email, to complete account deletion. Next Steps: Update the app to support account deletion. If the app already supports account deletion, reply to App Review in App Store Connect and identify where to locate this feature. If the app is unable to offer account deletion or needs to provide additional customer service flows to facilitate and confirm account deletion, either because the app operates in a highly-regulated industry or for some other reason, reply to App Review in App Store Connect and provide additional information or documentation. For questions regarding legal obligations, check with legal counsel.

Our e-learning app has been rejected in App Review regarding compliance with guideline 4.8.0: Login Services. The following were Apple Support's feedback: The app uses a third-party login service like Google or Facebook, but does not appear to offer an equivalent login option with Sign in with Apple. Next Steps: Revise the app to offer an equivalent login option that meets all of the above requirements. If the app already includes a login option that meets the above requirements, reply to App Review in App Store Connect, identify which login option meets the requirements, and explain why it meets the requirements. Additionally, it would be appropriate to update the screenshots in the app's metadata to accurately reflect the revised app once another login service has been implemented. Note that Sign in with Apple meets the requirements specified in guideline 4.8. Now, regarding their instructions, the following are our queries: Our mobile app for iOS already has SSO login options for Google and Facebook. Could you clarify what is meant by "an equivalent login option"? Are there any specific third-party login services other than "Sign in with Apple" that already comply with the requirements in Guideline 4.8? We are using “Manual sign up/sign in”, “Continue with Google” and “Continue with Facebook” to let users sign up and sign in to our platform. As per the parameters involved with the third-party login, will using sign in with Apple solve the problem related to Guideline 4.8? So is it mandatory under Apple’s Guidelines to include "Sign in with Apple" now, in addition to other SSO options? If it is mandatory, how is it that many iOS apps do not include the "Sign in with Apple" option? From a technical perspective, what options are available to satisfy Apple’s guidelines in this regard? Could manual sign-in/sign-out features of the app cause any conflicts with compliance in this area? Looking forward to anyone's kind response that can help us resolve this issue. Thanks!

I want to publish an unlisted app for an enterprise audience and would like to know if the registration flow is required. Since my app will only have features that require log in Apple guidelines say it needs the registration process but to ensure that only desired users will have access I plan to create accounts from outside the app, thus making the registration within the app unnecessary. Is there any docs, guideline or policy that states that registration is not needed for unlisted apps?

Hello! I have been rejected around 3 times in a row (citing 2.3.3 (inaccurate metadata)) due to iPad screenshots that are not present in my submission. These screenshots are from a much earlier build and despite pointing this out directly this issue has persisted. I have removed all screenshots and submitted completely new ones twice. It appears that there must be a glitch or technical issue preventing the review team from seeing these updated screenshots. I am unsure of how to solve this as on my end this issue appears to be resolved. My next attempt will be to set up a call with a live reviewer in order to sort this out. Any advise would be appreciated! Thank you for your time!

Hi everyone, We’ve been trying to submit our game to the App Store for quite some time now, but we’ve encountered multiple rejections despite addressing all the feedback we’ve received. Initially, we resolved a few issues, such as providing in-game screenshots without UI elements, but there is one recurring problem that continues to block us. Every time, the review team reports an issue with the “Sign in with Apple” feature, specifically stating: “You have canceled the Sign-In With Apple process. You may try to log in again.” This error only occurs when a user actively cancels the login process. However, we’ve tested the feature on multiple devices, including iPads and iPhones, targeting all iOS versions from 17 and above. The login process works flawlessly in all our tests. We’ve ensured that we are following Apple’s best practices and have meticulously reviewed our implementation numerous times and also reviewed with another team which implemented it the same way and did got approved. It’s becoming frustrating as the issue appears to be on the review side. We’ve even uploaded videos demonstrating various scenarios: successful login, canceled login, auto-login, etc., yet we still receive no detailed feedback. Each review cycle takes about 24 hours, which is significantly delaying our iOS launch. (The game has already launched on Android without any issues.) Has anyone experienced a similar situation, where a working feature consistently fails during App Store review? If so, how did you resolve it? We’re quite behind schedule and would appreciate any advice. The "Sign in with Apple" library we use (lupidan): https://github.com/lupidan/apple-signin-unity The Game is made with Unity (6000.0.19f1) Built with Xcode 16. Thank You! ------- This is the reviewer notes ------- Guideline 2.1 - Performance - App Completeness Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you are unable to provide a demo account due to legal or security obligations, you may include a built-in demo mode in lieu of a demo account with prior approval by Apple. Ensure the demo mode exhibits your app’s full features and functionality. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems. Issue Description The app exhibited one or more bugs that would negatively impact App Store users. Bug description: we were unable to login via Sign in with Apple Steps to reproduce bug: Tap on Sign in with Apple Sign in with Apple Canceled error Review device details: Device type: iPhone 13 mini and iPad Air (5th generation) OS version: iOS 18.0 Next Steps Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review. If the bug cannot be reproduced, try the following: For new apps, uninstall all previous versions of the app from a device, then install and follow the steps to reproduce. For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.

Hello, I’m facing an issue with the subscriptions in my app during the review process. When I test the app in Xcode using a StoreKit configuration file, I can see and purchase the subscriptions without any problems. Testing with a Sandbox user in TestFlight also works fine – I can see and purchase the correct subscriptions. However, my app was rejected during the review because the reviewer said the "Try for Free" button wasn’t working. In the screenshot, I noticed that the subscriptions didn't load and it showed dummy data instead. This issue only seems to happen during the review. When I test the app in both TestFlight and the Xcode simulator, everything works perfectly. I can see the subscriptions, purchase them, and the app runs as expected. Could you please help me understand why this issue is happening during the review, even though everything works fine on my end? Also my banking information are ok and complete. Thank you very much!

Dear Apple Team, I have an issue that I would like the Apple Review Team to clarify: Context: We have an application released on both iOS and the web, offering paid services through a subscription model, currently using Apple’s In-App Purchase mechanism. However, due to technical limitations and users lacking the technical knowledge to resolve payment issues on their own, our customer support team is directing users to an external website of the application to complete payments. Is this approach compliant with Apple's guidelines? Thank you for your support. Best regards, LuckyP

Can you have a referral system in your app, where each user is assigned a code. And when another user uses the code, they get a reward from it? I don't have subscriptions in my app, and I only have in app purchases where a user can buy 1, 3 or 5 scans which are all consumable. So when another user uses someone else's code, I keep track of it and when there is 2 uses of that code, the user can get a free scan. I got feedback from Apple saying: Guideline 3.1.1 - Business - Payments - In-App Purchase The app unlocks or enables additional functionality with mechanisms other than in-app purchase, which is not appropriate. Specifically, the app uses Referral codes to unlock or enable Face scans. Next Steps It would be appropriate to remove these features from the app and any other feature that unlocks or enables functionality with mechanisms other than the App Store. Is there a way to make this work while adhering to the guidelines? Do I need to have it as a in-app currency? And that would be allowed?

Hello, we have encountered the Guideline 1.4.1 - Safety - Physical Harm, Guideline 2.3.3 - Performance - Accurate Metadata, etc., eveytime we try to upload or update any of our apps, which just takes temperature, blood pressure, glucose, weight and oximetry readings from external BLE gadgets, we receive the same reply, sometimes with less motives other with more. Also, the reviewers, keep requesting documentation for Certification of devices, approved by the FDA, EU and Brazil, and yet that is not enough for them. The "Reviewer" if there is really one, does not read or does not understand all the documentation we have provided as: FDA, EU (Europe) and Anvisa Clearances and Certifications. Letters from Hospital or medical institutions. Reduce the number of countries. Mentioning that the app might be used only for the Users or Patients associated with a particular Institution. Etc. Nothing is enough for Apple and its Reviewers, and every time they ask for something new or different, or a video, etc. Also, we have not found any where on any documentation that using an iPhone, iWatch or a MacBook, or any Apple's product, the User can not make a misguided decision and have a "Physical Harm 1.4.1", ahh, but if it is made by Apple and approved by its own reviewers then is is correct. We have spent a lot of time developing these Apps and Remote Patient Monitoring Systems, and it is nonsense that we have to strip down all features from our app, just to complied with the reviewers, and yet, there is no way to move forward. Our customers are just moving to other Platforms as the WebApps or any other distribution form without a Store, which forces developers to comply with non sense and endless requirements, and that the reviewers deny all documentations, certifications, documents, etc., provided, no end to the story, just time after just the same thing. Good luck to anybody trying to use and BLE gadget or device, and by the way, we already have just one app approved by apple named EmmitecWL1, trying to get Approval for EmmitecJD1, and even though they are basically the same, they are used by different medical institutions, and we have more than 10 other customers waiting for their apps on iOS, with no clear future. Ahh, almost forgot, this time we were submitting the app named Emmitec WL1, and the very expert and honest reviewer sent a lot of screen captures of an older app named EmmitecWL, so just what we could expect, they do not even pay attention of what they are doing, they do reject a newer app reviewing and old one. Thanks for your time.

Hey, I am trying to publish on appstore a game for the first time. The game was rejected by apple due to "Guideline 4.1 - Design - Copycats This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform." and no matter what, the reviewer is not clarifying or answering any questions, just more vague copy paste answers. Is this typical in apple ecosystem? is there any way of getting proper answers and specifics for why an app is rejected? maybe paying bribes for the correct guys?

Hi there, Im trying to submit an app but is rejected from apple gour guidelines 4.3(a) Design-Spam violation. Can someone help me with that please?

Hi, I made a macOS app that automatically sets the correct input/output devices depending on the connected speakers/microphones. The App is supposed to live in the background and act automatically, only allowing the users to change through settings which is accessible through the toolbar or through clicking on the toolbar icon to cycle between modes. However, my app was just rejected for not providing UI beyond this. Guideline 4 - Design "Menu items are not visible, except by right-clicking. Users should not have to right click to access menu items." I don't think that this app needs a UI beyond that for something which it is supposed to do automatically. I'm having a hard time to understand what's expected here, should I invent a UI to pass the review and give option to the user to disable that?

In my app, book club owners can charge users to join their clubs. My platform ( company ) takes an application fee, while the club owners receive a service fee from these transactions. I have one to many live discussions, in the future I will add sell ticket feature. Can I use Stripe for these B2B transactions, or am I required to process these through Apple IAP? If I am pushed to be use Apple IAP then how to split the user purchase between me and the club owners. Regards.

I’m encountering an issue during the Apple review process and was hoping someone might be able to help or offer some insights. My app uses RevenueCat to manage all subscription processes, including receipt validation. RevenueCat is supposed to automatically handle switching between production and sandbox environments. Everything is configured properly, and I’ve thoroughly tested the subscription flow on multiple devices, including both iPhone and iPad, with no issues. In the past two Apple app reviews, the subscription process was completed successfully, and I haven’t made any changes to the code or anything related to RevenueCat since then. I’ve also tested using the release build configuration, and everything works fine on my end. However, Apple has now reported an "Error 23" message, indicating a configuration issue during their latest review. Since everything works perfectly in my tests and passed previous reviews, I’m unsure what’s causing this issue now. Has anyone experienced something similar with RevenueCat or "Error 23"? Could it be a temporary sandbox environment issue? Any advice on how to troubleshoot this or fix the problem? Thanks in advance for any help!

I submitted an app for review and it was rejected. We've been in discussion with the review team for over a month now, going back and forth providing contracts, legal agreements, proof of security measures, etc. 3 weeks ago the app was rejected again citing the same reason as the initial rejection (lack of proof of partnership agreements), which we have provided proof of. I replied asking the reviewer to scroll back in the history as this issue was already addressed by the previous reviewer. They once again said that we needed to provide it. I replied again with another message containing all of the proof we have submitted to date, responses from legal teams, compliance teams, from partners themselves, etc I also opened an appeal with the apple review board, as this feature is identical to features in dozens of other apps listed in the store. And our partners confirmed everything was above board with what we are doing. After a week of no response I replied to the review asking if its possible to get an update, as the team funding the development of the app are becoming irate with the delays. Its now been 12 days since our last response. Is there any other avenue I can use to try get an update?