handling push notifications

[Mike Kerner]

Try it.  That's my observation.  So, what I do, instead, is instead of
sending the payload (which has to be short, anyhow), is have the app
recognize that it's gotten a push notification, then hit my server to find
out why.  The message you send is for the user, anyway.  The payload has to
be small, unfortunately, so either you have to send many messages to get
the entire payload (and Apple specifically states that they do not
guarantee delivery or the order of delivery), or you have to hit your
server, anyway.

On Thu, Oct 16, 2014 at 9:44 PM, Gerry <gerry.orkin at gmail.com> wrote:

> Terry wrote:
>
> > That"s disappointing
>
> Really? I'm just resigned to the fact that LC doesn't allow us to develop
> modern iOS apps that have the same capabilities (in terms of background
> operations) as xCode-developed apps. I've stopped trying and I've stopped
> being disappointed about it.
>
> What I'd LOVE is a clear statement from RunRev about their intentions in
> this area - will they ever support background operations? (And don't tell
> me to just use the .plist hack - the problem is much broader than the app
> not quitting on suspend).
>
> Gerry
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."