I would like to know what does "Send the push at this time in each user's respective timezone" mean while I am setting up scheduled push notifications in Parse.
Thanks in advance
It means that if you schedule the push, for example, to 8PM and request to "Send the push at this time in each user's respective timezone", then each user would get the push at 8PM local time (based on that user's timezone).
Related
I am testing a push notification that is related to an event that only has 24 hs of duration. So, I wanted to send a notification with a variant to see the impact and diference. But i dont want to that same notification be sended more than once because if it is sended 24 hs later the event is off and we will be sending a wrong notification.
The message will be send everyday in the usual configuration or only the first day (That it is when it is schedule).
I have this doubt specially because when i see the result console y can see this:
We have a positive number for notification opened on days before the starting date. I DONT want users to see notif after 24 hs. I cant find any documentation regarding this.
I need to send an email alert everyday to notify pending Approvals to all approvers. Does this possible in App maker? Please suggest.
I am sending approval emails immediately after request created and this is working absolutely fine.
I want to know the event or an utility in App Maker which can help to trigger emails for pending approvals to approvers every day.
You can achieve this using Triggers in App Makers server script.
Please check the sample code below for more details.
ScriptApp.newTrigger("functionName").timeBased().everyDays(1).create();
You have to create a function which sends the email and add the name of the function in the place of newTrigger("functionName") with the quotes.
I am a React Native developer currently working on a vehicle tracking app.
We want to develop a feature that allows users to exit the app, but continually be updated in the form of notifications when the vehicle moves (on average every 60 seconds).
I have been tasked with coming up the best way of integrating this. Our app already has push notifications set up with Firebase and we do use this to push out generic messages to the app.
My thinking is as follows:
When a user begins tracking a vehicle, the app should subscribe to a Firebase topic identified as the vehicle's registration. On the server side, each time an update comes in for a vehicle, send out a Firebase notification to that vehicle registration's topic, and then any users tracking it will be updated. When a user returns to the app and presses 'Stop tracking', the app unsubscribes from the topic.
In theory I think this would work. The reason I'm posting is I'm not sure it's the most efficient way. Our server received updates for over 1,000 vehicles every minute.
Any help/ideas would be gratefully received!
I'm working on an app which allows users to confirm they attended a google calendar event. I'd like them to make the confirmation immediately after the end time of the event.
Will subscription to Google's event push notifications (https://developers.google.com/google-apps/calendar/v3/reference/events/watch) let me know when the event is over?
If not, what's the best way to solve the above problem?
Push notifications only let you know about changes on the calendar (someone moved the event, someone responded etc.). There are no push notifications at starts and ends of events.
You can still combine storing the events and watching the changes to them with having a cron job (or similar) to run your code when events end.
I want to test my application's handling of webhook events from stripe when a subscription payment has been made (or failed). Here is what I've tried so far:
Set up a new subscription
Update user's credit card to be the one that can be added to an account, but will fail to actually be charged
Change the trial end date to be in one second
Wait a few seconds expecting the webhook to be sent
However, According to the documentation:
If you have configured webhooks, the invoice will wait until one hour after the last webhook is successfully sent (or the last webhook times out after failing).
One hour is a long time to wait, since I am trying to do this as part of an automated integration test suite.
One suggestion (from IRC) is to fake out the webhook request, so that my integration test sends the event, instead of Stripe sending it. However, since Stripe doesn't include any sort of HMAC in the webhooks, I can't trust the data in the payload. So, my application just takes the event ID from the webhook payload and fetches the event from the Stripe API:
If security is a concern, or if it's important to confirm that Stripe sent the webhook, you should only use the ID sent in your webhook and should request the remaining details from the API directly.
This will obviously not work if I am trying to inject fake events for my test (by design).
What are the best practices for testing this sort of scenario?
It seems there isn't a perfect way to do this. As suggested by #koopajah in a comment, I added a configuration value in my application that will disable fetching the event from Stripe, and instead just trust the event data in the webhook. This allows me to test my flow in almost the same way as it would work on production, since the event data in the webhook and the event fetched from Stripe are identical (assuming it is an authentic webhook request :)
Unless/until Stripe includes an HMAC signature in the webhook request to authenticate that it came from them, I think this is the best way to solve the problem.
One hour is a long time to wait, since I am trying to do this as part of an automated integration test suite.
You can shorten the wait by going to the invoice and selecting the "Charge customer" button, as shown below.