Google Drive Api stops working after publishing app

Question

I'm using google drive api in my app which works fine on both debug and release builds when I install it using .apk file.

But if I publish the same release .apk on playstore and then download it from there I can't sign in to Google.

All I can find regarding the issue is that people aren't using release keystore to generate credentials on Google's developer console, which is not the case for me.

while using the app downloaded from store please attach your phone with android studio and check the logcat specified filtered for your app! You shall see the google response there! and also implement the worse Case scenario Toasts/etc for google login call — Rizwan Atta, Jun 29 '18 at 09:37

score 7 · Accepted Answer · answered Jun 29 '18 at 12:38

7

I found a problem:

Check if you have been enrolled in App Signing program under Release Management. If yes, there must be two certificates - upload and App signing.

Copy Sha1 of App Signing certificate and create new OAuth client ID in developer console.

Then go to Firebase Project settings, add copied fingerprint to your app and download google-services.json.

Replace your existing google-services.json in android studio with downloaded one and you are good to go.

I have no idea when or why I enabled this thing. It replaces signing certificate of your uploaded application with the new one.

answered Jun 29 '18 at 12:38

arsena

1,935
19
36

1

THis is caused by Google Play App signing (which is a good thing) https://support.google.com/googleplay/android-developer/answer/7384423 – Nick Fortescue Jul 01 '18 at 08:09
What's connecting between Google Drive API and Firebase? – Yury Matatov Jun 11 '21 at 07:42
1

@YuryMatatov Firebase automatically creates new OAuth 2.0 Client ID for added SHA1 in Cloud Platform. – Menos Jul 01 '21 at 12:12

Google Drive Api stops working after publishing app

1 Answers1

Linked