- Comunidade
- Pergunta
Hi. I'm trying to retrieve user's albums using me/albums but i'm getting the following errors on Graph Explorer:
{ "error": { "message": "(#10) Application does not have permission for this action", "type": "OAuthException", "code": 10, "fbtrace_id": "A1QZ2wQfn_IT-YaZp4P2Ziw" } }
user_photos permissions in grated in test mode , and me/photos?fields=picture&limit=10&type=uploaded retourn uploaded photos.
So it's not related to permission error. Looks like a bug.
Same here, I'm stuck in the process of requesting and getting rejected for user_photos/user_videos. I can't figure out what's going wrong. I set up the test user, switched to dev mode, but the Graph API isn't working properly at all.
{ "error": { "message": "(#10) Application does not have permission for this action", "type": "OAuthException", "code": 10, "fbtrace_id": "AnK-PKjkVno4SK7NC5eILuD" } }
Hello,
I'm facing an issue with fetching albums from Facebook. Previously, everything was functioning correctly, but at the beginning of this week, I noticed the functionality isn't working. Initially, I thought something might have broken, but it's also not functioning in the Graph API explorer. The app is in Development mode, and I've tested it with both an Administrator user and a Test user.
Has anyone discovered a solution to this problem?
{ "error": { "message": "(#10) Application does not have permission for this action", "type": "OAuthException", "code": 10, "fbtrace_id": "ADbAroPgNSDnoZxhbt43QPt" } }
This is disappointing and ridiculous in their own Graph API Explorer (generating a new Access Token): { "error": { "message": "(#10) Application does not have permission for this action", "type": "OAuthException", "code": 10, "fbtrace_id": "AK-Ox-8TWkdScfjJ_JrxMM_" } }
This page clearly says, "user_photos" is the required permission to access this resource (route): https://developers.facebook.com/docs/graph-api/reference/v18.0/user/albums
It's the same for version 20.
{ "error": { "message": "(#10) Application does not have permission for this action", "type": "OAuthException", "code": 10, "fbtrace_id": "A1QZ2wQfn_IT-YaZp4P2Ziw" } }
This isn't an answer, this is a copy of another error from someone else that looks comparable to mine making the request to the "/me/albums" route.
Thank you I only posted what I got ..to the guy that had to comment under me. That was the answer that I got so that’s why I was questioning what I was doing wrong pardon me I thought that’s what this was. We were supposed to do if we needed help
This stopped working a few weeks ago already. Since there is no specific albums permissions it should suffice to submit the respective permission for review (use photos endpoint w/o requesting the albums field instead).
How does one "submit the respective permission for review"? The permission is called, "user_photos"
Even if you submit a request for permission without any successful API calls it will be rejected
"Even if you submit a request for permission without any successful API calls it will be rejected"
What does that mean? It's definitely not an answer to my question.
My Graph API call to the "/me/albums" route was working perfectly fine for months. What happened to this route? Is this the type of quality I can expect from Facebook's Graph API in the future? It just randomly stops working one day for weeks on end?
Rear my comment again: you don’t need to show requesting albums for app review only photos.
You need to have "user_photos" permission enabled to make graph API requests to get albums.
https://developers.facebook.com/docs/graph-api/reference/v18.0/user/albums
albums is only accessable with advanced access, if you don't have advanced access for user_photos it fails with this error.
Thanks Lars! :)
Hi, for all who care,
I just tested the API with graph tools and found it has been fixed. This is great news, as it means we can now proceed with our data analysis and visualizations without further issues. Let's take a break and resume our work with renewed energy.
Best regards.
OMG Thank you Bunny Lin! Why was this broken, why was there no communication about this from Facebook?!