I re-tested this today and confirmed that a UTC date only works on Android within a 12 hour period of a day. It’s an AM/PM issue and being mishandled on the Java side. *Slaps forehead*
We won’t be able to push out a fix for this until about 2 weeks from now since we’re readying the next release version of Corona. It missed the deadline. So, the only solution at the moment is to use the work-around I posted up above where you schedule a notification based on an duration instead of a UTC date/time value. That’ll work on both iOS and Android. Sorry about the inconvenience.
Oh good. I’m glad my solution helped you finish your release.
Just so you know, I did get approval to get this fixed (for real this time… honest!) yesterday and the fix is available in today’s daily build. Oh and that Corona Simulator crash has been resolved as well. Thank you for your patience and for informing us of this notification issue.
I re-tested this today and confirmed that a UTC date only works on Android within a 12 hour period of a day. It’s an AM/PM issue and being mishandled on the Java side. *Slaps forehead*
We won’t be able to push out a fix for this until about 2 weeks from now since we’re readying the next release version of Corona. It missed the deadline. So, the only solution at the moment is to use the work-around I posted up above where you schedule a notification based on an duration instead of a UTC date/time value. That’ll work on both iOS and Android. Sorry about the inconvenience.
Oh good. I’m glad my solution helped you finish your release.
Just so you know, I did get approval to get this fixed (for real this time… honest!) yesterday and the fix is available in today’s daily build. Oh and that Corona Simulator crash has been resolved as well. Thank you for your patience and for informing us of this notification issue.