You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to send a push notification with delayed_option=timezone and delivery_time_of_day=now but it fails with an OneSignalException.
I debugged a little bit and it appears that if you send "timezone" with "now" it fails but if you use "TIMEZONE", "Timezone" or even "timezonE" in the REST API of OneSignal it works.
The weirdest part though is that on our staging sites it still works fine and only in my IDE or using cURL it failes if I use "timezone". I wonder if this is a change in the OneSignal API or if I'm doing something wrong.
We are using timezone+now for a few years but only today I found this issue. Maybe it is related to the downtime earlier this morning.
The text was updated successfully, but these errors were encountered:
I'm trying to send a push notification with delayed_option=timezone and delivery_time_of_day=now but it fails with an OneSignalException.
I debugged a little bit and it appears that if you send "timezone" with "now" it fails but if you use "TIMEZONE", "Timezone" or even "timezonE" in the REST API of OneSignal it works.
The weirdest part though is that on our staging sites it still works fine and only in my IDE or using cURL it failes if I use "timezone". I wonder if this is a change in the OneSignal API or if I'm doing something wrong.
We are using timezone+now for a few years but only today I found this issue. Maybe it is related to the downtime earlier this morning.
The text was updated successfully, but these errors were encountered: