Search results for

4.3

584 results found

Post

Replies

Boosts

Views

Activity

Rejected for Spam 4.3 (A) Without Clear Reason – Previously Approved App Now Stuck in Review for Weeks! [App ID: 6744330283]
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
1
0
143
Jul ’25
Reply to App submission rejected
Thank you for your post and appeal. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple Experts event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Jun ’25
Unique application rejected due to guideline 4.3(a)-Design-Spam.
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
1
0
144
Jun ’25
Unique application rejected due to guideline 4.3(a)-Design-Spam.
Here is the English translation of your content:  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 (exclud
0
0
120
Jun ’25
4.3a Refuses to appeal or seek a solution, and the game production will solve the 4.3a problem for 2 years and be revised for half a year.
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
1
0
112
Jun ’25
No Response to My App Review Appeal (Submitted May 27)
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!
1
0
95
Jun ’25
Reply to 4.3 B Spam Error
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Jun ’25
Reply to App Submission Clarification – Similar Functionality to Existing App
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple Experts event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Jun ’25
Reply to Appeal Submission – No Confirmation or Update
Just to clarify the situation in case someone can offer further insight: It's a new app and the reason it was rejected was 4.3(b) Spam - Your app primarily features astrology, horoscopes, palm reading, fortune telling or zodiac reports that duplicate the content and functionality of similar apps in a saturated category. -- but this seems to be a misunderstanding. My app’s purpose is quite the opposite of what was stated in the rejection. It’s a science-based educational experience that uses Greek mythology as a narrative hook, then guides users through constellations (not horoscopes or zodiac signs) to explore verified astronomical (not astrological) knowledge. The goal is to inspire curiosity about the universe through astronomy and not astrology. There is no horoscope, zodiac, or fortune telling content in the app. I’d really appreciate any additional feedback or help ensuring the app is accurately understood.
Jun ’25
Reply to Continous 4.3 (a) Spam rejection
Thank you for your post and appeal. We're investigating this issue and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Jun ’25
Reply to Request for update on app review pending since June 2nd
I'm currently experiencing the same issue as you. I’ve already gone through this twice — my app was approved in versions 1.0 and 1.1, but all the newer versions have been consecutively rejected. If you wait the full 7 days, the system will automatically treat your app as spam and reject it without a proper review. This issue can be identified when even your TestFlight beta builds or App Store submissions are delayed for 7 days, only to be rejected with the reason Spam 4.3(A). This has already happened to two of my apps. Now my third app is facing the same problem. I’ve contacted the support team via email and phone, but they’ve been very irresponsible — only giving vague, generic responses. Apple does not seem to value new developers. They clearly prioritize older, established ones. A company that claims to be professional is now proving its worth by moving backwards. My app ID 6744330283 is also affected just like yours. Despite having gained user trust and over $3,000 in purchases so far, my app is
Jun ’25
Reply to App stuck in “In Review” and then “Waiting for Review” — seeking advice
I'm currently experiencing the same issue as you. I’ve already gone through this twice — my app was approved in versions 1.0 and 1.1, but all the newer versions have been consecutively rejected. If you wait the full 7 days, the system will automatically treat your app as spam and reject it without a proper review. This issue can be identified when even your TestFlight beta builds or App Store submissions are delayed for 7 days, only to be rejected with the reason Spam 4.3(A). This has already happened to two of my apps. Now my third app is facing the same problem. I’ve contacted the support team via email and phone, but they’ve been very irresponsible — only giving vague, generic responses. Apple does not seem to value new developers. They clearly prioritize older, established ones. A company that claims to be professional is now proving its worth by moving backwards. My app ID 6744330283 is also affected just like yours. Despite having gained user trust and over $3,000 in purchases so far, my app is
Jun ’25
App Submission Clarification – Similar Functionality to Existing App
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?
1
0
49
Jun ’25