Facebook PHP API:获取自有群组帖子及应用审核步骤咨询
Hey there! Let’s walk through this clearly—this is a super common question when working with Facebook Group permissions, so you’re in good company.
First off: Yes, you absolutely need test users (or a test group) to get through the app review. Here’s why: Facebook’s review team needs to verify your app actually works as intended when it has the user_managed_groups permission, and without test credentials, they can’t validate that functionality.
Let’s break down the exact steps to submit your review successfully:
- Create a test user: Head to your Facebook Developer Dashboard, navigate to the Test Users section of your app, and create a new test user. Assign this test user admin access to your existing group (or even easier, create a dedicated test group and make the test user its admin—this keeps your real group data separate during review).
- Grant the test user
user_managed_groupspermission: In the test user’s settings, enable this permission. Now you can use this test user’s access token to call the Graph API endpoint/{group-id}/feedand confirm you can pull post content—this is key to proving your feature works.
- First, validate your functionality locally: Use the test user’s token to fetch group posts and make sure your app displays them correctly. Take clear screenshots of the successful API response (if you’re testing via Graph Explorer) and your app’s UI showing the loaded posts. A short screen recording of the workflow (login → select group → view posts) is even better for the review team.
- Make sure your app’s purpose is obvious: The review team needs to see that you’re using this permission for a legitimate, user-facing feature. For example, if your app helps admins moderate posts, show that workflow clearly in your demo.
- Go to your app’s App Review section in the Developer Dashboard, select Permissions and Features, and find
user_managed_groupsto start the request. - Fill out the request form thoroughly:
- Use Case Description: Be specific about why you need this permission. For example: "Our app helps group admins curate and analyze post engagement in the groups they manage, making it easier to maintain a positive community." Avoid vague statements like "we need to access group posts."
- Demo Instructions: Give step-by-step directions for the review team to test your feature with your test user. Example: "Log in using test user email:
test-admin@example.com, password:TestPass123. Navigate to the 'My Managed Groups' tab, select 'Test Community Group', then tap 'View All Posts' to see the group’s post content loaded." - Attachments: Upload your screenshots or screen recording here—this is your proof that the feature works when the permission is granted.
- Additional Notes: If relevant, mention that you’re the admin of the target group, or that your app only accesses groups the user manages (not random public groups).
- It’s common for the review team to ask for more details or a clearer demo. When they do, respond promptly with exactly what they’re requesting—whether that’s a more detailed video, clarification on your use case, or additional screenshots. The more transparent you are, the faster your request will get approved.
A quick reminder: You don’t need to use real user data during review. The test user setup is designed for this exact scenario, so the review team will rely on that to validate your app. Just make sure your test environment mirrors what real users will experience once the permission is live.
内容的提问来源于stack exchange,提问作者Regof

