Thanks for the reply!
I am missing the permission:
<uses-permission android:name="android.permission.MANAGE_ACCOUNTS"/>
Adding that permission certainly sounds like it fits my problem.
If I am understanding issue 318 correctly it sounds like different
implementations of Android on various phones may or may not check
permissions the same way (tempted to say correctly). That certainly
makes things a little more exciting (I guess).
I will see if I can get my guy to run a test version with that
permission added to it.
I'll post back and let everyone know if that fixes it.
Thanks Again!
-Aaron
On Mar 1, 10:27 pm, Spiral123 <
cumis...@gmail.com> wrote:
> lol. welcome to the wacky world of Android OAuth debugging!
>
> first thing I would recommend is to look at your manifest. You should
> have at least:
>
> <uses-permission android:name="android.permission.GET_ACCOUNTS" />
> <uses-permission android:name="android.permission.USE_CREDENTIALS" />
> <uses-permission android:name="android.permission.MANAGE_ACCOUNTS"/>
>
> Try adding the following:
>
> <uses-permission
> android:name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
> <uses-permission
> android:name="com.google.android.googleapps.permission.GOOGLE_AUTH.wise" /
>
> <uses-permission
> android:name="com.google.android.googleapps.permission.GOOGLE_AUTH.writely" /
>
>
>
> The only reason for suggesting this is because your problem sounds
> similar to one experienced in the MyTracks project.
>
> Check out their issue 318:
http://code.google.com/p/mytracks/issues/detail?id=318&can=1&q=permis...