The policy does tell you that if an existing app is not allowed you have 30
days to submit an update. So, a little slower that ASAP.
> On May 18, 2017, at 7:51 AM, Bob Sneidar via use-livecode
> wrote:
>
> Dam! I was almost ready to deploy my new iOS app, Jerky
Dam! I was almost ready to deploy my new iOS app, Jerky 2.0!
Bob S
> On May 17, 2017, at 16:08 , Richard Gaskin via use-livecode
> wrote:
>
> Of course any app that violates any of the other policies outlined on that
> page will be dumped ASAP, regardless of
On 2017-05-18 15:00, Colin Holgate via use-livecode wrote:
The things that you’re talking about, involving an app updating
itself, does that currently get past Apple review? That would be an
argument to use with Google, in that Apple have usually been tougher
about this.
Also, does Google’s
The things that you’re talking about, involving an app updating itself, does
that currently get past Apple review? That would be an argument to use with
Google, in that Apple have usually been tougher about this.
Also, does Google’s policy suggest that you can’t even update an image in the
I haven’t been following this topic, but I happen to be at Google I/O. If there
are any short questions I could ask while I’m here I could ask around.
One thing I’m going to go to this morning involves Google Play policies.
___
use-livecode mailing
On 2017-05-18 00:25, J. Landman Gay via use-livecode wrote:
I just got a developer email about a revision to Google's policies for
apps on Google Play. Google will not allow apps that download
executable code, similar to Apple's policy. It sounds like that
includes stack content downloaded via a
J. Landman Gay wrote:
I just got a developer email about a revision to Google's policies for
apps on Google Play. Google will not allow apps that download executable
code, similar to Apple's policy. It sounds like that includes stack
content downloaded via a "launcher" app.