Hello everyone, I’m looking for some advice or shared experiences regarding an app rejection under App Store Review Guideline 4.3(b) – Design – Spam. Our app was rejected and, after an appeal to the App Review Board, Apple maintained that the app “duplicates the content and functionality of similar apps in a saturated category.” We strongly disagree with this classification and are struggling to understand how Guideline 4.3(b) has been applied in our case. The app was developed as an original product: Custom-designed content (including original cards and interactions) A unique visual style and UI A distinct interaction flow focused on encouraging social interaction between users This was not a template-based or reskinned app, nor is it part of a series of similar submissions. We fully respect the App Store Review Guidelines and are open to making adjustments to better align with them. However, what we find difficult is the lack of specific, actionable feedback. We have not received clear guidance on which exact elements are considered duplicative or what changes would meaningfully address the concern. Some of the questions we are hoping the community can help with: In your experience, what typically triggers a 4.3(b) rejection in cases like this? Are there specific mechanics, terminology, or presentation choices that reviewers often interpret as problematic? Have others successfully resolved a 4.3(b) rejection without completely abandoning their app concept? We have already invested significant time and resources into this project, and being advised to create an entirely new app is not financially feasible for us. We are genuinely trying to understand how to proceed in a way that is constructive and compliant. Any insights, experiences, or advice would be greatly appreciated. Thank you in advance. — Lars

Hi everyone, We’re looking for advice regarding an App Store review rejection and would really appreciate insights from developers with similar experience. Our app is a retro game emulator platform. It provides emulator functionality only (e.g. NES / GB / GBA emulation) and does NOT include, bundle, or download any game ROMs. Key points about our app design: ❌ No ROMs are bundled or distributed ❌ No in-app ROM downloads ✅ Users can only import their own ROM files that they legally own (e.g. personal backups) ✅ No copyrighted game names, box art, screenshots, or branding are used ✅ The app is positioned as a general-purpose emulator tool, similar to a media player that plays user-provided files However, during review we received the following rejection: The app appears to contain copyrighted video game files. Apps and their content should not infringe upon the rights of another party… We’re confused about what might have triggered this decision and would appreciate guidance on: On what basis Apple may conclude that the app “contains” copyrighted game files? Could this be related to: App screenshots or preview videos? Default demo flows or UI text? The emulator functionality itself? What changes are typically required to pass review, such as: Adding stronger legal disclaimers Requiring user confirmation that imported ROMs are legally owned Removing any potentially misleading UI wording Explicitly clarifying ROM ownership responsibility We’ve noticed that similar emulator apps already exist on the App Store, so we’re trying to understand: Whether there is a clear compliance path What modifications have worked for other developers in similar cases Thanks a lot in advance for any advice or shared experience 🙏 Happy to provide more details if needed.

Hi everyone, We’re looking for advice regarding an App Store review rejection and would really appreciate insights from developers with similar experience. Our app is a retro game emulator platform. It provides emulator functionality only (e.g. NES / GB / GBA emulation) and does NOT include, bundle, or download any game ROMs. Key points about our app design: ❌ No ROMs are bundled or distributed ❌ No in-app ROM downloads ✅ Users can only import their own ROM files that they legally own (e.g. personal backups) ✅ No copyrighted game names, box art, screenshots, or branding are used ✅ The app is positioned as a general-purpose emulator tool, similar to a media player that plays user-provided files However, during review we received the following rejection: The app appears to contain copyrighted video game files. Apps and their content should not infringe upon the rights of another party… We’re confused about what might have triggered this decision and would appreciate guidance on: On what basis Apple may conclude that the app “contains” copyrighted game files? Could this be related to: App screenshots or preview videos? Default demo flows or UI text? The emulator functionality itself? What changes are typically required to pass review, such as: Adding stronger legal disclaimers Requiring user confirmation that imported ROMs are legally owned Removing any potentially misleading UI wording Explicitly clarifying ROM ownership responsibility We’ve noticed that similar emulator apps already exist on the App Store, so we’re trying to understand: Whether there is a clear compliance path What modifications have worked for other developers in similar cases Thanks a lot in advance for any advice or shared experience 🙏 Happy to provide more details if needed.

On January 1, 2026, we received a notice regarding the potential removal of our app with a 30-day resolution deadline. We treated this matter with immediate urgency and submitted an appeal on the same day. However, two weeks have passed without any feedback or clarification. As we have not yet received specific details regarding the violation, we are unable to identify the exact cause or take the necessary corrective actions. With only two weeks remaining in the compliance window, it is critical for us to understand the issue promptly to resolve it before the deadline. Could you please provide an update on the status of our appeal? We are fully committed to complying with App Store policies. If there are any additional materials required or proactive steps we should take while waiting, please let us know.

Did any one face this issue "Note that users expect apps they download to function on all the devices where they are available. Since your app may be downloaded onto iPad devices, it is important that it also function as expected for iPad users" even though we already done the following Target → General → Deployment Info Devices: ☑ iPhone ☐ iPad ← MUST be unchecked UIDeviceFamily = 1 Mac Catalyst is set to NO

