Ok I understand now. Maybe this behavior should be made a bit more explicit in the documentation since this is the recommended policy and I guess most developers will use it without trying to implement their own - resulting in false negatives for the users.
Thanks, BoD On Aug 7, 1:25 pm, String <[email protected]> wrote: > On Aug 6, 9: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? > > The Policy code does get distinct responses, it just boils it down to > either "allow" or "disallow" before it gets to your callback. If the > device is offline, and no response has been cached, it's really a > matter of opinion if that user should be allowed or not. My opinion is > that "disallow" makes sense in this case. > > String -- 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
