Thanks a lot for your reply. I'm going to implement my own Policy then. Issue starred.
BoD On Aug 7, 1:03 am, Trevor Johns <[email protected]> wrote: > Yes, with the default policy implementations, this is what happens. > > You can write a custom policy that behaves differently if you want, but we > currently don't provide any indicator to the application as to the cause of > the license failure. > > Probably a good thing, I opened a feature request for you > here:http://code.google.com/p/marketlicensing/issues/detail?id=12 > > For now, the recommend behavior is to just have a retry button when the > license check fails. > > -- > Trevor Johns > Google Developer Programs, Androidhttp://developer.android.com > > On Fri, Aug 6, 2010 at 1:55 PM, BoD <[email protected]> wrote: > > Isn't it strange that if the device is offline, this gives the same > > reply as if the application is not authorized?! > > And the code can't distinct these two cases? > > > In effect I don't see how you are supposed to use this policy. If you > > receive dontAllow the first time, what are you supposed to do? > > > BoD > > > On Aug 6, 6:32 pm, String <[email protected]> wrote: > > > 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]<android-developers%[email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- 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