Brand new to app development and marketing and preparing to launch my app on both the App Store and Google Play Store soon I understand ASO is a strong approach for organic growth and would appreciate any tools services or practical advice on how to do ASO efficiently and effectively

Hello everyone, I’m looking for guidance regarding a prolonged App Store review delay. I submitted my app for review more than 12 days ago, and its status has remained “Waiting for Review” with no updates. I have also tried contacting Apple through App Store Connect and the Contact Us option, but I haven’t received any response so far. This app does not include any unusual features, private APIs, or sensitive content, and previous versions (or similar apps) were reviewed much faster. The long delay is blocking a planned release and affecting our timeline. Could anyone please advise: If this review duration is normal lately? Whether there is a recommended escalation path beyond App Store Connect messages? If there are any known review backlogs or issues I should be aware of? Any insights or suggestions from developers who’ve faced a similar situation would be greatly appreciated. Thank you for your time and help.

I am developing a utility application for macOS. In the next version, I would like to access data files from multiple third-party web browsers. However, requiring users to manually select and grant access to each browser’s folder individually would be inconvenient from a usability perspective. Therefore, I am considering requesting Full Disk Access for my app. Is it realistic to expect App Store review approval when requesting Full Disk Access? Under what conditions or use cases is such permission typically accepted by Apple? I would greatly appreciate any advice or experiences you can share.

Hey everyone, I’ve been building iOS apps since 2011, released several, took a four-year break, and recently launched two new apps, but the ecosystem feels very different now. Earlier, new apps saw strong first-day downloads and fast Google indexing, while today my App Store pages took weeks to appear and show almost no organic traction without promotion, so I’m curious if others notice this and how developers now gain discovery.

Hello everyone, I'm seeking advice from the community regarding an App Review rejection I've been struggling with. Situation: My Mac app, an application launcher, has been rejected under Guideline 5.2.5 for being "too similar to LaunchPad, which creates a misleading association with Apple." After requesting specific feedback on what needs to change, I received only a generic response directing me to read the guidelines without any actionable details about which features or design elements are problematic. My App's Differentiating Features: My app includes numerous features that distinguish it from LaunchPad: Windowed mode in addition to fullscreen Category topbar with filtering capabilities Resizable grid with customizable icon sizes and spacing Advanced organization with custom categories, tags, and usage tracking Different visual design language and interaction patterns The Challenge: I've observed several other app launchers on the Mac App Store that appear to share more similarities with LaunchPad than mine does (e.g., identical pagination, similar grid layouts, similar visual design). This makes it difficult to understand why my app specifically was flagged. What I've Tried: Provided detailed documentation of differentiating features Requested specific feedback on which elements need changing Compared my app to approved alternatives on the store Received only a generic response with no actionable guidance Questions for the Community: Has anyone else faced this type of rejection for app launchers or similar utility apps? What specific changes did you make that satisfied App Review? Are there particular visual elements or features that App Review considers "off limits" for this category? Should I consider filing a formal appeal, or is there a better path forward? Are there any Apple engineers who might be able to provide insight into how to differentiate from built-in macOS apps while still solving the same user problem? My Goal: I'm not trying to clone LaunchPad - I'm trying to provide users with a more powerful, customizable alternative. However, without specific guidance on what crosses the line, I'm stuck in a loop where I can't make meaningful changes. Any advice, experiences, or suggestions would be greatly appreciated. Has anyone successfully navigated a similar rejection? Thank you in advance for your help!

Hello, I submitted my game app on 28 Dec last year. Unfortunately, it was stuck in review for weeks. I've tried submitting a request to expedite the review, I've reached out via the contact form, I've even tried resubmitting the build - all to no avail. Prior to this, I've been able to release monthly updates without trouble. Any advice on this issue would be greatly appreciated, thank you kindly!

Hello everyone, My team is exploring the implementation of an Apple Wallet pass for a loyalty program linked to a brand in an age-restricted product category. The intended use cases for the Wallet pass are: Member identification at events — Quick verification at brand events or exclusive venues, with tier-based perks (e.g., priority entry for higher tiers) Support services — Members present their card at retail locations to receive assistance Tier and points display — Dynamic visual changes based on loyalty level and current points balance Notifications — Pass updates for expiring points, upcoming events, or relevant announcements The pass would function as a standard Store Card (membership/loyalty) — no payments, no stored value, just identification and informational display. Before investing development effort, I'd like to understand: Has anyone successfully implemented Wallet passes for brands in restricted categories (tobacco, alcohol, etc.)? Are there specific guidelines or restrictions I should be aware of beyond the standard Wallet documentation? Is there a recommended channel to get official guidance from Apple on eligibility before building? Any insights or experiences would be appreciated. Thanks!

I was wondering if there was a way to submit an app for review before completing the terms of service and privacy policy in case the app does not get approved.

