They need to provide several example Policy source files for different setups. The default has some disadvantages. It always shows "activating" when the app was run rather than any cached policy. Some of my customers complained about it. Other developers have modified their policy file for more liberal activation and caching. I've done this too but you have to do quite a bit of experimentation and no one is sure what the server is sending the customers if anything different at all.
I think the Android team wanted to avoid discussing the LVL too much as it would provide hints to pirates. But the pirates have taken the easy way out by hooking into the app and going around LVL all together. On Apr 10, 7:43 am, Nicholas Johnson <metthejohn...@gmail.com> wrote: > I use the default implementation of the Server Managed Policy (read about it > here<http://developer.android.com/guide/publishing/licensing.html#ServerMa...>) > for a paid version of my app, and haven't had any problems of note. I > haven't had any complaints about false-negatives, or the like -- however, > this *doesn't* mean that it doesn't happen, it just means that if it does, > then nobody has complained about it to me. > > As for you concerns: > > What problems with the grace period are you referring to? The grace period > will actually help you out if the case of "Retry" responses from the server. > > As for the licensing implementation with no network access, you shouldn't > worry too much about that either. Normally, you get about 10 retries before > the 503 error occurs. However, if the user has already checked the license > with a Server Managed Policy, then the license is cached on the phone for a > period of time. So, if the user starts the app up while their device is in > Airplane mode (let's say 10 hours into a 12 hour cross-oceanic flight), then > the cached license could still give the user a valid response -- even with > no network access. This all depends on the VT extra from the initial license > response. I'm not sure what a typical value is, but I know it last at least > several hours, if not a day or more (if you wanted you could check out the > value yourself by setting a breakpoint in the default implementation). Now, > if the user *hasn't ever* received a valid license check, then it will fail > without network connection. At which point, in my app, I ask the user to > check for network connectivity and retry. > > Something to note: I haven't verified this with anyone on the Android dev > team, but I'm pretty sure that once you release your application with LVL > enabled on your phone *and* you don't buy your own app (i.e. you have the > release version installed on your device, but haven't actually bought it > through the market), then the VT extra in the licensing response is not a > date that a typical user will receive. That is, I've found that without > actually purchasing the app, the licensing server gives me a validity time > which basically disables any valid cached response. Again, I've only seen > this once I actually release the app, and *have NOT *bought it myself. > > Nick -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
