Search results for

“4.3”

792 results found

Post

Replies

Boosts

Views

Activity

No response from App Review after a 4.3(b) rejection, is this normal?
Hi all, We submitted our app in App Store Connect in August and initially got quick responses from Apple (~2 days). On Aug 22, we were rejected under Guideline 4.3(b) (Design - Spam). Our app is a dating app, so we understand why it can trigger the guideline, but we believe it offers a meaningfully different experience from what's already on the Store and wanted to make our case. The Review team's rejection message invited us to reply with more information, so we did on Aug 24. We haven't heard anything back since. We sent a follow-up on Sep 7, and that's also gone unanswered. It's now been about three weeks of silence after our initial reply. A few questions for anyone who's been through this: Is it common for Resolution Center threads to go quiet like this after a 4.3(b) rejection? Has anyone had success getting a response by escalating, and if so, how (phone support, a fresh submission, something else)? Should we go through the formal Appeal process instead, or does that risk cutting off
1
0
249
Sep ’26
App Store Review 4.3 . help!help!help!
We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. 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 our requirements to prevent spam in App Store Review Guideline 4.3.
4
0
2.4k
Sep ’23
Urgent: App Store Rejection under Guideline 4.3
Our Application [7 Dawns: Echoes] was recently rejected by the App Store for Guideline 4.3 Apple ID:6753892922 Bundle ID:com.ark.jylhgl.ios Change of Operating Entity Our company, has obtained exclusive global operating rights (excluding Mainland China, Hong Kong, Macau, Taiwan, and certain regions of South Korea) from the copyright owner. The previous distributor’s version, Eternal Sword M (App ID 1369681345, Bundle ID com.emagroups.ea2), has been fully removed from the App Store. Our cooperation with them officially ended on December 29, 2023. New Version Updates This submission is not a duplicate, but a newly operated and updated version. We introduced new gameplay systems (7-day seasonal competitive mode, team-based PvP, dispatch and multi-pet strategy systems), optimized monetization and in-game economy, and improved performance and UI (including redesigned app icon and key interfaces). Evidence Submitted We have provided the Operating Authorization Letter and Software Copyright Certificate via
1
0
172
Dec ’25
watchOS 4.3 beta 3 Activity doesn't properly sync with iOS 11.3 beta 4
On the Watch: watchOS 4.3 beta 3On the paired iPhone: iOS 11.3 beta 4Observed behavior: Activity numbers (Move/Exercise/Stand) stop updating on the Watch, until the Watch is put to Airplane mode/restarted. If nothing is done - data is lost completely. In particular, Stand hours are missing and marked as empty, like the watch was not even on the wrist during that hour. Was previously observed with watchOS 4.3 beta 2 and 1 (and iOS 11.3 beta 2 and 1), but was fine with iOS 11.3 beta 3. After iOS 11.3 was updated to beta 4 - problem occured again and stay there.Remarks: with this iPhone two Apple Watches are paired. One with watchOS 4.2.3, another one - with watchOS 4.3 beta 3. However, the Watch with watchOS 4.2.3 is completely turned off for a week already.
0
0
416
Mar ’18
3rd time rejected: Guideline 4.3(a) - Design - Spam
My app keep getting rejected after changing complete UI. It's an finance tool app. any advice Guideline 4.3(a) - Design - Spam We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. 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
1
0
271
Jul ’25
Need some help understanding 4.3(a) rejection for my app Siply
My app Siply keeps getting flagged for Guideline 4.3(a) – Spam, saying it’s “similar in binary, metadata, or concept” to other apps on the App Store. I’ve already had a call with App Review and made a ton of changes since then, obviously they won't tell me what app they think it's emulating, which doesn't really help me as a dev. I've redone both design and function, but it’s still getting rejected for the same thing. Just for context, Siply isn’t a template or copy app. It’s built from scratch with a Create ML model for container volume estimation, a custom Figma UI, and a Firebase backend for login and data. The whole interface and flow are fully custom-built. I’m just trying to figure out what part of it is being seen as “too similar” so I can fix it the right way. Could this be triggered by me having other apps under the same developer account or Firebase project? Any insight would help, I’m kinda stuck on this one.
1
0
154
Oct ’25
First app rejected under 4.3(a) Design – Spam despite original code and assets — appeal guidance?
My first and only app, tower defense game (App ID 6802129713), was rejected under Guideline 4.3(a) Design – Spam. I'm a solo developer; the game is built on the open-source Godot 4 engine, with all code written from scratch and all art generated by my own tools in the same repository. The core of the game is a custom simulation running up to hundreds of thousands enemies on-device, which I believe no other App Store game does. I replied in the review thread with a point-by-point response to each 4.3(a) factor and asked which app mine is believed to resemble, but received only the standard template in return, so I don't know what to change. I've filed an appeal with the App Review Board. Has anyone successfully resolved a 4.3(a) flag in a similar situation? Is there anything else I can provide to demonstrate originality?
2
0
207
Sep ’26
Reply to Can SAAS-developed template apps pass the review and be published?
Appstore Guideline 4.3 may forbid you to do so. And here are some advices on how to handle it. 4.3 Spam Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. https://developer.apple.com/app-store/review/guidelines/
Aug ’23
All 66 of My Previously Approved Apps Are Being Removed Under Guideline 4.3
Today I received 66 separate, identical App Review notices, one for every live app in my developer account, stating that each app will be removed from the App Store under Guideline 4.3. These apps were previously reviewed, approved, and live. They are not 66 versions of one product. They span substantially different concepts and functionality, including games, utilities, productivity tools, social tools, and video tools. Every notice says the app shares a similar “binary, metadata, and/or concept” with apps submitted by other developers, but does not identify what specifically triggered the finding. Because all 66 notices arrived together with identical language, this appears to be a portfolio-level re-evaluation. Could someone from App Review please clarify: Is there a way to request a review of the developer portfolio as a whole rather than appealing 66 identical decisions individually? Can App Review identify whether the finding is based primarily on binary/source similarity, metadata, concepts, o
0
0
219
Sep ’26
4.3(a) on an update to a live app with 30 approved versions — App ID 6776105247
Hi, NewTake — AI Video Editor (App ID 6776105247) has been on the App Store since June 2026 with 30 approved versions and paying subscribers; version 1.8.9 was approved on August 27, 2026. Version 1.8.10 (submission 5ac4e580-9634-431d-be60-c4580e775295), which differs from 1.8.9 only by an optional feedback text field, was rejected under Guideline 4.3(a) on August 28 and again on August 29 after a Resolution Center reply. Both responses were the guideline template and did not reference anything specific in the submission. The app is a single bundle ID with an original on-device pipeline (transcription, scene detection, false-start trimming, captions — video never leaves the phone). No other app on our account shares code, assets, or concept with it. We have filed an App Review Board appeal and requested a call. We'd be grateful for guidance on what specifically triggers 4.3(a) on an update to an already-approved app, so we can address it.
1
0
135
Aug ’26
Rejected for Guideline 4.3(a) - Spam, looking for advice on next steps
Hello, My game was rejected under Guideline 4.3(a) (Design - Spam), with the message stating that it shares a similar binary, metadata, and/or concept with other apps already submitted to the App Store. The issue is I can’t figure out where this is coming from: No shared source code, template, or assets with any other game. No duplicated metadata. The app’s concept is still fairly niche on the App Store (I could only find around a dozen apps with a similar concept, at most). I’m trying to better understand what might have triggered this rejection, and I’m fully willing to make changes if needed. Has anyone else run into this kind of rejection under similar circumstances? How did you go about clarifying things with the review team, and did requesting an App Review Appointment help in cases like this? Thanks in advance for any insight.
2
0
500
Aug ’26
No response after 4.3(a) rejection, unlisted distribution already approved
Hello, Our app (Apple ID 6797897487) is an internal operations tool built under contract for a single business. It was rejected under guideline 4.3(a) on 29 August. We replied in App Store Connect on 31 August and on 10 September, adding that Apple had approved unlisted app distribution for the app on 8 September, but we have not received any response since. What is the recommended next step here? Should we resubmit the same build with the updated information, or wait for a reply to the existing messages? Thank you.
2
0
399
4w
Reply to Repeated Guideline 4.3 Rejection for Update – Requesting Insight From Fellow Developers And App Review Team
This is amazing how they just comment the same generic response even in the forum. i am facing the exact same issue I submitted my app last week and got rejected due to 4.3. After explaining the features and uniqueness of the app, they worte Me a reply that the issue has resolved. then they rejected due to 2.3.6 , fixed that and again today they returned to say again that the app is being rejected due to 4.3. Even when I attach screenshots of their message saying it has resolved just 48 hours ago, they are still holding their ground and keep on re me. they are not even saying what in the app is breaching the 4.3 guideline. this is an absolutely disgraceful
Nov ’25
Reply to 5 identical review rejections and no details
The same, but before approve I got 4.3 Design Spam rejection and then send appeal.
Replies
Boosts
Views
Activity
Apr ’18
No response from App Review after a 4.3(b) rejection, is this normal?
Hi all, We submitted our app in App Store Connect in August and initially got quick responses from Apple (~2 days). On Aug 22, we were rejected under Guideline 4.3(b) (Design - Spam). Our app is a dating app, so we understand why it can trigger the guideline, but we believe it offers a meaningfully different experience from what's already on the Store and wanted to make our case. The Review team's rejection message invited us to reply with more information, so we did on Aug 24. We haven't heard anything back since. We sent a follow-up on Sep 7, and that's also gone unanswered. It's now been about three weeks of silence after our initial reply. A few questions for anyone who's been through this: Is it common for Resolution Center threads to go quiet like this after a 4.3(b) rejection? Has anyone had success getting a response by escalating, and if so, how (phone support, a fresh submission, something else)? Should we go through the formal Appeal process instead, or does that risk cutting off
Replies
1
Boosts
0
Views
249
Activity
Sep ’26
App Store Review 4.3 . help!help!help!
We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. 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 our requirements to prevent spam in App Store Review Guideline 4.3.
Replies
4
Boosts
0
Views
2.4k
Activity
Sep ’23
Urgent: App Store Rejection under Guideline 4.3
Our Application [7 Dawns: Echoes] was recently rejected by the App Store for Guideline 4.3 Apple ID:6753892922 Bundle ID:com.ark.jylhgl.ios Change of Operating Entity Our company, has obtained exclusive global operating rights (excluding Mainland China, Hong Kong, Macau, Taiwan, and certain regions of South Korea) from the copyright owner. The previous distributor’s version, Eternal Sword M (App ID 1369681345, Bundle ID com.emagroups.ea2), has been fully removed from the App Store. Our cooperation with them officially ended on December 29, 2023. New Version Updates This submission is not a duplicate, but a newly operated and updated version. We introduced new gameplay systems (7-day seasonal competitive mode, team-based PvP, dispatch and multi-pet strategy systems), optimized monetization and in-game economy, and improved performance and UI (including redesigned app icon and key interfaces). Evidence Submitted We have provided the Operating Authorization Letter and Software Copyright Certificate via
Replies
1
Boosts
0
Views
172
Activity
Dec ’25
watchOS 4.3 beta 3 Activity doesn't properly sync with iOS 11.3 beta 4
On the Watch: watchOS 4.3 beta 3On the paired iPhone: iOS 11.3 beta 4Observed behavior: Activity numbers (Move/Exercise/Stand) stop updating on the Watch, until the Watch is put to Airplane mode/restarted. If nothing is done - data is lost completely. In particular, Stand hours are missing and marked as empty, like the watch was not even on the wrist during that hour. Was previously observed with watchOS 4.3 beta 2 and 1 (and iOS 11.3 beta 2 and 1), but was fine with iOS 11.3 beta 3. After iOS 11.3 was updated to beta 4 - problem occured again and stay there.Remarks: with this iPhone two Apple Watches are paired. One with watchOS 4.2.3, another one - with watchOS 4.3 beta 3. However, the Watch with watchOS 4.2.3 is completely turned off for a week already.
Replies
0
Boosts
0
Views
416
Activity
Mar ’18
3rd time rejected: Guideline 4.3(a) - Design - Spam
My app keep getting rejected after changing complete UI. It's an finance tool app. any advice Guideline 4.3(a) - Design - Spam We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. 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
Replies
1
Boosts
0
Views
271
Activity
Jul ’25
Need some help understanding 4.3(a) rejection for my app Siply
My app Siply keeps getting flagged for Guideline 4.3(a) – Spam, saying it’s “similar in binary, metadata, or concept” to other apps on the App Store. I’ve already had a call with App Review and made a ton of changes since then, obviously they won't tell me what app they think it's emulating, which doesn't really help me as a dev. I've redone both design and function, but it’s still getting rejected for the same thing. Just for context, Siply isn’t a template or copy app. It’s built from scratch with a Create ML model for container volume estimation, a custom Figma UI, and a Firebase backend for login and data. The whole interface and flow are fully custom-built. I’m just trying to figure out what part of it is being seen as “too similar” so I can fix it the right way. Could this be triggered by me having other apps under the same developer account or Firebase project? Any insight would help, I’m kinda stuck on this one.
Replies
1
Boosts
0
Views
154
Activity
Oct ’25
Reply to App Rejection for Design 4.3 – Need Help!
Hi, we are facing 4.3 rejection too. Did you find a solution to it? Can you share anything about how to overcome it?
Replies
Boosts
Views
Activity
Mar ’24
First app rejected under 4.3(a) Design – Spam despite original code and assets — appeal guidance?
My first and only app, tower defense game (App ID 6802129713), was rejected under Guideline 4.3(a) Design – Spam. I'm a solo developer; the game is built on the open-source Godot 4 engine, with all code written from scratch and all art generated by my own tools in the same repository. The core of the game is a custom simulation running up to hundreds of thousands enemies on-device, which I believe no other App Store game does. I replied in the review thread with a point-by-point response to each 4.3(a) factor and asked which app mine is believed to resemble, but received only the standard template in return, so I don't know what to change. I've filed an appeal with the App Review Board. Has anyone successfully resolved a 4.3(a) flag in a similar situation? Is there anything else I can provide to demonstrate originality?
Replies
2
Boosts
0
Views
207
Activity
Sep ’26
Reply to Can SAAS-developed template apps pass the review and be published?
Appstore Guideline 4.3 may forbid you to do so. And here are some advices on how to handle it. 4.3 Spam Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. https://developer.apple.com/app-store/review/guidelines/
Replies
Boosts
Views
Activity
Aug ’23
All 66 of My Previously Approved Apps Are Being Removed Under Guideline 4.3
Today I received 66 separate, identical App Review notices, one for every live app in my developer account, stating that each app will be removed from the App Store under Guideline 4.3. These apps were previously reviewed, approved, and live. They are not 66 versions of one product. They span substantially different concepts and functionality, including games, utilities, productivity tools, social tools, and video tools. Every notice says the app shares a similar “binary, metadata, and/or concept” with apps submitted by other developers, but does not identify what specifically triggered the finding. Because all 66 notices arrived together with identical language, this appears to be a portfolio-level re-evaluation. Could someone from App Review please clarify: Is there a way to request a review of the developer portfolio as a whole rather than appealing 66 identical decisions individually? Can App Review identify whether the finding is based primarily on binary/source similarity, metadata, concepts, o
Replies
0
Boosts
0
Views
219
Activity
Sep ’26
4.3(a) on an update to a live app with 30 approved versions — App ID 6776105247
Hi, NewTake — AI Video Editor (App ID 6776105247) has been on the App Store since June 2026 with 30 approved versions and paying subscribers; version 1.8.9 was approved on August 27, 2026. Version 1.8.10 (submission 5ac4e580-9634-431d-be60-c4580e775295), which differs from 1.8.9 only by an optional feedback text field, was rejected under Guideline 4.3(a) on August 28 and again on August 29 after a Resolution Center reply. Both responses were the guideline template and did not reference anything specific in the submission. The app is a single bundle ID with an original on-device pipeline (transcription, scene detection, false-start trimming, captions — video never leaves the phone). No other app on our account shares code, assets, or concept with it. We have filed an App Review Board appeal and requested a call. We'd be grateful for guidance on what specifically triggers 4.3(a) on an update to an already-approved app, so we can address it.
Replies
1
Boosts
0
Views
135
Activity
Aug ’26
Rejected for Guideline 4.3(a) - Spam, looking for advice on next steps
Hello, My game was rejected under Guideline 4.3(a) (Design - Spam), with the message stating that it shares a similar binary, metadata, and/or concept with other apps already submitted to the App Store. The issue is I can’t figure out where this is coming from: No shared source code, template, or assets with any other game. No duplicated metadata. The app’s concept is still fairly niche on the App Store (I could only find around a dozen apps with a similar concept, at most). I’m trying to better understand what might have triggered this rejection, and I’m fully willing to make changes if needed. Has anyone else run into this kind of rejection under similar circumstances? How did you go about clarifying things with the review team, and did requesting an App Review Appointment help in cases like this? Thanks in advance for any insight.
Replies
2
Boosts
0
Views
500
Activity
Aug ’26
No response after 4.3(a) rejection, unlisted distribution already approved
Hello, Our app (Apple ID 6797897487) is an internal operations tool built under contract for a single business. It was rejected under guideline 4.3(a) on 29 August. We replied in App Store Connect on 31 August and on 10 September, adding that Apple had approved unlisted app distribution for the app on 8 September, but we have not received any response since. What is the recommended next step here? Should we resubmit the same build with the updated information, or wait for a reply to the existing messages? Thank you.
Replies
2
Boosts
0
Views
399
Activity
4w
Reply to Repeated Guideline 4.3 Rejection for Update – Requesting Insight From Fellow Developers And App Review Team
This is amazing how they just comment the same generic response even in the forum. i am facing the exact same issue I submitted my app last week and got rejected due to 4.3. After explaining the features and uniqueness of the app, they worte Me a reply that the issue has resolved. then they rejected due to 2.3.6 , fixed that and again today they returned to say again that the app is being rejected due to 4.3. Even when I attach screenshots of their message saying it has resolved just 48 hours ago, they are still holding their ground and keep on re me. they are not even saying what in the app is breaching the 4.3 guideline. this is an absolutely disgraceful
Replies
Boosts
Views
Activity
Nov ’25