4.3

Hey everyone, We recently submitted our new dating app, Rove Dating, and it’s been rejected under Guideline 4.3(b) — “Design: Spam.” I’d really appreciate your insights, especially from anyone who’s faced something similar or has experience getting nuanced apps approved in a saturated category. Before building Rove, we spoke to dozens of users of existing dating platforms. We consistently heard the same thing: people are deeply dissatisfied with current apps. They’re overwhelmed, burned out by swiping, and frustrated by endless choices and low-quality interactions. It became clear that the problem isn’t that there are “too many” dating apps — it’s that most aren’t adapting to how people actually want to date in 2025. We designed Rove to address those pain points head-on, with a totally different approach to matching, message limits, and emotional safety. We believe our app meaningfully improves the dating experience — but we’re having trouble getting that across in the review process. Below is the ex

My app keep getting rejected after changing complete UI. It's an finance tool app. any advice 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. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts

Hello Apple Developer Support & Community, I’m reaching out regarding the unexpected termination of my Apple Developer Program account, associated with App ID: 6744330283. Recently, my app was flagged under Guideline 4.3 - Spam, and I was asked to make necessary changes. I followed all guidance provided by Apple, including a phone call with an App Review team member, who clarified the steps I should take. I did not submit any further update after that call. However, before I had the chance to upload the new, compliant version of my app, my entire developer account was terminated without a clear explanation or additional warning. I believe this was a misunderstanding, as I was actively working on compliance and fully committed to resolving the issue. My app is not spam I only followed Apple’s instructions I never uploaded a new version after my call with App Review No specific violation or example of “spam” was shown to me I’ve submitted an official appeal via the App Review Board, but I’m hoping

Hello Apple Developer Team and Community, I’m writing to raise a serious concern regarding my app (App ID: 6744330283) which is now being repeatedly rejected under Guideline 4.3 (A) – Spam, despite being previously approved and published for at least two earlier versions. We have had multiple rounds of communication with the App Review team in the past, carefully addressing every request and making adjustments accordingly. These previous versions were reviewed and approved without any reference to 4.3 issues. However, since a recent update, we’ve been receiving rejections citing Spam 4.3 (A) — without any specific explanation or detailed reasoning. Even more frustrating: Each review now takes over a week to process, making our release cycle extremely difficult to manage. It required dozens of phone calls and emails just to get the app reviewed at all. I even had a meeting with an App Review team member, where I was told: “The recent updates are considered Spam 4.3, while th

Section 1: Our game was developed using Cocos Creator 3.8.5, written in TypeScript. The team spent nearly two years completing it. Initially, our submission wasn't classified under Guideline 4.3(a). The first four reviews provided normal feedback, which we addressed. However, after a subsequent rejection citing 4.3(a), we considered whether similarities in gameplay concepts, narrative, or art assets might exist. In response, our team introduced unique features not found in other App Store applications. We completely redesigned our original art assets to ensure originality and extensively modified aspects potentially resembling other developers’ work. This included removing all third-party SDK modules except Apple Pay and Sign in with Apple. Despite these significant efforts, we still received a 4.3(a) rejection. We have now iterated over 20 versions but continue to face this issue.  Section 2: Our game’s business logic code (excluding the Cocos engine code) is entirely original and

Hello, please someone help me this outrageous i worked so hard on this game for many months and payed apple developer fee to get my app Rejected for being spam which is completely FALSE my app genre is endless runner which is very popular and have a lot of apps but my story is original my music is composed by a professional musician specifically for my game, the UI designed by ME, yes my control mechanics is the same as many apps—this is expected due to genre standards, not duplication. The presence of similar controls codes does not automatically make a game spam. If this logic applied broadly, many top games on the App Store would be at risk of the same guideline violation, Yes i did use some free to use commercially Unity assets (which is entirely permitted under Apple’s policy), i have customized and integrated them meaningfully into the game, so how is this spam?

Our game was written by Cocos Creator version 3.8.5 ‌TypeScript, which took the team nearly 2 years to complete. At the beginning, my application was not defined as 4.3a. The first four reviews were all normal feedback questions. We revised the questions. After the last review rejected 4.3A, we also suspected that the reasons such as game creativity, game copywriting and game art might be close to other applications. Then our team added functional innovations that other applications in the Apple Store didn't have, and the original art was original. We created new art again because of 4.3a, and also revised many places that may be similar to other developers, including that we removed all SDK modules except Apple Pay and Apple Login, and it also showed that 4.3a refused, and we have revised no less than 20 versions or failed. Our business code except the game engine code is newly developed by us and should not be duplicated with other developers' code. Is it because the JSC file and binary file output by JavaS

Hi everyone, I submitted an appeal to the App Review Board on May 27, related to a rejection under Guideline 4.3(a). (We noticed your app shares a similar binary, metadata, and/or concept as other apps you already submitted to the App Store, with only minor differences.) (The app is named LucidYou and was submitted through my personal developer account.). So far, I haven't received any update or response in App Store Connect or via email. I fully understand that WWDC may have delayed reviews, and I appreciate how busy this time of year is. Still, I just want to make sure my appeal was received and is still being considered. Has anyone else experienced longer-than-usual response times for appeals recently? Should I follow up via App Store Connect again or wait a bit longer? Thanks in advance — any advice or shared experience would be appreciated!

Hello, I submitted an appeal after my app was rejected under Guideline 4.3(a). It has now been over 5 days and I have not received any reply from the App Review Team. Has anyone experienced similar delays recently? Does Apple respond eventually or is there something else I should do? Thank you in advance.

I can't pass rule 4.3b. I'm practicing horoscope. How do you think I should proceed? Is it possible to publish this application?

We are preparing to submit a new app that shares some functionality and with an app we have previously distributed on the App Store. The Codebase will be different (the existing one was developped using React JS and the Second one usinf SWIFT). While the new app includes updated features, a redesigned interface, and is intended for a different user audience, we would like to confirm in advance whether submitting it as a separate app (with a new Bundle ID) is acceptable under current App Store Review Guidelines. In particular, we would appreciate clarification regarding Guideline 4.3 (Spam), to ensure that the submission will not be considered a duplicate or unnecessarily repetitive version of our existing app. Could you please advise on this matter?