申请Instagram的public_content及follower_list权限遇阻，求可行方案

Hey there, since you’ve already got a valid use case and Facebook approval under your belt, let’s break down how to address the deprecated permissions you’re facing:

1. Understand the Current Permission Replacements #

First, let’s clarify what Facebook recommends instead of the retired permissions:

public_content - This permission is no longer available. For accessing public user profile info (like name, username, profile picture), you don’t need a special permission—you can directly call the Graph API’s /<target-user-id> endpoint for public fields, as long as the user’s profile is set to public. For public media content, if your use case requires it, align with permissions like pages_read_engagement (if working with Pages) or confirm your approved use case covers this access via basic profile permissions.

follower_list - This has been split into two specific permissions:

• user_followers: Grants access to the list of users following your authenticated user
• user_following: Grants access to the list of users your authenticated user follows

2. Update Your Permission Requests in the Developer Dashboard #

Since you already have a verified use case, updating your permissions should be straightforward:

• Log into the Facebook Developer Platform and navigate to your app
• Go to App Review > Permissions and Features
• Search for user_followers and user_following, then click "Request" for each
• When submitting the request, reference your already-approved use case, explicitly stating that these are replacements for the deprecated follower_list permission. Reuse any documentation or details you provided for your initial approval to speed up the process.
• For public content access, confirm you have the default public_profile permission enabled (this is automatically available for most apps and covers basic public user info access).

3. Adjust Your API Calls #

Update your code to use the new permissions and endpoints:

• Login Flow: Request the required permissions during authentication:

  // Example for Facebook Login SDK
  FB.login(function(response) {
    // Handle response logic here
  }, {scope: 'public_profile,user_followers,user_following'});
  

• Get Public User Info: Call the user endpoint for public fields (no extra permission needed for public data):

  GET /<target-user-id>?fields=id,name,username,profile_picture
  

• Get Follower List: Use the followers endpoint with the user_followers permission:

  GET /<authenticated-user-id>/followers
  

• Get Following List: Use the following endpoint with the user_following permission:

  GET /<authenticated-user-id>/following
  

4. Reach Out to Facebook Support if Needed #

If you hit snags with permission approval (even with your existing verified use case), head to the Support tab in the Developer Dashboard. Submit a ticket that includes:

• Your app ID
• A reference to your previously approved use case
• A clear explanation that you’re seeking replacement permissions for the deprecated follower_list and public_content
• Any relevant documentation from your initial approval

Facebook’s support team should prioritize your request given your already-verified legitimate use case.

内容的提问来源于stack exchange，提问作者Meghanaa Aggarwall