Your app works perfectly in Development mode. You submit it for App Review. A few days later every permission comes back rejected, with a one-line note.
I've been through this on real submissions – one approved the day after submitting, one rejected on the first try. The difference was almost never the code. It was the proof.
This post is the short version of what I learned: how reviewers actually check your app, the rejection reasons I see most often, and a 6-step routine to fix and resubmit.
Not affiliated with Meta. Meta makes every App Review decision, and dashboard names change often – always re-check developers.facebook.com.
How a reviewer actually checks your app
Picture someone busy, checking many apps a day, who has never heard of your product and may not speak your language. For each permission they:
- Read your permission explanation
- Watch your screencast – often without sound
- Try to log in with the test account you gave them
- Check your privacy policy, terms and data deletion URLs
- Decide – per permission
Reviewers don't read your code. They judge only what they can see and try. Getting stuck at any one of these steps is enough for a rejection.
One more trap: in Development mode every permission "works" because you're the admin. App Review decides whether other people's accounts can use it (Advanced Access). Passing locally proves nothing to the reviewer.
The rejection reasons I see most often
Screencast
- The consent screen never appears. You recorded with an account that was already connected, so Meta skipped the permission screen ("You previously logged in…"). The reviewer never sees the permission being granted. Fix: remove the app in Instagram/Facebook/Threads → Settings → Apps and websites, disconnect it in your app, then record from a disconnected state.
- The end result is never shown. For a publishing permission, the reviewer wants to see the post live on Instagram/Facebook/Threads – not just a "Success" toast in your app.
- One long video for every permission. Cut one clip per permission, each focused on where that permission is used.
-
Unreadable or local-language UI. Record at 1080p, browser zoom 110–125%, pause after each click, and add English captions that name the permission at the moment it's used, e.g.
User publishes – instagram_business_content_publish. - No audio needed. Meta says reviewers don't listen, so put everything in on-screen text.
Reviewer access
-
"Unable to log in." The most avoidable one. Reviewers can't receive your OTP, magic link or SMS code.
Fix: a dedicated
reviewer@yourdomain.comaccount with email + password, pre-confirmed, and a direct link to the password tab (e.g./login?method=password). Test it from an incognito window on another network. - Features behind a paywall or waitlist. Give the reviewer account your top plan and beta access. Never ask them to pay.
- Geo-blocks, captchas, bot protection. Reviewers can connect from any country.
Permission explanations
- Too generic. "We need this permission for our app to work" explains nothing. Neither does "to improve user experience".
- Requested "for later". If the feature isn't built and visible in the video, don't request the permission yet.
A structure that works – I call it A-F-T-B:
- Action – what the user does ("The user clicks Post now…")
- Feature – where in the app ("…in the editor…")
- Target data – what Meta data/action is used, and what is not ("…we publish the image and caption; we do not read followers or messages…")
- Benefit – why it helps the user ("…so small businesses can plan a week of content in one sitting.")
Legal & data
- Privacy policy doesn't mention Meta data. Generic generators skip it. List what you receive per platform (user ID, username, access token, user-created content…), why, where it's stored, for how long, and how to delete it.
- Policy not reachable. It must load publicly on your own domain – no login, no Google Docs link, no popup covering it.
-
No data deletion path. Either a public instructions page or a Data Deletion Callback that verifies Meta's
signed_requestand returns a statusurl+confirmation_code. - Inconsistent answers. Your form, privacy policy and Data Handling answers must say the same thing. Reviewers compare them.
Technical & admin
- No successful test API call. Meta requires at least one successful call for each permission you request Advanced Access for, within the 30 days before submitting. It can take up to 2 days to show up; until then the Request advanced access button stays grey.
- Business Verification not done, redirect URI mismatch (even a trailing dot breaks it), or an app name/icon that uses Meta branding.
- The video only shows the Graph API Explorer. It's fine for the test API call, but it doesn't prove your feature.
The 6-step fix routine after a rejection
-
Read the notes per permission. Open each permission in App Review – notes are written per permission. Copy them into a
submission-log.mdwith the date. - Diagnose. Match the keywords ("screencast", "unable to log in", "not demonstrated", "privacy policy", "not necessary") to the reasons above.
- Fix the app, not just the text. If the reviewer couldn't log in, rewording a sentence changes nothing.
- Re-record the proof. Start disconnected, show the full consent screen, show the result on the Meta platform, re-test the reviewer login from a clean browser.
- Write a short resubmission note. Say exactly what changed, with timestamps:
1. Screencast: re-recorded from a disconnected state. The Instagram
permission screen is visible at 0:25–0:50; the published post is
shown on Instagram at 2:05.
2. Login: the test account now signs in with email + password at
https://yourapp.example/login?method=password (verified on [date]).
- Resubmit your core permissions first. Passing with 2 permissions and adding more later is usually faster than being rejected with 6 at once. Never resubmit the same thing unchanged.
While you wait: freeze the UI, legal pages and reviewer account. Changing button labels or the password mid-review makes your video and instructions wrong. And after approval, reconnect the account to get a fresh token – on one of my apps, the newly approved feature only started working after re-authorising.
A 2-minute pre-submit checklist
- [ ] Every permission maps to one real feature you can show in ≤30 seconds of video
- [ ] Test API call succeeded for each permission in the last 30 days
- [ ] Reviewer account: email + password, all features unlocked, tested today in incognito
- [ ] Screencast starts disconnected, consent screen fully visible, result shown on the Meta platform
- [ ] One clip per permission, English captions with permission names
- [ ] Privacy policy names Meta data per platform; terms and data deletion are public
- [ ] Explanations follow Action → Feature → Target data → Benefit
- [ ] Business name identical in documents, Business portfolio, website and policy
Want the full version?
I turned everything above into a 50-page guide, Pass Meta App Review: 34 rejection reasons with a fix for each, screencast scripts per permission, English templates for every form field, 15 copy-paste Claude prompts (privacy policy, deletion callback, test instructions, consistency audit) and a printable final checklist.
👉 Pass Meta App Review on Gumroad
Disclosure: I'm the author of the guide. The post above is meant to be useful on its own – if it helps you pass, that's the point.
What rejection note did you get? Drop it in the comments and I'll tell you what I'd fix first.
Top comments (0)