We have add the 'business_management' scope on the OAuth2 process as we move from v12 graph API to v17. But users that are not owner of our app still have auth2 dialog that not mentions Businesses. Our users still failed to use pages that are managed by a business account.
Do we need an advanced access to business_management or submit a review to enable this behavior for all users ?

I want to upload a video file to Facebook in reel format (reel.mp4) with Graph API reference docs at https://developers.facebook.com/docs/video-api/guides/reels-publishing/
Currently when I use local file upload, it always returns ``` $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_POSTFIELDS, file_get_contents('facebook_reel.mp4')); curl_setopt($ch, CURLOPT_HTTPHEADER, $headers); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $response = curl_exec($ch); curl_close($ch); var_dump($response);
Result :
"copyright_check_status": { "status": "error" }
2. The same file will be returned if uploaded using file_url
Result:
"copyright_check_status": { "status": "complete", "matches_found": false } ``` Please help check the Endpoint again Thanks

I have a test application with a verified webhook and a connected test user in the Meta developers console. The webhook has two subscriptions: messages and messaging_postbacks. The webhook receives the messages callbacks but doesn't receive postbacks when the test user clicks postback buttons in the chat.Could you please tell what is the problem?
In the same time it receives test messaging_postbacks from the developer console.

Why have blog posts featured Images with 'non-English' file names recently stopped showing when shared on Facebook? We noticed it about 2 weeks ago. If I change the image file name to English letters, the image shows. Why has this change suddenly occurred with no warning? We have hundreds of shared posts on Facebook, all of which have non-English featured image file names. I have since found out this problem also affects other non-English languages such as Hebrew.

I just migrated a number from
previous (was on dialog 360): waba id: 233934109801832 & phone id: 207432572461460
new (my own app, which is an approved tech provider): waba id: 271460509379017 & phone id: 274762832380571
app's name is Spur (app id: 931280875302744), embedded signup flow went well, previous waba 2 factor was turned off, but when i hit register on the new waba phone id i get:
{
"error": {
"message": "(#100) Invalid parameter",
"type": "OAuthException",
"code": 100,
"error_data": {
"messaging_product": "whatsapp",
"details": "Provided Phone Number ID 274762832380571 does not match stored Phone Number ID 207432572461460 for 41435082047. Try deleting the previous registration first."
},
"fbtrace_id": "AMZjVZ7PIWx-7Lws_iEIm2t"
}
}
request is
curl --location 'https://graph.facebook.com/v19.0/274762832380571/register' --header 'Authorization: Bearer ' --header 'Content-Type: application/json' --data '{
"messaging_product": "whatsapp",
"pin": "123456"
}'
Anyone came across this issue?