“4.3”

I have app, which I developed and published: https://itunes.apple.com/us/app/selfie-horoscopes/id1437164941?ls=1&mt=8After approval I decided to make update and added IAP subscription.And got this:We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam.The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved.Why so? 🙂

Hi everyone. I’m looking for some advice regarding repeated rejections under Guideline 4.3(a) - Design - Spam. I’m a solo developer and have been making car simulator sandbox games since 2020. I already have an older game in the same genre on the App Store, and I’ve spent around 2 years developing its sequel. The new game is also available on Google Play, where it has passed 1M installs in its first month and currently has a 4.9 rating. The iOS version has now been rejected 5 times over the last 4 months. Attempt 1: Rejected under 4.3(a) with: We noticed the app shares a similar binary, metadata, and/or concept... I explained what makes the game different, filed an appeal, added a new feature, and submitted again. Attempt 2: Same rejection. I requested a phone call with App Review. During the call, I was told that their system had detected a binary match with another developer’s game in the same genre. The reviewer explained that similarities could come from game code, assets, shared engine

My application was developed by myself There is a reason for being misunderstood Please allow me to provide some information： My application has already been launched on a macOS platform version (temporarily called AAA). I encountered difficulties in compiling the SDK, as it cannot be compatible with two platforms in the same project at the same time. Therefore, I have specifically developed an iOS version (temporarily called BBB) This version uses a different bundle ID from the plaintiff's macOS platform version, equivalent to two independent apps. Then, the (BBB) version of my iOS platform was rejected. The reason was 4.3- Spam. I accepted this decision and did not attempt to apply for listing again, and deleted the relevant information. Later on, I spent time and finally overcame the difficulties of SDK compilation, successfully developing an iOS version (temporarily called CCC) based on the macOS version, using the same bundle ID as the macOS version, which can be considered as the same app My ne

Hi everyone, I would like to ask for help how should I resolve the issue with app submission for Guideline 4.3(a) - Design - Spam. I will explain my case to you. I assigned a task to junior engineer to submit an app from a personal developer account because my organization account has not been available yet. I thought I could be transfer later or resubmit under different bundle id and account would be okay. yes, it was my fault . But the app review process was taking too long in the personal account and I told him to cancel and delete the app submission, thinking that there might be not issue since the app was not released in AppStore. After I submitted the updated version of app with organization account, it doesn't get approve and getting 4.3.0 Spam rejection. We have taken about 6 months of work putting all the efforts both in the technical and business side on the product from scratch. We are about to launch in next week and our app is got rejected. I don't know what to do. I've all the authority

I develop apps for radio stations and WebTVs.Recently I had to update some apps at the same day, because I had to change the streaming url, and all were rejected. Now, even the new apps are rejected.I submitted an appeal explaining that my apps are individually branded, so branding on the home screen, app store searching and the app name matter for my clients. I believe my apps are not creating clutter, each one has unique brand, name, color scheme, background and specific content. That will not confusing users.They replied:We understand that your radio and TV apps are individually branded. However, they share the same concept and feature set. It is no longer appropriate to submit multiple apps that provide the same or similar feature set.To resolve this issue, please consolidate similar apps into a single directory app (for example, all radio apps into one container, and all TV apps into one container) that allows users to select from different channels within the app.These type of one container app with mul

I am being completely blocked from creating apps, or even updating apps. This is the message I receive every time:We noticed that your app provides the same feature set as other apps that have been submitted to the App Store (either under your own account or across multiple developer accounts) and simply varies in content or language.Apps that simply duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps.We encourage you to review your app concept and incorporate different content and features that are in compliance with the App Store Review Guidelines.Best regards,App Store ReviewNo matter what I do I get this for any app I put up. I uploaded 2 bug fixes to 2 apps already on the store, and 1 new app, completely different than any other app I've ever put up, and they all were put into review and rejected in 1 minute. 1 minute for all 3. The reason, is stated above. When I asked about it further I was presen

Hello So I have an application which is in the Apple store. I wanted to fixe some issue therefore i created update build with the following: • Reworked Character Physics: Improved responsiveness and movement for smoother, more controlled gameplay. • Bug Fixes & Performance Enhancements: Fixed critical issues affecting gameplay consistency and stability. Players will now experience better performance and more accurate controls. • Mac Catalyst Fixes: Improved support for macOS, fixing issues related to UI scaling and responsiveness. The changes above are basically all there is. Now it seems that i am not able to pass review as it constantly marks design spam and not give anything in particular. Whats up with that ?

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

I’m looking for advice and clarification regarding an issue I’ve encountered during the review process. My app was recently rejected under Guideline 4.3(a) for allegedly duplicating content or functionality of other apps. The feedback stated that my app appears to be identical to apps already on the App Store, but I’m confident this is a misunderstanding. The app is entirely unique, both in its functionality and its independently developed codebase. This rejection is puzzling, as I’ve thoroughly reviewed the guidelines and ensured that my app adheres to them. Has anyone else encountered similar issues? How did you address them? To the Apple team: Could you provide additional context or examples of the similarities identified? I’d be happy to address any concerns or make adjustments if necessary to align with the App Store standards. Submission ID: a6e96157-a543-45c6-b05d-8c50766ea4bf I’m grateful for any insights or advice from the community and the Apple team. Thanks in advance for your help! Best r

We are seeking clarification on guideline 4.3, Spam. We are readying to deploy an individual and unique app for each of our clients and were advised we should review the guideline. Since we have seen other companies who appear to be building with the same set-up we do not think we are in conflict, but we want to make sure we are proceeding correctly. To elaborate on our setup: We build with a shared codebase that deals with communication with our servers, page rendering and state management however, the resultant app produced is unique to each client. Clients select custom background images, logos, provide custom messaging and may choose from any one of our color themes. Also, their “App Information”, eg their description, keywords, marketing and naming used for their store presence are unique to the produced app. Users who install our clients app may view details related to our client’s business and use it to manage services with our client. Users without an account may browse views of our a client’

Hello everyone, I am hoping to get some advice or hear from anyone who has successfully navigated a similar situation with App Review. We are currently stuck in a review cycle regarding Guideline 4.3(a) - Design - Spam, and the goalposts seem to be shifting. The Context: Our company recently acquired a B2B application (a utility app used by regional cable operators in India for payment collection). The app was originally built by an independent developer whose Apple Developer account was subsequently terminated. We legally acquired the complete intellectual property, source code, and distribution rights. The Review Timeline: Submission 1: Flagged under 4.3(a). App Review stated the app was associated with a terminated account. We replied via the Resolution Center, attaching the fully executed IP Assignment Agreement and proving we are a distinct, compliant corporate entity. We also updated the Bundle ID and backend infrastructure. Submission 2 (Current): Apple reviewed the IP documentation b

After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are already enough of these apps on the App Store. While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid category quota can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers,