On 4/4/2015 12:08 AM, Bernard Devlin wrote:
I assume you are trying to send a push notification from one Livecode
app to another.
Thanks for the info, Bernard. I'm not actually trying to send a
notification to another app, the stack is more a reminder system.
Notifications are generated by
Android can delay notifications for power saving reasons. As I understand it
the more there are from one app and the less the user interacts with them, the
more likely they are to be delayed.
I think to do what you want more reliably you'd need to use background
processing (wake up every 30
When I looked at Android notifications a while back, I saw some
irregularity with them being delivered, and with the aural alert of a new
notification. I haven't looked at this for some time. However, when I
look at this page
On 4/3/2015 4:04 AM, Bernard Devlin wrote:
Livecode does get the ID of the notification. Is there some way you can
incorporate that ID with the later messages?
I thought of that, but there's no way to specify an ID when you create a
new notification. The ID is read-only and assigned by the
I assume you are trying to send a push notification from one Livecode
app to another.
When I was testing push notifications, I did my tests via curl
curl -v -H Authorization:key=??? -X POST --data @push.txt
https://android.googleapis.com/gcm/send
where the file push.txt contained the
Is anyone using local notifications on Android? I need to know more
about how they work and I can't find much online about it.
I need to send notifications every half hour for a 5-minute period, 30
seconds apart. I have this working in theory; notifications are
scheduled correctly and mostly
