Rory, where did you get the "ah" information from? Is there any documentation on the actual Google service behind this?
I checked the Android 2.0 Calendar and Contacts app and they only seem to use a homegrown mechanism. Maybe better luck with Android 2.1? Cheers, Mariano On Dec 3 2009, 9:59 pm, RoryD <[email protected]> wrote: > On Nov 9, 5:00 pm, Nerdrow <[email protected]> wrote: > > > I don't know the authTokenType to pass as an input parameter. > > It looks like "ah" does the trick for authTokenType! > > If you specify true for notifyAuthFail, you'll get a notification > posted saying "Permission Requested" that takes you to a screen where > Android says "The listed applications are requesting permission to > access the Google App Engine login credentials for account > [email protected]. Do you wish to grant this permission?" then Allow/ > Deny buttons and the name of your app. > > I was usingblockingGetAuthToken& it returns null for the token in > this first case, presumably because there's no way to proceed without > user interaction. After you authorize the app, > subsequentblockingGetAuthTokencalls succeed. I suspect non-blocking > getAuthToken calls will properly handle this asynchronous behavior. > > Sweet, now I can remove all my homegrown AppEngine auth stuff :-) -- 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
