Android local notifications
bdrunrev at gmail.com
Sat Apr 4 01:08:15 EDT 2015
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"
where the file "push.txt" contained the parameters which determined
the values of
Your android key would go in the above command line where it says "???"
By using http to send the notifications to the Android URL listed
above, you may be able to se the id and thus check whether the problem
of updating notifications is resolved this way. If so, then you do at
least have a non-Livecode solution which may be acceptable until the
Livecode engine is changed to accept the ID as a parameter.
push.txt contained this kind of text
The final parameter (registration_id) may be what you want. My notes
from these tests don't mention why I was including that (maybe I was
actually trying to work out how to re-use IDs).
The "myurl://" is to do with associating an android app with a URL
schema. I think you can ignore it.
Let me know if it works. It's a couple of years since I looked at
this, so I'm a bit foggy on it all.
On Fri, Apr 3, 2015 at 6:13 PM, J. Landman Gay <jacque at hyperactivesw.com>
> 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 engine.
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode