Guideline 5.6

Guideline 5.6 - Developer Code of Conduct: Submission Does Not Meet Quality Standard; Not Eligible for Resubmission

High SeverityHard FixTypical Fix: 1-4 weeks (appeal response plus any rebuild)1 Report

Also known as:Guideline 5.6 - Developer Code of Conduct: Your app does not meet the quality standard required for the App Store. This app is not eligible for resubmission.Guideline 5.6.4 - App Quality: The submission contains placeholder content, unfinished features, or elements that appear unintentional or unrefined. Replies and resubmissions will not be reviewed.Guideline 5.6 - Review Suspended: Due to the severity of the issue, we will not review further submissions of this app. Resubmissions will be rejected with an automated message.Guideline 5.6 - Developer Code of Conduct: Continued submission of apps with the same or similar issues may result in removal from the Apple Developer Program.Guideline 5.6 - Developer Code of Conduct: The app does not function consistently across all supported devices and does not provide a meaningful, polished, and reliable experience.

Our Take

This is one of the most severe outcomes during app review. Apple is not asking for a specific fix. It's saying the build looked unfinished, unpolished, or unreliable enough that it has closed the resubmission channel for this app record.

The wording is template language: 'meaningful, polished, and reliable,' 'placeholder content,' and 'unintentional, unfinished, or unrefined' are standard phrases. The message names no screen, crash, or defect, so a human reviewer probably escalated it using a standard block. It is not a bug-specific automated rejection.

Common root causes are an app that...

Reads as a template, shell, or thin wrapper

Has visible placeholder text, broken screens, or dead-end flows

Encounters instability on some devices (often iPad or a specific iOS version)

Has a history of earlier rejections (2.1, 4.2, 4.3, 2.3) that Apple believes went unaddressed.

The practical consequence is that replying in App Store Connect or resubmitting the same binary will not work. Apple says it will auto-reject both, and repeated attempts risk escalating this to a Developer Program License Agreement issue. For all intents and purposes, your app is effectively stuck in limbo, and you're unlikely to retrieve it.

The fastest compliant path is:

1. Stop resubmitting

2. Audit the build against Apple's four bullet points

3. Not recommended, but you can try sending one calm, factual request for clarification or reconsideration through Apple's formal appeal channel (App Review Board / Developer Support contact form)

4. If that does not reverse the decision, submit a separate, materially improved new app that's not a reskin or a copy under another account.

This preserves your business model while avoiding the account-level risk of looking like you are evading enforcement.

Resolution Guide

Stop all replies and resubmissions of this binary

Apple states these will be auto-rejected and not reviewed. Repeated attempts add to the record and raise the risk of account-level action. Do not upload the same build, a lightly modified build, or a copy under another account or bundle ID.

Review your full rejection history

Check App Store Connect for earlier rejections on this app and others in your account (2.1, 2.3, 4.2, 4.3, 5.6). A 5.6 suspension often follows a pattern. Note anything Apple flagged before that may not have been fully addressed.

Run a strict quality audit against Apple's four bullet points

Walk through every screen on real hardware, on the oldest and newest supported iOS versions, and on both iPhone and iPad if the app is universal. Look for placeholder text or images, lorem ipsum, dead buttons, empty states with no guidance, broken links, inconsistent UI, crashes, and features that are advertised but not functional. Also confirm the app offers real functionality beyond a web wrapper or template.

Document the audit and any improvements

Prepare a short, factual summary: what the app does, who it is for, what you verified, and what you changed. Include a clean demo video and, if applicable, working demo credentials. Keep it concise and neutral.

NOT RECOMMENDED: Send one formal request for clarification or reconsideration

Use Apple's formal appeal route (App Review Board appeal or the Contact Us / Developer Support form), not the App Store Connect reply thread. State that the notice cites no specific screen, defect, or guideline requirement. Note that 5.6.4 describes quality signals such as excessive customer reports, negative reviews, and refund requests, none of which apply to a pre-release submission. Ask Apple to identify the specific issues, or to reconsider. Offer targeted fixes if specifics are provided. Keep the tone calm and professional, with no accusations. Send it once.

Submit a separate, materially improved new app