Hi, Anyone else hitting this App Store Connect issue? I have now submitted two app versions. Both get accepted and I can release them, but the subscriptions are never included. What is happening: App versions get approved normally No “In-App Purchases” section appears on the app version review page Subscriptions page shows subscriptions stuck on “In Review” for 10 days Subscription localization is “Rejected” and completely locked I cannot edit, recreate, or resubmit anything related to subscriptions.. Tried submitting a new app version again, same result. App approved, subscriptions still stuck. So I keep releasing without subscriptions every time 🤦‍♂️ Anyone experienced this or found a way to unblock subscriptions when localization is rejected and locked? Thanks!

Dear App Review Team, Our app – Apple ID 6754872058 has been stuck in the “In Review” status for over 7 days (since Jan, 15 at 10:44 PM). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this hold? • Is any action required from our side? • When can we expect the review to finish? Thank you very much for your time and assistance.

Hey all, I am a first time publisher navigating the App Review process. I want to publish a watchOS only app, but keep getting this feedback: Regarding 4.0, Apple Watch app icon's background color is still black. Based on our investigation, you have included plain black icons. To resolve this issue, it would be appropriate to modify your app's Apple Watch app icon to include a lighter background color to ensure that it is recognizable and appears circular on Apple Watch. I set the following configs: Project -> Targets -> Apple Watch App -> App Icons & Launch Screen -> App Icon set to my Icon Composer file. Checked App Icons Source. I was able to install my build through TestFlight and successfully install on my watch, and the App Icon displays properly there. I also saw a recent Reddit post from another developer facing the same issue. I can't link that post, but will share this post with the OP. I attached what the reviewer sent me with the rejection.

Hey All, Last week, I submitted a build of my app with the ability for users to subscribe & receive some extra content in exchange. I wasn't super sold on that being the right path for my app, and when I rightfully received a rejection for missing in app EULA, I decided that I'd postpone monetizing the app and I'd give away that content instead. So, I went ahead and disabled any paths of entry to the subscribe modal & marked the subscriptions as "Remove from Sale" in AppStoreConnect. Additionally, I updated the subscription review notes to be "This is not accessible in app at this time" Sadly, I still got rejected due to missing EULA and the tester being unable to find where IAP's are offered. I'd like to avoid cutting a new build, and instead just remove the subscriptions from being associated with this submission. But, I cannot for the life of me figure out how to remove them! Please help! TLDR: How do you disassociate an IAP or Subscription from an app submission?

I've been rejected by Apple many times for design spam. I'm confused whether this is because I'm reusing codebase or because my app is similar to other apps on the store. However, very few other apps on the App Store are similar to mine, so I don't think I'm spamming. Could you please tell me how to fix this? Should I refect the codebase or completely redesign the app's features? Thank you for reading!

When creating a new App Store version to update ASO keywords and metadata, I notice that elements like the app icon and other details are missing and I am looking for a way to copy the existing metadata from the previous version. Also, is it possible to submit a new App Store version solely for ASO improvements without uploading a new build and still have the changes applied successfully.

Hello App Review Team, I am writing to seek clarification regarding repeated review feedback received via App Store Connect (Resolution Center) for my app: App Name: Animal Sounds & Insects 90+ App ID: 6741077718 Team ID: 24MTF8NJ6Q Over the past two weeks, this app update has remained in review with multiple rejections referencing similar concerns, despite detailed responses and clarifications already provided in the Resolution Center. Unfortunately, I have not received follow-up responses or specific guidance there, which has prevented me from releasing even a minor update. To ensure clarity and avoid further delays, I am summarizing the key points below. Parental Gate (Guideline 1.3 – Kids Category) The review feedback indicates that the app may include links, commerce, or ad interactions without parental permission. I would like to clarify that the app implements a mandatory, non-dismissible parental gate, which is required before: Opening any external links Engaging in any form of commerce, including in-app purchases Interacting with any advertisements This parental gate cannot be bypassed or disabled and is triggered consistently across all applicable user flows. No child user can access links, purchases, or ad interactions without successfully completing the parental gate. If there is a specific screen, flow, or scenario where this behavior was interpreted differently during review, I would greatly appreciate precise details so I can verify and address it immediately. Advertising Experience (Guideline 4.0 – Design) The review also notes that users are required to view advertisements prior to using the app. I would like to clarify that the app does not require users to view advertisements before accessing its core functionality. Specifically: There are no forced ads No launch or entry interstitials No ads that block or gate access to the app’s main features Advertising within the app is passive and non-intrusive. This setup has been live for over one year, and no recent changes were introduced that would alter this behavior. Request for Guidance I fully respect and support the App Review Guidelines and am committed to complying with them. Given the repeated rejections and lack of actionable feedback so far, I kindly request: Clear and specific guidance on the exact screen, flow, or behavior being flagged Confirmation on whether the current parental gate implementation is being detected correctly during review My goal is to resolve any remaining concerns as quickly and accurately as possible so the review process can move forward. Thank you very much for your time and support. I appreciate the work of the App Review team and look forward to your guidance. Kind regards, Jiyan Aslan Developer, Animal Sounds & Insects 90+