Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As written in <a href="http://developers.facebook.com/blog/post/500" rel="nofollow noreferrer">How-To: Handle expired access tokens</a> developers blog post</p> <blockquote> <p>Access tokens for users can become invalid due to various reasons. In most cases, they can expire if it’s past the time specified by the <code>expires</code> field (by default access token have a 2 hour lifetime). What many developers do not realize is that an access token can also expire if a user changes her password, logs out or if she de-authorizes the app via the App Dashboard. It is very important that your apps handle such situations. If your access token expires, you need to reacquire a valid access token.</p> </blockquote> <p>Before we could use <code>offline_access</code> permission to get token that not expire (unless user is connected with application), this permission is now deprecated, see <a href="http://developers.facebook.com/docs/offline-access-deprecation/" rel="nofollow noreferrer">Deprecation of Offline Access Permission</a> to see how you can get <code>access_token</code> with longer expiration time.</p> <p><strong>Update:</strong><br> As of Aug 2012 Facebook PHP-SDK <a href="https://github.com/facebook/facebook-php-sdk/commit/1270f0debaab3b93d683a9817c7adbc7e9e5cdc0" rel="nofollow noreferrer">have added simple way of extending <code>access_token</code></a> (see <a href="http://facebook.stackoverflow.com/questions/8982025/how-to-extend-access-token-validity-since-offline-access-deprecation">How to extend access token validity since offline_access deprecation</a> for more details)</p> <p>Extracted from <a href="https://stackoverflow.com/questions/9060336/error-validating-access-token">here</a>.</p>
 

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