“4.3”

Hello, I would like to ask for help with a Guideline 4.3(a) - Design - Spam rejection that I have been trying to resolve with App Review for about a month. Situation My app (Apple ID: 6782845619, version 1.2, Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb) was rejected under Guideline 4.3(a). The review message states that the app is available in the same locations as another identical app you submitted to the App Store. The other app referenced is an early prototype I created. It was approved in review at one point, but it was never released on the App Store. I have since taken the following steps, in line with the guidance in the rejection message: I withdrew the prototype app from App Review entirely (its status in App Store Connect is now Developer Rejected). I set its Country or Region Availability to none — it is now unavailable in all 175 countries and regions, so there is no storefront overlap with My app (Apple ID: 6782845619) at all. In other words, My app (Apple ID: 678284561

Hello everyone, I am seeking advice regarding a recurring issue with our app, YouMi UM, which was rejected due to alleged spam under App Review Guideline 4.3(a). The review team stated that our app shares a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. Our app, YouMi UM, has been successfully launched on the Android platform, and we have invested significant effort into its UI design and features. However, when submitting to Apple, the review team pointed out similarities between our app and others submitted by different developers, particularly in terms of binary files, metadata, and concept, which led them to believe it might violate Guideline 4.3. Our app is independently developed, with all code and design being original. We have also added several unique features, such as real-time news widgets, branded dynamic toast notifications, and exclusive scene transition animations, which are not commonly found in similar

Hi everyone, First, some context and a genuine compliment: this is our first iOS submission, and overall the App Store Connect tooling and TestFlight have been a great experience — our beta reached 1,351 external testers organically, with 1,700+ sessions and a crash rate below 1%. That said, we're stuck in a loop we don't know how to break, and I'd love advice from anyone who has been through it. Our game, Truckers Brasil Online, is a truck simulator with proprietary real-time online multiplayer, 100% developed in-house in Unity by our Brazilian studio. Same game, same brand and same company operating on Google Play since 2024. Our official YouTube channel has 1.84M subscribers with years of public devlogs documenting the development. We own all source code, all 3D models (including the original Blender source files of every truck), and the dedicated servers that run the multiplayer. The review history: Jul 04 — rejected under 4.3(a) Spam (similar binary, metadata, and/or concept), no specific app na

Hello everyone, I'm looking for guidance on a situation that has been quite frustrating for me. I've developed an AI-powered Tarot app that offers an innovative and enhanced experience. Its features include: 3 different tarot decks 70 tarot spreads AI-based personalized interpretations Extensive customization options The app has been successfully published on Android (You can search Tarot AI 3D in the android store) and has received positive feedback from users. Many have contacted me asking for an iOS version, so I decided to rebuild it in Unity with an improved approach, ensuring it meets quality and uniqueness standards. This new version has already been approved on Android. However, after several attempts, Apple has repeatedly rejected it under Guideline 4.3(b) - Design - Spam. I carefully reviewed the guidelines and put all my effort into creating a unique, high-quality experience. I have submitted two appeals (one 15 days ago and another about 5 days ago), but I have not received any response.

Hello, I'm seeking advice regarding my app CloakLine which has been rejected multiple times under Guideline 4.3(a) for being too similar to other apps. App Details: Name: CloakLine Bundle ID: com.ztech.cloakline Current Status: Rejected Rejection History: Initial Rejection: Reason: Similar binary, metadata, and/or concept to other apps Reviewer's comment: Submitting similar or repackaged apps is a form of spam Our Response: I've verified that no app with a similar name exists in the App Store This is our original work, not a repackaged app We have only one bundle ID All assets, code, and designs are original Actions Taken: Requested Phone Call: Was told our app has similar functionalities to other apps But no specific details were provided about which functionalities or which apps First Appeal: Added 5+ new unique features Result: Still rejected Second Appeal: Added another 5+ unique features Result: Still rejected Current Situation: We've ensured our app's uniqueness through: Distinctive app name an

Hello everyone, I'm hoping to get some advice or visibility on a frustrating catch-22 situation with App Review regarding my company's VPN app. Background: I originally developed our VPN app under my personal Apple Developer account. App Review correctly informed me that under Guideline 5.4 (VPN Apps), the app must be submitted by an enrolled Organization, not an individual. To fully comply with Apple's policies, I formed my company, enrolled as an Organization, and transferred the app. My previous personal account was closed as a direct result of this migration. The Issue: Now, submitting the exact same app under my new, fully compliant organizational account, I am getting repeatedly rejected under Guideline 4.3(a) Design - Spam: We noticed the app shares a similar binary, metadata, and/or concept as apps previously submitted by a terminated Apple Developer Program account. The terminated account is my own previous personal account! The similar binary is because it is literally the exact same app be

Hello everyone, I hope you are all doing well. I’m opening this discussion because we’ve encountered a repeated Guideline 4.3 rejection for an update, despite having previously addressed the same concern with the App Review team and reaching a resolution. Several weeks ago, we went through a detailed review process regarding Guideline 4.3. We provided full technical explanations, clarified our development structure, redesigned parts of the UI, and made all adjustments requested by the App Review team. That update was ultimately approved, and the app has been live on the App Store since then without any issues. However, our new submission—which includes only a critical bug fix—is now being rejected again for the same 4.3 reason. No changes have been made to the concept, design, or core functionality since the previously approved version. The update is not introducing new features or new UI; it simply resolves a performance bug affecting downloads and uploads, which users are already

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

We submitted our application for a review and got rejected with the followings. Review date: February 18, 2025 Version reviewed: 1.0.0 Guideline 4.3(a) - Design - Spam We noticed your app shares a similar binary, metadata, and/or concept as apps previously submitted by a terminated Apple Developer Program account. 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 Learn more about o

Hello Apple App Review Team, I'm looking for guidance regarding an App Review case that appears to be pending without a response. Our app was rejected under Guideline 4.3. We responded to the App Review Team through the Resolution Center with a detailed clarification regarding the app's purpose and functionality. Timeline: July 27: App rejected under Guideline 4.3. July 28: We responded through the Resolution Center. August 4: We sent a follow-up through the Resolution Center. August 5: We opened an Apple Developer Support case regarding the pending review. August 10: We still have not received a response from App Review or Developer Support. Developer Support Case ID: 20000128863068 We have also attempted to contact Developer Support by phone but have not received a call. The latest TestFlight build has already passed Beta App Review and is available for external testing. We have intentionally held off submitting the latest build for production while waiting for clarification on the current