Tell us what is blocking publishing.

Three short steps. Paste what you have or attach a screenshot — we only ask for what a reviewer needs. The initial review is free; implementation, if required, is quoted separately.

Step 1 of 3 — Publishing 1/3

Step 1: Publishing
Step 2: App details
Step 3: Contact

Coming from “Android Developer Verification”: we have pre-filled what that page already tells us, so you only need to add the details. Change anything that does not match.

Which store or platform is affected?

Google Play Play Console notice or email Apple App Store App Store Connect / App Review message Not sure We will work it out

The console notice or error

Either is enough to start. A screenshot or PDF from your phone is fine; you do not have to type anything out.

Console notice, error, or description of the problem (optional)

Paste the message or describe the problem. A screenshot is fine instead. No rejection notice is needed.

Screenshot, photo or PDF of the notice (instead of, or as well as, the text)

PNG, JPG or PDF. Up to 5 files, 10 MB each. On a phone you can pick from your photos or take a picture of the screen. Stored privately and viewable only by our reviewers.

Selected (uploads when you continue):

Free initial review
No payment required
No passwords or signing keys
No source code required initially

Your submission is reviewed by our technical team. The Rejection Decoder is only preliminary automated guidance. Technical implementation, if required, is quoted separately.

Just want a quick automated reading? Try the Decoder

What happens next

Submit the details — you receive a reference.
An engineer on our technical team reads the notice and your files — not an autoresponder.
We explain the likely cause and the recommended next step.
If implementation is required, we provide a separate quote.

We’ll reply by email with our findings and the recommended next step. We will never ask you for passwords, signing keys or store credentials to do the review.

What does my free rejection review include?

Likely rejection cause
Relevant policy or guideline
What we would verify
Whether a change is likely required
Fix, reply or appeal recommendation
Recommended next step

Do not include passwords, signing keys, keystores, API secrets, recovery codes, payment credentials or personal data belonging to your users. We do not need any of these to review a rejection and we will ask you to remove them if they are included.

App Rejection Fix is independent of Google and Apple and does not guarantee outcomes.