I changed my FB password for security purposes and now I can't load videos I've made using Movie Maker. "Error validating access token: The session has been invalidated because the user has changed the password." Yet I can't figure out how to update the password. Microsoft is conducting an online survey to understand your opinion of the Msdn Web site.cheers, G See https://developers.facebook.com/docs/authentication/access-token-expiration/ https://developers.facebook.com/blog/post/2011/05/13/how-to--handle-expired-access-tokens/ https://developers.facebook.com/roadmap/offline-access-removal/#extend_token @tschellenbach Thanks for all the replies!I have checked out the above mentioned links, I think @rahul342 posted the main page earlier.Instead please check the Deprecation of Offline Access Permission document which explains how to start using access tokens that are valid for up to 60 days.https://developers.facebook.com/docs/authentication/ Hey Gaura, Yes there will be a recommended recipe for how to deal with this.Please read below: Please note: On May 2, 2012, the offline_access permission will be removed.If you are building a new application you shouldn't use this permission.
When you login using Facebook you should never get an expired access token.
I have not tried defining the App / Web Url for HTTPS and doing the request with HTTP but I suspect it would also hiccup somehow. It was a URL difference, but unlike the others that have posted, mine was the difference between HTTP and HTTPS.
Or as in our case, the Request Method might be incorrect - GET with Headers or POSTing both throw the 2500, you have to do GET with a Querystring. We have Big IP handling HTTPS requests and forwarding over to an HTTP Apache server.
Then I failed when I try to generate an access token. The thing that made it work was to change the redirect uri (in both requests for the flow) from: I.e., add the trailing slash. They helped, but in my case the problem was that my redir URL had a query parameter and Facebook wasn't cool with that.
In the guide page, it says the following url could be used to generated an access token: I am quite sure every parameter is correct because if I change the client_id value or client_secret parameter, I will got a different error message. So, moral of the story is that the redir url you sent to exchange the token has to be identical the the original redir url and it can't have query parameters. In our case the trailing slash in the URL was already there, so I tried the Token we were using in the FB Debug Tool and it validated, so it looked like FB wasn't even seeing the Token in the request.