Well, if anyone is still following this thread at all... I'm able to replicate the behavior RoryD describes, but it is still less than ideal from the user's perspective. Here's what happens:
1) The user opens the app for the first time, clicks a button to log in. 2) Account Manager tries to get the auth token, returns null and produces a system notification. 3) At this point, the user would have to return to the home screen, open Notifications, select the system notification that was just produced and allow the app access to their user credentials. 4) The user could then relaunch the app, click a button to log in, and the Account Manager would then be able to successfully retrieve the auth token and use it to log in. I really don't want users to have to exit my app to accept a permission notification before reentering the app. Granted, they would only have to do this once, but it's still extremely clunky. A couple of questions: 1) If we're already declaring the GET_ACCOUNTS and USE_CREDENTIALS permissions in the manifest, and the user is aware of this when they install the app, why the extra steps of notifying the user and forcing them to allow the app to use their credentials? Isn't this overkill? 2) Is there a way to take the user directly to the notification screen when the system sends the notification, rather than have the user manually navigate away from the app to the notification screen? -- 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
