Guideline 5.6 Rejection with NO Screenshots or Crash Logs – How to Diagnose?

Question

Created 15h

Replies 6

Boosts 2

Participants 7

Hi everyone,

I'm a relatively new developer and I just received my first App Store rejection. I'm posting here because I'm genuinely stuck and hoping the community can help me figure out where to even begin.

The Problem:

My app was rejected under Guideline 5.6 - Developer Code of Conduct - Review Suspended. The full message is the standard one: the app doesn't meet the "required quality standard," it's "not eligible for resubmission," and I should "ensure every screen, interaction, and piece of content has been thoughtfully designed" before submitting a new app.

Here's why I'm confused:

The rejection came with ZERO attachments. No screenshots. No screen recordings. No crash logs. No specific mention of a buggy feature, a broken button, or an unfinished screen. It's just a blanket statement about "quality" and "polish."

in my case, there's absolutely nothing to go on.

What I've checked so far:

I've tested the app on multiple physical devices (iPhone 12, 14, 15) – no crashes.

I've reviewed every screen for placeholder text, "Lorem Ipsum," or dummy images – none found.

I've checked the In-App Purchase / subscription screen for proper legal disclaimers and auto-renewal text – all present.

I've made sure there are no debug logs or test toggles left in the production build.

Everything looks fine to me, which is why I'm so lost. Without specific feedback, I don't know if the issue is:

A UI inconsistency I'm blind to?

A subtle crash that only happens on a device I don't own?

An issue with the paywall flow that I've misunderstood?

Something about the metadata, screenshots, or app description?

My questions for the community: Has anyone else received a Guideline 5.6 rejection with no attachments? Is this common, or does it suggest the reviewer flagged the app as "low-quality" purely based on first impressions (like the design feels outdated or the concept is too simple)?

Since the message says replies and resubmissions of this binary won't be reviewed, and I can't get clarification from the reviewer, what's the safest way to proceed? Should I: Create a completely new App ID and submit as a new app?

Or can I submit a new version under the same App ID? (I've heard mixed answers on this.)

More importantly – how do I figure out what to fix?

Without a starting point, I'm worried I'll fix the wrong things and get rejected again, which I know can lead to account termination after repeated violations. Are there any "hidden" quality checks that reviewers apply that aren't obvious to developers? For example, does Apple penalize apps that:

Have a generic icon or unpolished splash screen? Take too long to load on first launch?

Have unclear navigation or confusing user flow?

Lack a proper onboarding/tutorial for first-time users?

Thanks in advance for any help you can offer. I really want to get this right and not waste my one or two remaining chances.

my app id : 6764726742

Answer 1

AntonSorokin OP

12h

I received a rejection today with exactly the same text, and I have no idea what to do about it, interesting

Answer 2

NarekBayunts OP

9h

My App got rejected for the same reason, but UI, all the interaction flows and purchases were tested and polished properly. I got no useful info why it was rejected. My app id: 6775957885

Answer 3

rctacbad OP

7h

I received my first rejection as well for my first app. Also confused about what specifically is lacking quality with my app as there were no details provided.

Answer 4

Claude31 OP

2h

Should I: Create a completely new App ID and submit as a new app?

I do recommend NOT to do so. That would create more confusion, with a risk of being flagged as spam… Or worse, considered as "manipulative or misleading behavior or other fraudulent conduct will lead to your removal from the Apple Developer Program"

Impossible to speak for the reviewer, but some thoughts, hoping it will help.

What type of an app is ? Is it a paying app ? Does it include purchase or subscription ?

Have you checked your app on various simulators (different sizes, iPhone, iPad, Portrait and landscape) ?

Could you go to test flight ? Or at least test your app with a few other people. Their genuine comment may help you understand the issue.

After this, you could either appeal the review or resubmit, explaining what you have done since rejection in the comments to reviewer. Take care to use soft wording, not complaining or criticising the review process in those comments, but just be very factual.

Answer 5

App Review OP

Apple

1h

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to:

Provide specific reasons why you believe your app complies with the App Review Guidelines.
Submit only one appeal per rejection.
Respond to any requests for additional information before submitting an appeal.

Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Answer 6

Etresoft OP

51m

in my case, there's absolutely nothing to go on.

No one here knows anything about your app. It's obvious that Apple did give you feedback. You literally quoted them.

what's the safest way to proceed?

Again, that's obvious. Submit a newly designed app that Apple wants to have in the store.

Apple has publicly announced, through its updated App Review Guidelines and social media outreach, that it intends to try to raise the quality of apps in the store.

There's no mystery here. We all know what's going on and has been going on for years. It's unfortunate that Apple waited so long to take action.