Meta App Review
Test Credentials and Reviewer Access: The Silent Cause of Many Rejections
If the reviewer cannot get into the app, nothing else in the submission matters. How I prepare test access that works the first time.
Why reviewer access problems cause so many rejections
Products in development often sit behind invite-only signups, two-factor authentication, IP allowlists, or paid plans. These are sensible for production, but they block a reviewer who is trying to verify a feature. Many rejections that say a use case could not be verified are actually access failures.
The reviewer does not contact you to ask for a code or an invite. If they cannot get in, the review ends, and you wait for another full cycle.
Test credentials checklist for Meta App Review
- Create a dedicated reviewer account with a stable password that does not expire.
- Disable two-factor authentication and email verification for that account only.
- Give the account an active plan or trial so every feature in the submission is unlocked.
- Add realistic sample data so screens are not empty.
- Remove IP restrictions, VPN requirements, and region blocks for the review environment.
- For mobile apps, provide a build the reviewer can install, such as a TestFlight invite or an APK link, with clear install steps.
- Keep the account active for the entire review period and do not reset its data.
Connecting Meta assets for the reviewer
Many features need a connected Page, Instagram professional account, or WhatsApp number. The reviewer usually logs in with their own test Facebook account, which may not manage any assets. Decide in advance how the reviewer will see the feature work.
- If the flow requires connecting a Page, explain that the reviewer can create or use a test Page, and show the full connection flow in the screencast.
- If your app already has a connected test Page, explain which actions the reviewer can perform, such as sending a message to that Page.
- For WhatsApp, provide a test number and the exact message to send to trigger the flow.
- Never share personal Facebook passwords. Use test assets created for the review.
Write step-by-step reviewer instructions
In the submission notes, I write short numbered steps: where to log in, which button connects the Meta account, and where each feature lives. If the reviewer needs to send a message to a test Page or WhatsApp number to trigger a flow, I say exactly which account and what to send.
1. Open https://app.example.com/login
2. Sign in with reviewer@example.com / ReviewPass-2026
3. Click Connect Facebook and approve the requested permissions
4. Select the Page 'Example Support (Test)'
5. Open Inbox. Send 'Hello' to the Page from Messenger;
it appears in Inbox within a few seconds
6. Type a reply and click Send (uses pages_messaging)Those are illustrative values. Use real reviewer credentials in your submission, and keep them separate from any production admin account.
Test it like a stranger before submitting
Before submitting, I open a private browser window and follow my own instructions word by word. If anything requires knowledge that is not written down, I fix the instructions or the product. Ideally, someone who did not build the feature does this test. It takes ten minutes and prevents a multi-week delay.
Preparing realistic sample data
Empty screens are weak evidence. If the reviewer opens an inbox with no conversations or an analytics page with no data, they cannot see what the feature does. I seed the reviewer account with realistic sample data: a few customers, conversations with plausible messages, a booking or order history, and any settings the feature depends on.
The data should look real but contain no personal information from actual customers. I use a seed script so the same data can be recreated in seconds if anything is changed or deleted during testing. The script lives in the repository next to the reviewer instructions, so anyone on the team can reset the environment before a submission.
When features depend on live Meta data, such as messages arriving from a Page, I explain in the instructions how the reviewer can generate that data themselves, for example by sending a message to a test Page. Combined with a clear screencast, this gives the reviewer two ways to confirm the use case.
Keep the review environment stable
While the review is pending, avoid deployments that change login, onboarding, or the features under review. If a deployment is unavoidable, retest the reviewer flow immediately after it. If the review is rejected anyway, check access first as part of the resubmission audit, because it is the easiest cause to rule out.
Frequently asked questions
Can I give reviewers my real admin account?
No. Create a dedicated reviewer account with limited, safe permissions and sample data. It is safer and easier to keep stable.
What if my app requires two-factor authentication?
Disable it for the reviewer account only. Reviewers cannot receive your codes.
Do reviewers test from a specific country?
You should not assume a location. Remove geo-blocking and IP restrictions from the review environment.
How do I handle a paid-only feature?
Give the reviewer account an active paid plan or an unlocked trial for the whole review period.