Before you submit your app for App Review, take a moment to review some of the most common mistakes that can lead to requests for additional information or rejection.
If we need to log into your app to test its functionality, make sure to provide us with all the necessary login credentials and login instructions when filling out the App Verification Details section of your App Review request.
App Review > Requests > Complete App Verification > Provide verification details:
If you are unable to supply login credentials because your app exchanges data directly with Facebook APIs and doesn’t have a user interface, make sure that your submission accurately describes and shows how your app will ultimately use the data provided by each permission and feature in your request.
Learn more about server-to-server apps.
Test Users are temporary Facebook accounts that you can create and use to test your app. You can create Test Users through the App Dashboard and include their login credentials (email and password) in your App Verification Details and we will use them when testing your app.
Facebook Platform Terms and Developer Policies restricts app creation and management through fake accounts. Please manage and develop your app through your personal Facebook account, but don't include your personal Facebook account's credentials when submitting your app for review — we will use our own test accounts or your Test User, if you have created one.
If we need to access a website in order to verify your app’s functionality, make sure that the website URL you provided in the App Verification Details section is accurate, working, and publicly accessible.
Before you submit for App Review, confirm that your app is using the requested Permissions and Features in an approved way. If the review team determines that your app’s use case is disallowed, then your submission will be rejected or you will be requested to provide additional clarifying information.
It is also important to only request Permissions and Features that your app actually needs to function. If the review team can’t see or have a clear understanding of why you are requesting a specific Permission or Feature, it will be rejected.
Your screen recording doesn’t have to be a big Hollywood production, it just needs to clearly show us how your app uses each Permission or Feature requested to enhance the app user's experience.
Our review team will use your screen recording to confirm that your app’s use of each requested Permission and Feature is clearly visible, follows an allowed use case, and is compliant with our Facebook Platform Terms and Developer Policies.
Refer to our Screen Recording guide to learn how to create an effective screen recording.
If your app does not directly request Permissions from app users, make sure your screen recording cleary shows how it uses data provided by those Permissions and any Features included in your App Review submission.
Refer to our Sample Server-to-Server Submission to better understand how to make a screen recording for these types of apps.
Believe it or not, this is sometimes a problem. Before you submit on your App Review request, double check that the app you are providing or referring to loads properly on each of the platforms that it supports.
If you are providing Test User credentials, make sure that those credentials work on all of your platforms your app supports.
Needless to say, if we cannot load your app on any of its supported platforms, we will not be able to verify your app and will reject your submission.