Google OAuth 2.0 and debug key for Google Drive API

Question

I've set up 2 Client IDs for Android application in the GoogleDriveAPI console: the first for the release APK and the second for Debug purposes. Everything ok with the released app, but my issue is only related to the second Client ID. I'm getting this exception: com.google.api.client.googleapis.extensions.android.gms.auth.GoogleAuthIOException

after the following lines:

Drive.Files.List request;
request = service.files().list();
String query = "mimeType='application/vnd.google-apps.folder' AND trashed=false AND title='" + title + "' AND '" + parentId + "' in parents";
request = request.setQ(query);
com.google.api.services.drive.model.FileList files = request.execute(); // <=I'm getting the exception here

I'm using ADT on windows, I've obtained the sha1 fingerprint for debug keystore from Windows->Preferences->Android->Build for the debug mode, but the Google Drive API authorization fails! Why? The (only) solution I've found is to use the "Release" Client ID also in Debug mode, with a custom fingerprint (and that actually works).

I registered both of them in the developer's console. But I use only the 'release' even when debugging for another reason. Once (it might have been a temporary glitch in GooPlaySvcs), I could not get all the files/folders created with the debug when I switched to release. It was in the early GDAA days (March 2014), so it may work now. I would suggest to check if it works OK before you have to download and re-upload 2K files to your phone(as I had to). There is a way to set your environment to produce 'release' SHA1 even when debugging. I'll try to find it and will GIST it soon. — seanpj
Thank you. Yes, it's what I did, I've found it also here: stackoverflow.com/questions/15754060/… — user4569980
Finally I deleted the Debug Client ID (even if it was working fine) from the API console for security reasons — user4569980
I fixed similar error by remove existing app, reinstall latest play store app, test over and over again of old apk and finally the existing development apk is working fine again without figure out the exact reason. — Fruit

seanpj seanpj · Accepted Answer · 2015-02-16T01:41:35

Try this: Take the *.apk file that isn't working (DEBUG.apk), I don't know what's your IDE, so I can't tell you where to find it, but it should be easy.

Open the '*.apk' file in 7-zip or similar unzipper and find 'META-INF\CERT.RSA' file in the archive. Unzip it, for instance to your ...\desktop\
Run 'keytool -printcert -file ...\desktop\CERT.RSA'.
You should see the SHA1 of the APK file in question, compare it with the SHA1 you registered in the console. Double-check the package name as well. PackageName-SHA1 combination is what authorizes the app version with Google Drive.

I vaguely remember this happening to me after re-installing/upgrading my IDE or moving project to another machine (basically generating different debug SHA1 than I registered).

I know it is a long shot, but this is what I use when run into trouble. Hope it helps, Good Luck.

Google OAuth 2.0 and debug key for Google Drive API

1 Answers