The photos endpoint has suddenly stopped working, I'm always getting an empty data response from the Graph API.
All the permissions are correctly set & I have tested with multiple pages with no luck.
Any help will be much appreciated.

After updating to API version v20.0, the Comment API fails to retrieve the 'from' field (including PSID and name) for non-test users. When using a verified and live app to fetch comments on posts using the page's Access Token, the 'from' field is only populated for test users. Comments from non-test users return without the 'from' field. This issue did not exist prior to the v20.0 update.
Below is the API usage flow and the response from step 4. As shown, the 'from' field is only available for the test users, while it is missing for non-test users. This functionality worked correctly before v20.
1. Obtain a User Access Token via OAuth
Permissions (all approved by Facebook and the app mode is live):
public_profile
email
pages_read_engagement
pages_show_list
pages_read_user_content
2. Use the User Access Token to retrieve the Page Access Token
GET me/accounts
{
"data": [
{
"id": "115...",
"access_token": "",
"name": "Page Name",
"tasks": [
"ADVERTISE",
"ANALYZE",
"CREATE_CONTENT",
"MESSAGING",
"MODERATE",
"MANAGE"
]
},
...
]
}
3. Use the to fetch posts
GET me/posts
{
"data": [
{
"created_time": "2024-05-24T13:51:35+0000",
"message": "Post Message",
"id": ""
},
...
]
}
4. Use the to fetch comments
GET /comments?fields=id,from,message
{
"data": [
{
"id": "",
"message": "message"
},
{
"id": "",
"message": "message"
// Where is from?
},
{
"from": {
"name": "",
"id": ""
},
"id": "",
"message": "message"
}
]
}
As shown, the 'from' field is missing for comments from non-test users, which was not the case before the v20 update. This issue needs to be addressed as it affects the ability to properly attribute comments to their respective users.
Our app's permissions have all been approved by Facebook to get "Advanced access" and the app mode is live. Everything was working correctly last week. After the release of version v20, this issue occurs across all API versions.

when using the /pages/search with the query "minnesota zoo", I expect the following page to be included in the search result:
URL: https://www.facebook.com/mnzoo Page Name: Minnesota Zoo Page ID: 136257148787
The search results include a different unofficial page with the same name, so I would expect the page above to be included as well.
Please let me know if you need any further information, thanks

Recently, we've found out that during conversation with user and the Facebook Page on Messenger we're getting some unexpected results regarding author of the message. It looks like for some users, instead real name, we're getting Facebook user.
"from": {
"name": "Facebook user",
"email": "[...]",
"id": "{ID}"
}
What is the reason of changing author name to Facebook user? We need to inform clients why it's happening.

This specifically seems to affect post_video_ad_break_ad_impressions, post_video_ad_break_earnings and post_video_ad_break_ad_cpm under Page insights -> Video Ad Breaks metrics.
A request in the form of
GET [page_id]/insights?metric=post_video_ad_break_earnings&period=day&since=1711954800&until=1714460400
returns
{
"data": [
],
"paging": { ... }
}
This doesn't change based on whether the period is set to day, lifetime or omitted. Similarly, it doesn't change with the value of since nor until, nor does it change if they are omitted.
When mixed in with other (older?) metrics, which work in isolation, either no data is returned for the affected metrics, or only data for unaffected metrics is returned, which seems to vary request to request (i.e. the same request may produce varying results when repeated).
This seems to affect multiple pages, authenticated by multiple users.
Question: am I doing something wrong? Am I omitting some parameter that is not (well) documented?
Due to the random interactions with other metrics this feels like a bug, but there no longer exists a path to report a bug in this product.