My apps use GoogleLoginServiceHelper and as far as I know they work on the Motorola Droid. One user reported an unrelated bug with the Droid to me but did not mention any other issues.
On Nov 9, 2:25 am, JP <[email protected]> wrote: > Introduced in 2.0, the SDK offers AccountManager to access accounts. > For all who jumped the gun using the method described in this > thread:http://groups.google.com/group/android-developers/browse_thread/threa... > > The challenge is how to migrate to 2.0 while not decoupling 1.x. > Needless to say that calling GoogleLoginServiceHelper in 2.0 crashes > and sinks the app. So I've tried a few things but basically could not > navigate around the VerifyError that is thrown as soon as an app using > AccountManager (or any of other new classes) is launched on 1.x (where > these classes do not exist). There's of course always the option to > create a new app that encapsulates the functionality of the existing > app and only handles access to accounts differently. But this is not > necessarily the most elegant solution. Has anybody looked into this > and come up with any ideas? -- 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
