Closed GoogleCodeExporter closed 9 years ago
This might be an issue with 1.5:
E/AndroidRuntime( 3750): java.lang.SecurityException: caller pid 3750 uid 10053
lacks com.google.android.googleapps.permission.GOOGLE_AUTH.fusiontables
E/AndroidRuntime( 3750): at android.os.Parcel.readException(Parcel.java:1245)
E/AndroidRuntime( 3750): at android.os.Parcel.readException(Parcel.java:1233)
E/AndroidRuntime( 3750): at
com.google.android.googleapps.IGoogleLoginService$Stub$Proxy.blockingGetCredenti
als(IGoogleLoginService.java:509)
E/AndroidRuntime( 3750): at
com.google.android.googlelogindist.GoogleLoginServiceBlockingHelper.getCredentia
ls(GoogleLoginServiceBlockingHelper.java:503)
E/AndroidRuntime( 3750): at
com.google.android.googlelogindist.GoogleLoginServiceHelper$2.run(GoogleLoginSer
viceHelper.java:336)
Original comment by sandordo...@google.com
on 18 Feb 2011 at 4:57
Sounds easy to fix, though I'm curious why some Android versions would check
this permissions and others wouldn't.
Original comment by rdama...@google.com
on 18 Feb 2011 at 4:00
Original comment by rdama...@google.com
on 18 Feb 2011 at 4:06
Please review:
http://code.google.com/r/rdamazio-mytracks-staging1/source/detail?r=1fa5ba26cc6e
f9a676b93b1083af3acab7b76227
Original comment by rdama...@google.com
on 18 Feb 2011 at 4:09
Original comment by rdama...@google.com
on 18 Feb 2011 at 4:33
If you have time I think there are actually dupes of this bug floating around.
I tried to dedup the issues last night but I did not triage all of the fusion
tables bugs.
Original comment by sandordo...@google.com
on 18 Feb 2011 at 6:05
The problem still exists, despite rdamazio's fix. Here's a log extract from my
ADP1 running stock Android 1.6, when I try to upload to Fusion Tables:
03-01 11:43:53.648 D/MyTracks( 8590): Logging in to fusiontables...
03-01 11:43:54.167 W/GoogleLoginService( 7311): caller pid 8590 uid 10029 lacks
com.google.android.googleapps.permission.GOOGLE_AUTH.fusiontables
03-01 11:43:54.197 W/dalvikvm( 8590): threadid=23: thread exiting with uncaught
exception (group=0x4001da20)
03-01 11:43:54.197 E/AndroidRuntime( 8590): Uncaught handler: thread Thread-15
exiting due to uncaught exception
03-01 11:43:54.267 E/AndroidRuntime( 8590): java.lang.SecurityException: caller
pid 8590 uid 10029 lacks
com.google.android.googleapps.permission.GOOGLE_AUTH.fusiontables
03-01 11:43:54.267 E/AndroidRuntime( 8590): at
android.os.Parcel.readException(Parcel.java:1218)
03-01 11:43:54.267 E/AndroidRuntime( 8590): at
android.os.Parcel.readException(Parcel.java:1206)
03-01 11:43:54.267 E/AndroidRuntime( 8590): at
com.google.android.googleapps.IGoogleLoginService$Stub$Proxy.blockingGetCredenti
als(IGoogleLoginService.java:517)
03-01 11:43:54.267 E/AndroidRuntime( 8590): at
com.google.android.googlelogindist.GoogleLoginServiceBlockingHelper.getCredentia
ls(GoogleLoginServiceBlockingHelper.java:503)
03-01 11:43:54.267 E/AndroidRuntime( 8590): at
com.google.android.googlelogindist.GoogleLoginServiceHelper$2.run(GoogleLoginSer
viceHelper.java:336)
Original comment by simon.le...@gmail.com
on 1 Mar 2011 at 10:57
Concerning dupes: The newly opened #370 seems to be a duplicate of this. (It's
clear that this happens because folks typically only check OPEN issues before
creating new ones :-).
Original comment by simon.le...@gmail.com
on 1 Mar 2011 at 11:02
Issue 370 has been merged into this issue.
Original comment by rdama...@google.com
on 1 Mar 2011 at 2:26
Investigating again.
Original comment by rdama...@google.com
on 1 Mar 2011 at 2:27
Reproduced on 1.6.
Original comment by rdama...@google.com
on 1 Mar 2011 at 2:30
Ok, found the issue - that permission is not declared anywhere in the Android
system libraries.
Working with the Android and Fusion Tables teams to figure out a solution.
Original comment by rdama...@google.com
on 1 Mar 2011 at 3:07
Since we're branching off the My Tracks versions and the main version will be
API level 7 or higher, we don't need to address this in that version.
Also, if you still have 1.5 you should seriously consider upgrading your phone.
Original comment by rdama...@google.com
on 2 Feb 2012 at 2:32
Original issue reported on code.google.com by
alan.m.h...@gmail.com
on 13 Feb 2011 at 6:01Attachments: