Repeated Guideline 5.6 Rejections With No Specific Reason — Appeal Also Unanswered

Hi Apple Developer Community,

I'm hoping someone from the App Review community or Apple can help me understand what may be happening with our app.

Our educational app has now been rejected multiple times under Guideline 5.6 — Developer Code of Conduct.

The problem is that we have not received a specific explanation identifying which feature, behavior, or part of the app is considered a violation.

We have carefully reviewed the rejection and made sure that there are no features intentionally hidden from App Review. The functionality available to the reviewer is available to normal users as well.

We have already:

Replied to the App Review rejection asking for the specific reason. Submitted an appeal explaining the situation. Asked Apple to identify the specific feature or behavior that triggered Guideline 5.6.

However, we have not received a response to either the appeal or our message in the App Review/Resolution Center yet.

About the app:

This is an educational application used by students for exam preparation. The upcoming examination period is approaching, and students are currently waiting for access to the application and its preparation materials. This makes the situation particularly time-sensitive for us.

We are willing to make any changes required by Apple, but without knowing what behavior triggered 5.6, we don't want to keep making random changes and repeatedly resubmitting the same app.

My questions are:

  • What kinds of situations typically result in a 5.6 rejection when Apple does not specify a particular feature?
  • Is there anything specific we should check in our app or review configuration?
  • Is there a way to obtain clarification on the exact 5.6 concern while the appeal is pending?
  • Should we wait for the appeal response before submitting another build?

We would really appreciate any guidance. We are not trying to bypass App Review — we simply want to understand the specific issue so we can fix it correctly and provide students access before their exams.

Thank you.

Common Triggers for Guideline 5.6 Rejections

Aggressive or Deceptive Paywalls: Using exit discount offers (dropping the price the moment a user tries to close the paywall) or showing back-to-back paywalls during onboarding.

Asking for Ratings Too Early: Requesting an App Store rating or review during the initial onboarding flow or on the very first launch (violating Guideline 5.6.3 enforcement).

AI-Generated or Template-Like Behavior: Rapidly submitted AI wrappers or apps sharing generic binary structures that automated filters flag as suspicious or low-effort.Remote Configuration / Feature Flags: Using services like Firebase

Remote Config or dynamic script bridges where functionality could theoretically change post-approval, which automated scanners mistake for hidden code.

Incomplete Metadata or Placeholder Content: Leaving dummy text, "coming soon" placeholders, or failing to supply clear login credentials/demo modes for review.

Goodluck.

if your code is on github - I would hook up codex or some other AI to your repo and ask it to review your code base in comparison to apples guidelines. It is usually good at finding the items you might be overlooking.

Repeated Guideline 5.6 Rejections With No Specific Reason — Appeal Also Unanswered
 
 
Q