Post

Replies

Boosts

Views

Activity

Unexpected 4.3 (Spam) rejection for an fully original application
Hello. Our application was rejected under Guideline 4.3, but the rejection does not identify any specific functionality, design element, or metadata that allegedly violates the guideline. Our application is not a template, clone, white-label, or reskinned product. The application was developed entirely in-house by our company. All source code is owned by our company. The application uses our own backend infrastructure and servers. It implements our proprietary technology with intelligent routing, unique to the market. The UI/UX was designed specifically for this product and is not based on another application. This is the only application based on this codebase. This is first app from our company. We have asked App Review to identify the specific basis for the 4.3 determination and requested a manual review, but so far have only received the standard rejection. Please explain why the original application was rejected as spam if it is clearly not? Is the initial review performed entirely by a human reviewer, or are automated systems also involved in identifying potential issues?
5
1
216
1w
Organization Account Holder receives no response from Developer Support and app remains Waiting for Review
Our organization’s app has remained in Waiting for Review since 14 July 2026 We submitted multiple Developer Support requests by email and requested phone callbacks, also we request expedited review, but received no response and no callback. The support endpoint has also returned failed response for create issue: resultCode 1200 (Account Holder not allowed to perform operation) resultCode 35 (missing solutionsOffered) The Developer Program membership is active and the requests were submitted by the Organization Account Holder. Our company is incurring financial losses due to prolonged infrastructure downtime while our app remains in the App Review queue. Could Apple verify whether our Developer Team support authorization or App Review queue is affected by a technical issue?
1
0
173
1w
Unexpected 4.3 (Spam) rejection for an fully original application
Hello. Our application was rejected under Guideline 4.3, but the rejection does not identify any specific functionality, design element, or metadata that allegedly violates the guideline. Our application is not a template, clone, white-label, or reskinned product. The application was developed entirely in-house by our company. All source code is owned by our company. The application uses our own backend infrastructure and servers. It implements our proprietary technology with intelligent routing, unique to the market. The UI/UX was designed specifically for this product and is not based on another application. This is the only application based on this codebase. This is first app from our company. We have asked App Review to identify the specific basis for the 4.3 determination and requested a manual review, but so far have only received the standard rejection. Please explain why the original application was rejected as spam if it is clearly not? Is the initial review performed entirely by a human reviewer, or are automated systems also involved in identifying potential issues?
Replies
5
Boosts
1
Views
216
Activity
1w
Organization Account Holder receives no response from Developer Support and app remains Waiting for Review
Our organization’s app has remained in Waiting for Review since 14 July 2026 We submitted multiple Developer Support requests by email and requested phone callbacks, also we request expedited review, but received no response and no callback. The support endpoint has also returned failed response for create issue: resultCode 1200 (Account Holder not allowed to perform operation) resultCode 35 (missing solutionsOffered) The Developer Program membership is active and the requests were submitted by the Organization Account Holder. Our company is incurring financial losses due to prolonged infrastructure downtime while our app remains in the App Review queue. Could Apple verify whether our Developer Team support authorization or App Review queue is affected by a technical issue?
Replies
1
Boosts
0
Views
173
Activity
1w