<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Revamp Space</title>
    <description>The latest articles on DEV Community by Revamp Space (@revamp_space).</description>
    <link>https://dev.to/revamp_space</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4249019%2Ff1813f16-91b7-48ef-a5fc-998cd0f59042.png</url>
      <title>DEV Community: Revamp Space</title>
      <link>https://dev.to/revamp_space</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/revamp_space"/>
    <language>en</language>
    <item>
      <title>Meta App Review Rejected Your App? A 6-Step Fix and the Most Common Reasons</title>
      <dc:creator>Revamp Space</dc:creator>
      <pubDate>Tue, 17 Nov 2026 06:26:13 +0000</pubDate>
      <link>https://dev.to/revamp_space/meta-app-review-rejected-your-app-a-6-step-fix-and-the-most-common-reasons-2eil</link>
      <guid>https://dev.to/revamp_space/meta-app-review-rejected-your-app-a-6-step-fix-and-the-most-common-reasons-2eil</guid>
      <description>&lt;p&gt;Your app works perfectly in Development mode. You submit it for App Review. A few days later every permission comes back &lt;strong&gt;rejected&lt;/strong&gt;, with a one-line note.&lt;/p&gt;

&lt;p&gt;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 &lt;strong&gt;proof&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Not affiliated with Meta. Meta makes every App Review decision, and dashboard names change often – always re-check &lt;a href="https://developers.facebook.com" rel="noopener noreferrer"&gt;developers.facebook.com&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  How a reviewer actually checks your app
&lt;/h2&gt;

&lt;p&gt;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:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Read&lt;/strong&gt; your permission explanation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch&lt;/strong&gt; your screencast – often without sound&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Try&lt;/strong&gt; to log in with the test account you gave them&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check&lt;/strong&gt; your privacy policy, terms and data deletion URLs&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decide&lt;/strong&gt; – per permission&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Reviewers don't read your code. They judge only what they can see and try. &lt;strong&gt;Getting stuck at any one of these steps is enough for a rejection.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One more trap: in Development mode every permission "works" because you're the admin. App Review decides whether &lt;em&gt;other people's&lt;/em&gt; accounts can use it (Advanced Access). Passing locally proves nothing to the reviewer.&lt;/p&gt;




