Facebook requires use to updated Data use checkup on several apps. But none of it can be done because at the first step of selecting a Business portfolio, it gives the error: Your account is restricted right now You have been temporarily blocked from performing this action.

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.

Facebook has informed us that our application is not compliant. They have requested us to provide a link to the Privacy Policy before the login, which we currently do on the signup page.
We've examined the Facebook app for an example to understand their requirements, but we cannot find any links to their own Privacy Policy.
Attached is a screenshot of our ongoing conversation. We've asked for more details, but they keep repeating the same response without addressing our questions.
Has anyone else encountered this situation, and if so, how did you resolve it?

I have this issue for a long time and I thought it might be at my end but it is not. I have the latest android messenger app and when I open a chatbot with quick replies it appears as it suppose to on windows web browser but on my android messenger app is not appearing or after I close the app after some minutes and open it again sometimes the quick replies appears.

In our app, we are trying to use Whatsapp Cloud API with our user's OAuth access token (received through the Facebook Login flow, and we have whatsapp_business_messaging,whatsapp_business_management and business_management scopes).

The WABA is defined in their own business.

The issue comes when we try to use https://developers.facebook.com/docs/whatsapp/cloud-api/reference/registration/ this call to finish getting access to the phone number - we receive (#200) You must accept the WhatsApp Business Cloud API terms to use the API. Check your WhatsApp Account Overview page

I'm wondering if this is some kind of terms of service that I need to accept (can't see any prompt to do so on my end), or something that our clients should accept in their WABA?