My experience so far is the same. It's not what's described in the docs: "ServerManagedPolicy is a flexible Policy that uses settings provided by the licensing server to manage response caching and access to the application while the device is offline (such as when the user is on an airplane)."
I can see why the initial license check would return "disallowed" if the device is offline. But after a successful check, my understanding is that the result be cached for a while, producing an "allowed" response. Which isn't what I'm seeing either. String On Aug 5, 11:18 pm, BoD <[email protected]> wrote: > Hi, > > I'm still experimenting with the LVL and I noticed that, with the > recommended strategy (ServerManagedPolicy), in case of no > connectivity, the callback's dontAllow() method is called. > > This seems a bit odd to me and I wanted to make sure this is the > expected behavior, and not a bug on my side. > > Thanks a lot for your help, > > BoD -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
