This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
hope this is the right place to post my question. In my company we use bot framework for developing our bots. We are dealing with messaging_postbacks webhook that is sent by Facebook Messenger when a new user initiate a new conversation with the bot through the Get Started button. Webhook is delivered correctly to our bot when user clicks Get Started button from the mobile app. However, when a new user writes to the bot through Messenger Chat Plugin, we do not receive messaging_postbacks webhook that should be delivered when clicking "Continue as NAME" button as per Facebook documentation (https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messaging_postbacks).
We were wondering why webhook from Chat Plugin is not delivered to our bot and found in the documentation something that caught our attention:
Graph API v7.0+ messaging_postback webhook event from the chat plugin will not be returning sender.id field. It will return a new sender.user_ref field. This changes will take effect on all older Graph API versions starting Nov 2, 2020.
This made us thought that perhaps bot framework hasn't been aligned with that change yet and this is why we aren't receiving the webhook. Is this possible? If yes do you know if there is any planning to update the behaviour?
Thank you.
Hi, thanks for reaching out. It seems your your inquiry regarding Facebook Graph API may be best suited for the Facebook Developer Community.
Hi, thanks for sharing more details. This issue requires proper diagnosis, it may be best to contact Azure support for further investigation. Sorry for any inconvenience.
Hi, as your suggestion I opened a ticket to Azure support, thank you.
Hi,
we already opened a few tickets to Facebook support but it seems that there is no problem with the webhook itself that should be delivered correctly. Do you know if bot framework has implemented the webhook change? We suspect that, since there is no longer the user ID, bot framework is unable to trace the user and reconstruct the conversation and consequently goes into error and does not send the webhook to our bot.
Thank you.