Monday, October 15, 2012

My Token Is What? Facebook Token Is "uh Broken"

Facebook has a way of messing with App publishers and users by making changes and not documenting the changes. They have something called an access token that allows an app to publish to a Facebook page while a user is not logged in. Lately a message pops up when a blogger/user checks the RSS Graffiti app that warns of expired access tokens. Problem is: This blogger is never logged out of Facebook because at least one device is always logged in to Facebook in the company.  So why is there an issue with the Access Token? That's anyone's guess, and don't count on Facebook helping out in any way.

RSS Graffiti explains it this way ...

You’re on this page because RSS Graffiti displayed the following message: 
“Facebook returned an access token that expires in x minutes. Please see our troubleshooting guide for help in resolving this issue.” 
This message is related to these errors which may be appearing in your activity log:
“RSS Graffiti does not have the proper credentials to publish to the target. No credentials found for target/page type” 
“Facebook error code: 190: Error invalidating access token: Session has expired at unix time …” 
These notices indicate RSS Graffiti doesn’t have a long-term access token for your profile. Access tokens allow RSS Graffiti to publish on your behalf when you’re not logged into Facebook. Whenever you visit the app, we attempt to request both a never-expiring access token for pages and a 60-day token for profiles and groups, so that publishing can continue for as long as possible without any action from you. 
However, Facebook made some recent changes which caused problems granting long term access tokens and there are certain cases where we are only able to get a 60-minute access token, which is nearly useless after you’re logged out for more than an hour.

The app publishers at RSS Graffiti seem a little frustrated with the message, too.

If you continue to see the short-lived access token message, you may be subject to a confirmed Facebook bug related to this problem. You can subscribe to the bug here to try and raise Facebook’s awareness of the problem so that they quickly implement a fix.

One user, Justin Tazyn, sums up Facebook's response to the issue perfectly ...

"This has been high priority for over 2 months. Is it really high priority?"