Note that there are some explanatory texts on larger screens.

plurals
  1. POProblem with access token while creating Facebook Test Users
    primarykey
    data
    text
    <p>I'm trying to create test users for my Facebook application. They announced this functionality in this blog post in November (http://developers.facebook.com/blog/post/429) and it is documented here (<a href="http://developers.facebook.com/docs/test_users/" rel="nofollow">http://developers.facebook.com/docs/test_users/</a>). I could not find the answer to this elsewhere...</p> <p>According to the documentation, "You can create a test user associated with a particular application using the Graph API with the application access token." This links to the section "Autenticating as an Application" and describes this CURL script:</p> <pre><code>curl -F grant_type=client_credentials \ -F client_id=your_app_id \ -F client_secret=your_app_secret \ https://graph.facebook.com/oauth/access_token </code></pre> <p>So far, so good. I ran this and get the following: </p> <pre><code>access_token=1182...18|nTI...r5Q </code></pre> <p>So now I want to POST this token to the graph api test user URL:</p> <pre><code>POST /1182...18/accounts/test-users?installed=true&amp;permissions=read_stream&amp;access_token=1182...18|nTI...r5Q </code></pre> <p>When I do this (both using the Facebook PHP SDK and just typing it into the browser) I get:</p> <pre><code>{ "error": { "type": "OAuthException", "message": "Invalid OAuth access token." } } </code></pre> <p>So the questions are: <li> Why am I getting this error message? <li> Am I using the wrong access token (despite Facebook explicitly telling me to use this one?) <li> Do I need to parse the access token somehow?</p> <p>Thank you for your help.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload