pcardune
commented
12 years ago The fbconsole package itself doesn't depend at all on offline_access. The tokens that are used in testing do have offline_access (that's how they stay working) but it looks like the deprecation of offline_access won't expire them. So this shouldn't be a problem unless we write more tests that require a different access token. But we can cross that bridge when we get there. For now, it shouldn't be a problem so I'm going to close this issue.
https://developers.facebook.com/docs/offline-access-deprecation/
Relevant to your script?
"Deprecation of Offline Access Permission Access_tokens allow users to interact with your [Facebook] apps in meaningful and social ways. While [Facebook] is deprecating the use of the offline_access permission, through a migration setting in the Developer App, we are now allowing the option to reset the expiration time for existing, valid access_tokens each time a user interacts with your site. For existing apps, there are no changes required for your app, but you should consider using the new endpoint that allows you to get access tokens with a longer expiration time.
Extending the expiration of existing access_tokens
When a user visits your site with an existing, valid access_token, you have the option to extend the expiration time of that access token without requiring the user to login again. Our platform will only extend the expiration time once per day, so even if a user revists your site multiple times a day, the token will be extended the first time requested."
more here: https://developers.facebook.com/docs/offline-access-deprecation/