I have been playing with this now for a week and can't seems to find a solution. Whatsapp Business API is set up and working 100% in Live. I have verified my Webhook but are not able to see any data coming into the webhook file since the verification. Many variations of code have been tried to get data but still I don't see any data on the file, even when testing from the Quickstart > Configuration page.

The code I am currently running is from an answer provided by @Tarik at the following post: (for facebook itself but coding is the same) Facebook Messenger API - Can't verify webhook URL (PHP)

My webhook.php file is:

$message = date('Y-m-d H:i:s'); foreach ($_REQUEST as $key => $value){     $message .= "$key => $value (".$_SERVER['REQUEST_METHOD'].")\n"; } $input = file_get_contents("php://input"); $array = print_r(json_decode($input, true), true); file_put_contents('log.txt', $message.$array."\nREQUEST_METHOD: $_SERVER[REQUEST_METHOD]\n----- Request Date: ".date("d.m.Y H:i:s")." IP: $_SERVER[REMOTE_ADDR] -----\n\n", FILE_APPEND); if ( isset($_REQUEST['hub_challenge']) ){     echo $_REQUEST['hub_challenge']; } 

When sending a test from the Webhook Configuration page, the log.txt file only returns this:

2024-08-08 13:17:38 REQUEST_METHOD: GET ----- Request Date: 08.08.2024 13:17:38 IP: 173.252.107.116 ----- 

I am a bit stuck here and also lost on ideas. Can anyone advise me how to actually read the data I should receive on the webhook? I was considering playing with the verification token to see if Meta require it for some sort of asynchronous communication but that don't seem to be the case. Any assistance will be appreciated.

Using the below end point my page token returns posts from the page:
https://graph.facebook.com/v18.0/{PAGEID}/feed?fields=id,created_time,message,status_type,from,place,picture,attachments&limit=100&access_token={TOKEN}
If I then take the post id from this return and try and get comments for it using the following end point I am getting (#200) Missing Permissions. https://graph.facebook.com/v18.0/{POSTID}/comments?limit=100&fields=created_time,from,comment_count,message,attachment&access_token={TOKEN}&order=chronological
But I am not being told what permissions are missing, and why I cannot get comments. This is also not always the case, this exact scenario works in many other cases, so there is an issue somewhere with the access of the user/page, rather than my process..... But I have no idea what, or how to find out.
If I look at the permission in the access token using the token access debugger tool, we have the following: pages_show_list, business_management, pages_read_engagement, pages_read_user_content, pages_manage_posts, public_profile
and my understanding from reading the documentation is that I just need this one: pages_read_user_content to read comments.
I am so confused.
Any help or suggestions of things I can try would be greatly appreciated. if only the error was more useful, and told me what I was missing, I could have a better idea of how to fix.
Thanks in advance

I am using the WhatsApp Cloud API to create and send forms using the Flow feature. The forms are successfully created and are accessible by other users without any issues. However, when I try to open the form on my own WhatsApp Business App, it gets stuck on the loading screen and never fully loads. Even simple test messages like "Hello World" fail to display.

Here are the steps I've taken:

1. Created a form using JSON.
2. Verified that the JSON is correctly formatted.
3. Confirmed that the form works on other users' devices.
4. Updated my WhatsApp Business App to the latest version.
5. I have a good internet connection

Example JSON:

{     "version": "3.1",     "screens": [         {             "id": "WELCOME_SCREEN",             "layout": {                 "type": "SingleColumnLayout",                 "children": [                     {                         "type": "TextHeading",                         "text": "Hello World"                     },                     {                         "type": "TextBody",                         "text": "Let's start building things!"                     },                     {                         "type": "Footer",                         "label": "Complete",                         "on-click-action": {                             "name": "complete",                             "payload": {}                         }                     }                 ]             },             "title": "Welcome",             "terminal": true,             "success": true,             "data": {}         }     ] } 

Log Information:

[2024-08-07 16:38:01] local.DEBUG: Sending message to WhatsApp API  [{"stdClass":{"type":"interactive","interactive":{"type":"flow","body":{"text":"Hello word template"},"action":{"name":"flow","parameters":{"mode":"draft","flow_message_version":"3","flow_token":"aiqvYS","flow_id":"11655894848158","flow_cta":"Me Test","flow_action":"navigate","flow_action_payload":{"screen":"WELCOME_SCREEN"}}},"header":{"type":"text","text":"Welcome to the BotController"}},"to":"2637123456","messaging_product":"whatsapp","recipient_type":"individual"}}] 

Has anyone encountered this issue before or have any suggestions on how to resolve it? Any insights or solutions would be greatly appreciated.

Additional Info:

• My device is running the latest version of the WhatsApp Business App.
• Basic flow forms also fail to load on my device.

Thank you in advance!

I can't find any documentation talking about this new type.
```"type":"interactive","interactive":{"type":"call_permission_reply"}}]}```

We've recently noticed an important issue that may be affecting many developers using the Messenger Platform on iOS. We believe this could be a bug introduced in a recent update:
ISSUE: External links with custom URL schemes (e.g., "app-name://linkdata") are no longer opening from webviews on iOS devices when using Messenger. SCOPE: This affects apps that use custom URL schemes for deep linking, including a common Swedish application we integrate with. TIMELINE: The problem appeared recently, suggesting it might be related to a recent Messenger iOS app update. PLATFORM SPECIFIC: The issue seems to be isolated to iOS. Android devices are functioning normally. IMPACT: This changes long-standing functionality that has worked well for years, potentially affecting numerous apps and users.
We're hoping to gather more information:
Has anyone else noticed this change in behavior? Are there any known workarounds available? Has anyone reported this to Facebook through official channels?
This issue is causing significant inconvenience for our users, and we suspect it might be impacting other developers as well. We're hoping this can be looked into and potentially addressed in an upcoming update.
If you're experiencing similar issues or have any insights, we'd greatly appreciate your input. Your experiences could help in understanding the extent of this problem.
Thank you for your time and any information you can provide.