Apple's own next steps allow a new submission after the listed actions are taken. This must be a genuine rebuild, with distinct functionality, original design, complete content, and stable behavior across devices. A reskin, renamed duplicate, or minor edit would be treated as 'the same or similar issues.' Reference your improvements in the App Review notes.

Escalate only through sanctioned channels

If you receive no response, follow up through Developer Support or request a call. Do not create new developer accounts to bypass the suspension. That would likely lead to termination.

Prevention

Run a pre-submission QA checklist covering placeholder content, empty states, and dead-end flows on every screen.

Test on multiple physical devices and OS versions, including iPad if the app is universal.

Resolve every prior rejection fully before resubmitting, rather than making minimal edits to get past review.

Ensure the app provides unique, substantial functionality and not a template or thin web wrapper.

Provide complete App Review notes, demo credentials, and a walkthrough video.

Use TestFlight with external testers to catch polish and stability issues before review.

Example Rejection Email

From:Apple App Review Team

Subject:Guideline 5.6 - Developer Code of Conduct: Submission Do

Guideline 5.6 - Developer Code of Conduct - Review Suspended This app is not eligible for resubmission at this time. See below for more information. Upon review, the current submission does not meet the required quality standard for distribution on the App Store. Apps submitted to the App Store must provide a meaningful, polished, and reliable experience for customers. Due to the severity of this issue, this app is not eligible for resubmission. Replies and resubmissions will not be reviewed. Resubmissions will be rejected with an automated message. Next Steps If you choose to submit a new app for review, take the following actions first: - Ensure every screen, interaction, and piece of content has been thoughtfully designed, reviewed, and tested prior to submission. - The app should offer a well-executed experience that appeals to an App Store audience. - Confirm that the app is free of inconsistencies, placeholder content, or elements that appear unintentional, unfinished, or unrefined. - Verify the app is stable and delivers a consistent, high-quality experience across all supported devices. Customers expect apps they download to function on all the devices where they are available. Continued submissions of apps that violate the App Review Guidelines, including submitting new apps with the same or similar issues, will be treated as a violation of the Apple Developer Program License Agreement and may result in removal from the Apple Developer Program.

Consider Appealing

An appeal is viable but narrow, and it must go through Apple's formal channel (App Review Board or Developer Support), not the App Store Connect reply thread Apple says it will ignore. The notice cites no specific screen, defect, or guideline requirement, so the developer can reasonably ask for specifics. The only quality-related text in 5.6 is 5.6.4, which describes signals like excessive customer reports, negative reviews, and refund requests. A pre-release submission has none of these, so the 'severity' behind the suspension is not explained by the written guideline. Treat this as a request for clarification and reconsideration, not a guaranteed reversal. Apple has discretion here, so run the quality audit and prepare a rebuilt app in parallel.

Generate Appeal

Before & After

Before — Rejected

The app has a settings screen with 'Lorem ipsum' text, a dead 'Upgrade' button, and an empty tab that shows a blank page.

After — Approved

Every screen has final copy, every button leads to a working flow, and empty states show helpful guidance and a clear next action.

What changed: Removes the placeholder and unfinished elements Apple names as grounds for the quality finding.

Before — Rejected

The app was tested only on one recent iPhone, and it crashes on iPad and on older supported iOS versions.

After — Approved

The app is tested on multiple physical iPhone and iPad models and on the minimum supported iOS version, with all crashes and layout issues fixed.

What changed: Addresses Apple's requirement that the app work consistently on all supported devices.

Before — Rejected

The submission is a lightly customized template or web wrapper with generic content and minimal native functionality.

After — Approved

The new app has original design, distinct native functionality, and complete content that serves a clear user need.

What changed: Shows a meaningful, differentiated experience rather than a 'same or similar' submission.

Before — Rejected

The developer resubmits the same binary with a short reply in App Store Connect.

After — Approved

The developer stops resubmitting and sends one concise appeal through the formal channel, or submits a materially improved new app.

What changed: Avoids automated rejections and the risk of a License Agreement violation.

Community Solutions · 0

More Guideline 5 (Legal) rejections

View all Guideline 5 rejections