I have an access token and the following url:
https://graph.facebook.com/v2.5/414950271951116?fields=posts.limit(50).until(1451606399).since(1420070400)%7Bmessage%2Ccreated_time%7D&access_token= INSERT APP TOKEN
Originally I made an app token which could make requests for 60 days. It seems that it's not working now. Is anyone else having this issue or am I doing something wrong? I don't seem to get any error messages.
it was my mistake. It seems that this particular user has blocked people from using the API on their Facebook page.
Related
I am trying to publish Facebook Timeline actions using the app access token instead of the user's access token (so that I don't have to deal with expiring sessions), as described here:
https://developers.facebook.com/docs/opengraph/using-app-tokens/
This was working fine, but stopped working a few days ago, now giving me this error:
The client token cannot be used for this API
Any ideas on why this is happening, and how to fix it?
I am getting error while posting to facebook pages "Error invalidating access token: Session does not match current stored session." I havent changed the pwd too.
I have deleted the app from my facebook account and then reinstalled it , but still the same message. One wierd thing is that i am able to post on my wall , but not on pages.
Is anyone facing this problem too ?
I think there are some issues with pages and access tokens - I reported the bug - http://developers.facebook.com/bugs/368315619896504 - if you are working with more than one page (or developing), going through the process will invalidate any other page tokens from the same application.
Your token should habe the permissions manage_pages and publish_stream.
Then you have to query the page token using userid/accounts.
There you get a list of pages where the user has posts rights.
to post on a page you should use the token you get from the accounts path.
How to get offline access token of facebook?
I know that from recently time is out of date. And if I can't get offline access tokens.
What solutions of this problem is?
If you want to get a fresh token, simply follow this guide. You can obtain it through the JavaScript SDK, or doing a request to Oauth. In both cases the user will not notice anything unless he de-authenticated your app.
We are getting troubles using Facebook Connect Graph API within a SharePoint Portal, We are facning problems while getting Access_token from cookie.
before, it was gotten from cookie and It did not come encripted like 'AAAD4Ta4Jx2MBANUYTxUZCAj6vgwON1SmgUZCpyYZAFDPj9eN679kaTuG7' but one week ago the code we get comes with that extrange format and it is not possible to get info of the user.
now, we have changed the way that we get access_token bye sending the encripted code to https://graph.facebook.com/oauth/access_token?... but we always get a bad request.
Could you please indicate us. what have changed in this API recently, why did it use to work before and not now.
Facebook is now sending encrypted access tokens as part of their switch to SSL and Oauth2.0. This is mentioned on their Facebook Roadmap. They work just like normal tokens. Use that token to call /me to get the users info, as you can't parse the user id from the token anymore.
up until 4 days ago this was working just fine, now I keep receiving an error when trying to post a youtube video on my friends (or even my own) wall.
Reading user ids from list.txt and send them a video
Posting video to user id: me
{"error":{"type":"OAuthException","message":"Error validating application."}}
I am getting the same error with an application which i created on a friends facebook account when trying to do the same thing.
Does anyone have an idea why this is and what I can do to fix it?
Thank you!
I started getting this problem for some of my users on my app recently. It was because my database field for storing oauth tokens was limited to 100 characters, which in the past has been long enough for facebook oauth tokens. Newer tokens are sometimes longer than that.
Just a guess...
I have suddenly started getting this on working code too. I have traced the API URL the PHP SDK is calling and it does have an access token in. The PHP SDK errors with 'An active access token must be used...' and calling the URL it called manually results in 'Error validating application.'