Rejection Fixes

Before You Resubmit: My Audit Process After a Meta App Review Rejection

Before You Resubmit: My Audit Process After a Meta App Review Rejection

Resubmitting quickly with small changes often leads to the same rejection. This is the structured audit I run before sending an app back to review.

Why fast resubmission after a rejection usually fails

After a rejection, the natural reaction is to tweak the description and resubmit the same day. That rarely works. The reviewer had a specific reason, and unless the evidence changes, the outcome usually does not. Each repeat rejection also adds another review cycle to the timeline.

I treat every rejection like a production incident: find the root cause, fix it, verify the fix, and only then ship again. The process below is the one I use.

Step 1: Map the rejection to individual permissions

I build a small table with one row per requested permission: approved or rejected, the reviewer's note, the timestamp in the video where it was shown, and the sentence in the description that explains it. Gaps in this table usually reveal the problem immediately.

Permission                 Status    Reviewer note           Video   Description
pages_messaging            approved  -                       01:10   Inbox reply
instagram_manage_comments  rejected  unable to verify        -       Comment replies
pages_read_engagement      rejected  not needed for feature  02:40   Post insights

Step 2: Classify the cause

Step 3: Fix the cause, not the wording

Each category has a different fix. Evidence problems need a new screencast. Access problems need a new reviewer account and tested instructions. Policy problems need a product change. Configuration problems need settings fixed. Scope problems need the permission removed.

Only after the fix do I rewrite the descriptions, so they describe the new reality. Changing wording without changing evidence is the most common reason for a second rejection.

Step 4: Re-test the whole submission, not just the fix

A fix in one area can break another. A new build may change a button label in the video, or a new reviewer account may lack sample data. Before resubmitting, I repeat the complete pre-submission checklist from the first-attempt approval guide, including a fresh private-window test of the reviewer flow.

Step 5: Write resubmission notes in the reviewer's language

In the notes, I answer the rejection reason directly: what was missing and where it can now be found, with timestamps. For example: “The previous screencast did not show replies appearing on Instagram. The new video shows this at 02:15 for instagram_manage_comments.” A reviewer should not need to compare two submissions to understand what changed.

A worked example of the audit

Imagine an inbox product requests three permissions and two are rejected. In the permission table, the comment management permission has a description but no video timestamp, because the recording showed comments in the app but never on Instagram. That is an evidence problem, fixed by recording the reply appearing under the Instagram post.

The engagement permission was rejected as not needed. Checking the code shows it was added for an analytics feature that was postponed. That is a scope problem, fixed by removing the permission. The resubmission now contains one permission with new evidence and a short note explaining what changed. It is a smaller, clearer submission, which is exactly what a reviewer wants to see.

The audit took about an hour. Resubmitting the original material with longer descriptions would have taken ten minutes, and would most likely have failed again for the same two reasons.

Patterns I see after repeated rejections

  • Too many permissions in one submission, so one weak permission drags down the review. Split them if they serve unrelated features.
  • Screencasts recorded in a developer environment that the reviewer cannot access.
  • Descriptions written by someone who did not record the video, so they describe different steps.
  • Policy mismatches hidden behind good evidence, such as promotional messaging framed as support.

When a submission has been rejected two or three times, I start again from the permission table instead of patching the old submission. A clean rebuild is usually faster than another round of small edits.

Frequently asked questions

How many times can I resubmit for Meta App Review?

There is no small fixed limit, but each attempt adds time and history. Fix the root cause before each resubmission.

Do approved permissions stay approved after a partial rejection?

Yes, approved permissions remain approved. Focus the resubmission on the rejected ones.

Should I remove rejected permissions?

If the feature does not truly need them, yes. Removing unnecessary permissions often leads to faster approval of the rest.

Can a policy problem be fixed with a better video?

No. If the use case is not allowed, change the product flow or use the correct product, then resubmit.