I am able to post trip requests, get estimates and ask for trip statuses, both in sandbox and live.
However, I am starting implementing status push notifications via webhooks and have hit a problem: I don't receive the notification (on sandbox). I have tried a couple of different URLs and servers to no avail. When pushing the notification ourselves from postman it works.
Do status push notifications via webhooks work on sandbox? If not, is there a way to test them?
According to the Webhooks documentation you should receive notifications every time you update the status of a ride request in sandbox mode.
Sandbox
When making Requests in the sandbox environment, we will also emit
webhook events for simulated trips. The requests.status_changed event
will be emitted every time the status of a simulated Request changes.
The requests.receipt_ready event will be emitted once a Request’s
status changes to completed.
Is you Webhook URL HTTPS enabled?
If this doesn't work you should consult the support team by visiting https://help.uber.com or by emailing support#uber.com.
If you want an easier way to debug, try setting up Ngrok
and then change the webhook URL in your developer dashboard to the link you get from Ngrok. That should allow you to debug the Webhooks issue on your local machine and verify that there is nothing wrong with your deployment setup (lack of HTTPS could definitely be the culprit as Mnemonic Flow said)
Related
After saving a data, I wait for the confirmation of the opposite server. With a different endpoint, I want to constantly check this server's approval check in the background. I want to send requests continuously until the transaction is approved and when it is approved, I want to take action. How can I make a request to a persistent endpoint?
From which sources should I get help, if there are examples, I would like to examine them.
Facebook recently released an optional Recurring Notifications feature for Messenger.
My group has attempted to use this feature in our app; in our chatbot flow, we present the user with the opt-in message, and when they click on the opt-in button, we are supposed to get a webhook event notification. Unfortunately, no request is coming to our webhook when the user clicks the button.
We've done some sanity checks:
The app is subscribed to messaging_optins notifications feed (v11).
I'm certain the webhook itself is configured properly, because our server is receiving other notification feeds (e.g. messages).
The problem also doesn't seem to be with our opt-in request button configuration, because even the Test button in the Facebook Developers dashboard (which is supposed to send a sample messaging_optins payload to our server) does not result in a call to our webhook.
Possibly irrelevant details: the page connected to this app is registered in Kenya and the webhook server is running on an AWS instance in Germany. We have another page registered in India connected to AWS in India, and that connection is working fine despite identical configuration.
What other things should we troubleshoot to identify the problem here?
We have webhooks firing in Azure Devops which push data to a logic app which in turn performs some actions. Sometimes due to too many requests at once or a multitude of other reasons, the logic apps fail. After a certain number of successive failures, the webhooks are disabled automatically. See link
There is no notification of webhooks disablement sent out.
Is there a way to notify when the webhooks are disabled?
Posting just if someone else is searching for fixing this.
We have created a logic app which runs daily and checks the status of the service hooks using the Service hooks API. If disabled due to any reason, it just enables it back and sends an email to support intimating them of this.
Works like a charm!
I'm testing a facebook instant games app and want my bot to collect messaging_game_plays events to log user data at the end of a play session.
I've set up an app page, app, and uploaded a build that I have moved to the testing stage. I also have a bot with a public webhook that I have successfully verified. The webhook is currently subscribed to messaging_game_plays as well as messages. I have simple echo functionality built into the bot and can spin up the messenger app on my phone, message the page, and receive an echo perfectly.
The problem arises when I go to the games section of my messenger app, play the game, and then exit the game. I expect my bot to receive a messaging_game_plays event per https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messaging_game_plays/, but I don't receive any indication in the logs of the bot server that anything has called the webhook (even after waiting a significant amount of time).
So my question is/questions are: am I missing something that is required for the messaging_game_plays to be sent to my bot? Is there anything that I need to add to my app-build specifically for this event to trigger? Is launching the game on my phone and exiting the game sufficient for testing this event?
I've searched forums and documentation with no luck but maybe I've missed something along the way. I have checked this question: Facebook Messenger webhook setup, but not triggered, and that helped me successfully trigger messages events which I am getting, I just can't seem to collect messaging_game_plays events.
I am rather new to this process so I may be missing something small, any help would be greatly appreciated!
For reference:
app webhook subscriptions
What does your fbapp-config.json file say? If your bot opt-in parameter is 'opt_in_dev' or 'opt_in_public' you will need to call the subscribeBotAsync method to subscribe your user to the bot before any webhooks will be sent.
Messenger bots will need to be opt-in only from January 19th (see here: https://www.facebook.com/fbgaminghome/blog/important-game-bots-update).
We're making this change to ensure a better player experience.
If you want to transfer player data without requiring the bot to be opted-in, you can use standard JavaScript fetch/XMLHttpRequest with getSignedPlayerInfoAsync to avoid tampering.
The webhooks guide lists email as one of the available services, however it seems that this only kicks off when a user actually pushes a change to the repository. How can you configure it so that an email is fired off for every event concerning that repo - issues opened/closed, pull requests, etc.?
You cannot, currently. See this pull request to the github-services which would enable at least pull request notification by email, but it was never merged by GitHub.
As a work-around I currently use IFTTT on my Android device to get notified about pull requests by email.