Handle expired tokens automatically about facebook-sdk

[DeaconDesperado]

It wouldn't be too difficult to spin something up for this, but unless I'm mistaken, the server-side access tokens are given the extended 60-day expiration by default. The deprecation of the offline access permission has gotten rid of the indefinite tokens that would never expire, but all that really needs to be amended in existing apps is to change the way you manage the persistence of your tokens (IE, expect to get a new one every time the user comes back from FB and re-authenticates, since this will provide a new token.)

See the section on "Server-side OAuth Developers"
https://developers.facebook.com/roadmap/offline-access-removal/

I would consider this more about how you manage the storage of your access tokens and associate them with your users. It's a little outside the scope of the sdk in that regard. If they are coming back and initiating a login again, you should be sending them back through the auth process as normal rather than just assuming your saved token is good. If they have already granted permission to your app, they will immediately hit the callback with a fresher token. You'd only encounter the expired access token issue if you were assuming you had good tokens like you used to be able to do with offline_access, which now, unfortunately, would mean you aren't Doing It Right™

[martey]

I think I agree with @DeaconDesperado's comments, and so am closing the issue. I think issues like this could be better resolved by us having better, more up-to-date examples, so it is clearer how developers might want to use this SDK.