Multiple rejection reasons — are these AND or OR?

Hey everyone,

I’m looking for a sanity check on a recent app rejection.

I received multiple rejection reasons in a single review, including:

  • manipulative ranking language in tool descriptions

  • destructiveHint mismatch

  • privacy policy gaps and undisclosed returned data

  • disallowed commerce

  • safeguard bypass concerns

The confusing part is that I don’t believe my app actually violates any of these (at least not intentionally), so I’m trying to understand whether:

  1. These reviews are typically “AND” logic (i.e., all issues must be fixed), or if sometimes they’re more “OR” / templated feedback

  2. Others have received multiple seemingly unrelated rejection reasons in one review

  3. In your experience, were these issues actually present but subtle (e.g., hidden fields, interpretation differences), or did you find cases of false positives?

I’m planning a full audit before resubmitting, but would love to learn from others who’ve gone through similar feedback.

Appreciate any pointers :folded_hands:

Welcome to the dev community @upplai

This Help Center article may be helpful as background, since it covers the app review process and explains a number of the rejection reasons that can appear in these cases.

It does not seem to directly resolve the main question about whether multiple rejection reasons are “and” or “or,” but it does help clarify what each listed issue means.

I’ll also try to gather more information so I can help give a more definitive answer on how to interpret review feedback like this.

1 Like