&lt;h2&gt;
  
  
  The rejection reasons I see most often
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Screencast
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The consent screen never appears.&lt;/strong&gt; 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.
&lt;strong&gt;Fix:&lt;/strong&gt; remove the app in Instagram/Facebook/Threads → Settings → &lt;em&gt;Apps and websites&lt;/em&gt;, disconnect it in your app, then record from a disconnected state.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The end result is never shown.&lt;/strong&gt; For a publishing permission, the reviewer wants to see the post live on Instagram/Facebook/Threads – not just a "Success" toast in your app.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One long video for every permission.&lt;/strong&gt; Cut one clip per permission, each focused on where that permission is used.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unreadable or local-language UI.&lt;/strong&gt; 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. &lt;code&gt;User publishes – instagram_business_content_publish&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No audio needed.&lt;/strong&gt; Meta says reviewers don't listen, so put everything in on-screen text.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Reviewer access
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;"Unable to log in."&lt;/strong&gt; The most avoidable one. Reviewers can't receive your OTP, magic link or SMS code.
&lt;strong&gt;Fix:&lt;/strong&gt; a dedicated &lt;code&gt;reviewer@yourdomain.com&lt;/code&gt; account with &lt;strong&gt;email + password&lt;/strong&gt;, pre-confirmed, and a direct link to the password tab (e.g. &lt;code&gt;/login?method=password&lt;/code&gt;). Test it from an incognito window on another network.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Features behind a paywall or waitlist.&lt;/strong&gt; Give the reviewer account your top plan and beta access. Never ask them to pay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Geo-blocks, captchas, bot protection.&lt;/strong&gt; Reviewers can connect from any country.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Permission explanations
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Too generic.&lt;/strong&gt; "We need this permission for our app to work" explains nothing. Neither does "to improve user experience".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Requested "for later".&lt;/strong&gt; If the feature isn't built and visible in the video, don't request the permission yet.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A structure that works – I call it &lt;strong&gt;A-F-T-B&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A&lt;/strong&gt;ction – what the user does ("The user clicks &lt;em&gt;Post now&lt;/em&gt;…")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;F&lt;/strong&gt;eature – where in the app ("…in the editor…")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;T&lt;/strong&gt;arget data – what Meta data/action is used, and what is &lt;em&gt;not&lt;/em&gt; ("…we publish the image and caption; we do not read followers or messages…")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;B&lt;/strong&gt;enefit – why it helps the user ("…so small businesses can plan a week of content in one sitting.")&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Legal &amp;amp; data
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Privacy policy doesn't mention Meta data.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Policy not reachable.&lt;/strong&gt; It must load publicly on your own domain – no login, no Google Docs link, no popup covering it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No data deletion path.&lt;/strong&gt; Either a public instructions page or a Data Deletion Callback that verifies Meta's &lt;code&gt;signed_request&lt;/code&gt; and returns a status &lt;code&gt;url&lt;/code&gt; + &lt;code&gt;confirmation_code&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inconsistent answers.&lt;/strong&gt; Your form, privacy policy and Data Handling answers must say the same thing. Reviewers compare them.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Technical &amp;amp; admin
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No successful test API call.&lt;/strong&gt; 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 &lt;em&gt;Request advanced access&lt;/em&gt; button stays grey.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business Verification not done&lt;/strong&gt;, redirect URI mismatch (even a trailing dot breaks it), or an app name/icon that uses Meta branding.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The video only shows the Graph API Explorer.&lt;/strong&gt; It's fine for the test API call, but it doesn't prove &lt;em&gt;your&lt;/em&gt; feature.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  The 6-step fix routine after a rejection
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Read the notes per permission.&lt;/strong&gt; Open each permission in App Review – notes are written per permission. Copy them into a &lt;code&gt;submission-log.md&lt;/code&gt; with the date.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Diagnose.&lt;/strong&gt; Match the keywords ("screencast", "unable to log in", "not demonstrated", "privacy policy", "not necessary") to the reasons above.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix the app, not just the text.&lt;/strong&gt; If the reviewer couldn't log in, rewording a sentence changes nothing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-record the proof.&lt;/strong&gt; Start disconnected, show the full consent screen, show the result on the Meta platform, re-test the reviewer login from a clean browser.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write a short resubmission note.&lt;/strong&gt; Say exactly what changed, with timestamps:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   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]).
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Resubmit your core permissions first.&lt;/strong&gt; Passing with 2 permissions and adding more later is usually faster than being rejected with 6 at once. Never resubmit the same thing unchanged.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;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, &lt;strong&gt;reconnect the account to get a fresh token&lt;/strong&gt; – on one of my apps, the newly approved feature only started working after re-authorising.&lt;/p&gt;




&lt;h2&gt;
  
  
  A 2-minute pre-submit checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Every permission maps to one real feature you can show in ≤30 seconds of video&lt;/li&gt;
&lt;li&gt;[ ] Test API call succeeded for each permission in the last 30 days&lt;/li&gt;
&lt;li&gt;[ ] Reviewer account: email + password, all features unlocked, tested today in incognito&lt;/li&gt;
&lt;li&gt;[ ] Screencast starts disconnected, consent screen fully visible, result shown on the Meta platform&lt;/li&gt;
&lt;li&gt;[ ] One clip per permission, English captions with permission names&lt;/li&gt;
&lt;li&gt;[ ] Privacy policy names Meta data per platform; terms and data deletion are public&lt;/li&gt;
&lt;li&gt;[ ] Explanations follow Action → Feature → Target data → Benefit&lt;/li&gt;
&lt;li&gt;[ ] Business name identical in documents, Business portfolio, website and policy&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Want the full version?
&lt;/h2&gt;

&lt;p&gt;I turned everything above into a 50-page guide, &lt;strong&gt;Pass Meta App Review&lt;/strong&gt;: 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.&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://revspace.gumroad.com/l/wmajer?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=meta_app_review" rel="noopener noreferrer"&gt;Pass Meta App Review on Gumroad&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;What rejection note did you get? Drop it in the comments and I'll tell you what I'd fix first.&lt;/p&gt;

</description>
      <category>instagram</category>
      <category>api</category>
      <category>webdev</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
