“4.3”

We have submitted an app which is published in production, however we are planning to move to use flutter and standardise the development and created the same design but name it to version 2 with new features, we are planning to migrate everything to this app but always get this issue and our appeal seems unable to reach Apple review some how. What should we do in this case?

Well it finally happened to me. I have been waiting for it. I got for rejected for spam, on a new Sudoku App. I have a Calcudoku App. A Nurikabe App. A Kakurasu App. All with the exact same interface.And I uploaded a Sudoku App, and got tagged for similar design Spam.There is ZERO way to combine the apps, unless I want to spend a few years.I can understand how the reviewer rejected it.But the 'spam design' is actually a GOOD thing. Having a similar design for completely different puzzle games add a familarity to the user. SO he / she only has to learn a new game and not a new interface.Obviously these reviewers are not programmers, and they just follow a checklist. Ironically, this is one of my best coded apps. I computer generated Sudoku Puzzles, not an easy thing to do. (They have TED talks on it)There is nothing I can do but appeal. There is no way to fix this. It is really quite depressing. I hope some of these these App reviewers are programmers, and my appeal is accepted.

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?

Hello, we have been having huge problems with guideline 4.3- Spam. We submitted our App just fine and it has been rejected on the update. We have responded multiples time with no help.Their original response was:“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” and ”When creating multiple apps where content is the only varying element, you should offer a single app to deliver differing content to customers. If you would like to offer this content for purchase, it would be appropriate to use the in-app purchase API”.We kindly explained to them our app has been created in-house with a team of over 15 developers. We did not use a template. We also attached our copyright for them. Not only this, but we only have 1 APP in our developer account. We have heard of developers being rejected with tons of APPS but we only have 1! We have double checked our description and keywords too and

Hello everyone, I’m looking for advice from developers who successfully resolved a Guideline 4.3(a) “Spam” rejection in a legitimate account migration scenario. Situation: I originally developed and submitted my app under my personal Apple Developer account. Later, after creating a business/company, I opened a business Apple Developer account because I wanted the app published under the company instead. The original app on the personal account was removed before submitting on the business account. I changed the Bundle ID and created a new app entry under the business account. However, the business-account submission was rejected under: “Guideline 4.3(a) - Design - Spam” with the message about “similar binary, metadata, and/or concept.” I appealed and explained that this is the same legitimate app/business transitioning from an individual account to a company account, not a spam network or template cloning situation. The appeal was denied. What makes this more confusing is that the app on the

I've exhausted all avenues getting this resolved; so I'm posting this here mainly to document the absurdity of what happened, and as a warning to other developers.We built an app that was rejected because of its name. We happily renamed the app, creating a new app record because we also wanted to rename the SKU and Bundle ID, and you can't do this any other way.Big mistakeNow there are two factors combining to put us in an impossible situation.The little-known, bizarre limitation of iTunes Connect that An app that has never been approved can never be deletedThe improper enforcement of the 4.3 guideline such that Similar apps you have submitted in the past apparently includes apps that were rejected and are not on the App Store.So now, our New Name app is being rejected for being too similar to our Old Name app. And the Old Name app can't be deleted because it was never approved.To make matters worse, thanks to inconsistent enforcement, our New Name app actually was approved in its first version (1.0)

I need practical guidance from developers who have successfully handled a Guideline 4.3(b) rejection, especially for an astrology-related app with broader personalized features. I mainly want to understand how to present the app, write the App Store description and Review Notes, choose screenshots, and decide whether to reply in the Resolution Center or file an appeal. My app was rejected because Apple said there are already many astrology apps on the App Store. However, it is not designed as a standard horoscope or prediction app. Its main experience focuses on personal milestones, AI-powered questions, relationship compatibility, private social connections, and a personalized user journey. Planetary positions are used only as one supporting input in the backend to provide contextual insights. They are not the main purpose of the app. Has anyone successfully handled a similar rejection? Any real experience or practical advice would be very helpful.

I am in the middle of trying to get an app approved for beta release and the back and forth with the App Store reviewers has been incredibly frustrating and concerning. On Tuesday, I created an app record for my app but quickly realized I made it under the wrong account- I'm working for a company that has a few brands under it's umbrella, and I was under the wrong account when I created the app record. Rather than wait several days to get Apple's approval to transfer app ownership, I decided to delete that app record and create a new one under the proper account. Worst mistake of my life. Now, Apple is insisting that the new app record is spam despite my clarification that I own the other app record and that it was deleted before the new one was created. I have no choice but to believe that somebody else is using our branding and asset somewhere in the App Store that I can't see. Does anybody know how I can resolve this? It should have never taken me the whole week to make an app available on test flight and

Hello, I allow myself to contact you because following two rejections of the update of my application because of a problem of multiple bundle ID, I rechecked my package in unity, checking the version numbers in xcode is all looks okay to me? Is there anything else I could look at? I had released an update a few days before without worries, thank you in advance for your answers

Hello, I am looking for guidance about a repeated Guideline 4.3(a) rejection affecting version 1.2 of an existing app. FilmFold versions 1.0 and 1.1 were approved under the same App Store record and bundle identifier. Version 1.2 is an update to the same product. FilmFold is the only app published under my seller account. It is not a template or white-label app, and it has not been submitted through another developer account. The rejection says the app shares a similar binary, metadata, or concept with apps submitted by me or other developers. I understand that Apple cannot disclose another developer's confidential information, but the replies have not identified whether the concern is related to code, assets, metadata or functionality. FilmFold is a camera app with 22 original virtual camera bodies. Each body defines its own optics, focal range, controls, aspect ratio and processing profile. The app includes custom native Swift video processing, an on-device photo pipeline, lenses, accessories, doub