Rejection Fixes

Fixing "Unable to Verify Use Case" and "Unable to Approve Permission" Rejections

Fixing "Unable to Verify Use Case" and "Unable to Approve Permission" Rejections

What these rejection messages actually mean, why they usually point to the screencast or test access, and how I rebuild a submission so the reviewer can confirm every step.

What “unable to verify use case” really means

These rejections are frustrating because they sound vague. In my experience, they almost always mean the same thing: the reviewer could not see enough evidence to connect the permission to a real feature. The product may be completely compliant, but the submission did not prove it.

The related message “unable to approve permission request” usually points to the same gap, sometimes combined with a scope question: the reviewer is not convinced the app needs that permission at all.

The usual causes of this Meta App Review rejection

  • The screencast skips the login and permission-grant flow.
  • The permission is mentioned in the description but never visibly used in the video.
  • The video shows the feature, but not the data that comes from or goes to Meta.
  • Test credentials did not work, required two-factor authentication, or the account was empty.
  • The use-case text describes a different flow than the one shown in the video.
  • The app was only accessible from a specific region, IP allowlist, or staging network.
  • The permission is not needed because another permission or Standard Access already covers the feature.

Diagnose before you change anything

I build a table with one row per rejected permission: the reviewer's note, the timestamp in the video where it was shown, and the sentence in the description that explains it. If any cell is empty, that is the likely cause. This takes less time than guessing, and it is the first step of my broader resubmission audit.

How to fix “unable to verify use case”

I do not just resubmit the same material with more explanation. I rebuild the evidence.

  • Rewrite each use-case description to match the video step by step, using real button labels.
  • Re-record the screencast from a logged-out state, following this screencast structure, with captions naming each permission when it is used.
  • Show both sides of the API call: the action in your app and the result in Facebook, Instagram, Messenger, or WhatsApp.
  • Prepare a reviewer account with realistic sample data so the feature looks real, not empty.
  • Test the credentials and instructions from a fresh private browser window.
  • Add numbered reviewer instructions to the submission notes.

Example: before and after a use-case description

Before: “Our platform uses instagram_manage_comments to help businesses engage with their audience.” This describes a goal, not a feature, and gives the reviewer nothing to verify.

After: “A social media manager opens the Comments page and selects an Instagram post. The app lists comments on that post using instagram_manage_comments. The manager types a reply under a comment and clicks Reply; the reply appears under the comment on Instagram. In the screencast, this is shown from 01:40 to 02:30.” The reviewer now knows the user, the screen, the action, the data, and where to look.

When the problem is the use case itself

Sometimes a “disallowed use case” rejection means the feature really does not fit the permission. Examples include using messaging permissions for unsolicited promotional messages, reading data the user did not explicitly connect, or using automation where the policy requires a human, as with the Human Agent feature. More documentation will not help. Change the product flow, use the correct permission or product, and resubmit with a clear explanation of what changed.

Preventing this rejection next time

The best fix is to make the evidence impossible to miss on the first attempt. I now write the use-case descriptions and the screencast script together, from the same permission table, so they always describe the same steps in the same order. Every description includes a timestamp pointing to the video.

I also run a short blind test before submitting: someone who did not build the feature watches the video without sound and explains what each permission does. If they hesitate on a permission, the reviewer will too. Combined with the checklist in getting approved on the first attempt, this has made “unable to verify” rejections rare in my projects.

Resubmission notes that answer the reviewer

In the notes, respond to the rejection directly and briefly: what was missing, what changed, and where to find it now. For example: “The previous video did not show the comment reply on Instagram. The new video shows it at 02:10.” A reviewer should not need to compare two submissions to understand what changed.

Frequently asked questions

Should I argue with the reviewer in the resubmission notes?

No. Acknowledge what was missing and point to the new evidence. A short, factual note works best.

Can I resubmit immediately?

You can, but resubmitting without new evidence usually leads to the same result. Fix the root cause first.

What if only one permission was rejected?

Fix that permission's evidence and resubmit. Approved permissions stay approved, so focus on the rejected ones.

Can the rejection be caused by the privacy policy?

It can contribute. Make sure the privacy policy mentions the data each permission accesses.