I would be careful removing your own authentication code just yet. So far Droid is the only phone with 2.0 on it and it's uncertain that once other phones get 2.0 whether or not they will also get the Facebook and Google authenticators. The emulator currently does *not* support Facebook or Google authenticators, for example.
On Dec 3, 12:59 pm, RoryD <rory1doug...@gmail.com> wrote: > On Nov 9, 5:00 pm, Nerdrow <troybe...@gmail.com> 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 > x...@gmail.com. Do you wish to grant this permission?" then Allow/ > Deny buttons and the name of your app. > > I was using blockingGetAuthToken & 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, subsequent > blockingGetAuthToken calls 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 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
