Well, an Android dev in Google's online office hours helped me troubleshoot this today.
It turns out that the reason the authToken from the AccountManager wasn't working was because it was expired. It was dated Dec. 9th, which is probably the day I first got my authentication code working. I guess it cached the authToken and has been using the same one ever since. So now the questions are: How do I clear out the cached authToken? How often would I need to do this? Is there a way of getting a new authToken that isn't going to require that the user agree to a system prompt every time? I'm going to try the invalidateAuthToken and updateUserCredentials methods. If the user is going to be prompted every time the authToken needs to be refreshed, using the authToken from AccountManager simply isn't going to be a worthwhile solution to authenticating a Google Service.
-- 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
