4.3

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

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

Hello, I am facing a recurring issue during the review process of my app, FlexicX, and I am struggling to understand the exact concerns raised by the App Store Review Team under Guideline 4.3. Each time I submit my app, I receive a response stating that it duplicates the content and functionality of other apps already on the App Store and is therefore considered a form of spam. However, no specific examples or comparisons are provided to help me understand which parts of my app are considered problematic or why. I submitted an appeal over a week ago but have not received any substantive response. Each time I contact support, I receive nearly identical replies, reiterating that the app duplicates functionality, but no clarification is given as to what exactly they believe is duplicated. This lack of detail is incredibly frustrating and makes it feel like the guidance is to simply “throw out the app and remake it,” which is neither realistic nor fair. FlexicX is a highly innovative game that has alread

We have spoken to many developers in previous months who have run into issues with the new 4.3 Design Guidelines rules & had their apps rejected, seemingly by a bot, or in general, by a reviewer because of similarities to previous apps. They have been asked to combine their similar apps into one container app.We understand why Apple is finally cracking down and doing this. They are trying to clean up the Appstore of clones, useless junk & other spam apps.In the process however, this has seemingly hurt indie developers who are not using templates, and design their own games from scratch. We've spoken with several developers, many who pride themselves in creating unique content such as educational & games for children, receieve these notices with no method to appeal, and auto-responses making the same blanket statement, ending in frustration for the developer & wasted months in development time.They are asked to combine their apps or games into one single container app to reduce the clu

Hello, I am facing an issue with App Store Review Guideline 4.3(a) - Design - Spam. My app was rejected because it was found to be similar to another app previously uploaded on a different Apple Developer account. However, I have lost access to my old developer account and cannot remove or modify the previous submission. Currently, I am unable to: Log in to the old Apple Developer account Remove or update the app that is causing the conflict My new app is intended for internal testing only and is not yet published on the App Store. I have made efforts to modify the app, but the system still detects similarities with the old app. I would like to ask for advice or assistance on how to proceed in this situation, as I no longer have control over the previous account. Has anyone experienced a similar situation, and is there any way Apple can help resolve this? Thank you very much for your support.

After installing Beta 3 tonight found that Crashplan is borked. The UI is totally unresponsive and unusable. Suspect it has something to do with the Apps Java dependence. It seems to continue to run backups but nothing with the UI works. I've seen a few forums in which folks are saying it does work but I'm not sure that is really the case. I've submitted diagnostics logs, and information to Apple and Crashplan. Recommend those experiencing the same problems report through the proper support channels.