Google sign in not working after publishing in play store
up vote
23
down vote
favorite
I went through this, and as far as the process goes I did that.
But I when I installed the app from play store I am not able to sign in using the google sign in button.
I have used Firebase for google sign in. When I am clicking the sign in button the option to choose the account is coming but then it is not signing in or doing anything.
So where possibly am I going wrong?
android 
firebase firebase-authentication google-signin edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
asked Sep 4 '16 at 15:11
arqam
1,05221334
|
show 16 more comments
up vote
23
down vote
favorite
I went through this, and as far as the process goes I did that.
But I when I installed the app from play store I am not able to sign in using the google sign in button.
I have used Firebase for google sign in. When I am clicking the sign in button the option to choose the account is coming but then it is not signing in or doing anything.
So where possibly am I going wrong?
android firebase firebase-authentication google-signin edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
asked Sep 4 '16 at 15:11
arqam
1,05221334
Add release keystore SHA1, get new API keys for it, set them in AndroidManifest if needed, and compile with new google-services.json
– Dima Rostopira
Sep 4 '16 at 15:13
@DimaRostopira I already included my project SHA keys in the Firebase account. What else is there and how to add in the Manifest?
– arqam
Sep 4 '16 at 15:16
in Manifest? Nothing, it's required only on some other API. Just get new google-services.json. And check GoogleApiClient init, maybe you use API key here directly
– Dima Rostopira
Sep 4 '16 at 15:17
@DimaRostopira But I have already got the google-services.json from firebase after completing the process. Why to get a new one?
– arqam
Sep 4 '16 at 15:19
1
Yes, in Firebase Console press settings icon at the right of app name, choose project settings and you will see
– Dima Rostopira
Sep 4 '16 at 15:37
|
show 16 more comments
up vote
23
down vote
favorite
up vote
23
down vote
favorite
I went through this, and as far as the process goes I did that.
But I when I installed the app from play store I am not able to sign in using the google sign in button.
I have used Firebase for google sign in. When I am clicking the sign in button the option to choose the account is coming but then it is not signing in or doing anything.
So where possibly am I going wrong?
android firebase firebase-authentication google-signin edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
asked Sep 4 '16 at 15:11
arqam
1,05221334
I went through this, and as far as the process goes I did that.
But I when I installed the app from play store I am not able to sign in using the google sign in button.
I have used Firebase for google sign in. When I am clicking the sign in button the option to choose the account is coming but then it is not signing in or doing anything.
So where possibly am I going wrong?
android firebase firebase-authentication google-signin android firebase firebase-authentication google-signin edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
asked Sep 4 '16 at 15:11
arqam
1,05221334
edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
asked Sep 4 '16 at 15:11
arqam
1,05221334
edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
edited Sep 4 '16 at 21:58
Frank van Puffelen
225k26365392
225k26365392
asked Sep 4 '16 at 15:11
arqam
1,05221334
asked Sep 4 '16 at 15:11
arqam
1,05221334
asked Sep 4 '16 at 15:11
arqam
1,05221334
1,05221334
Add release keystore SHA1, get new API keys for it, set them in AndroidManifest if needed, and compile with new google-services.json
– Dima Rostopira
Sep 4 '16 at 15:13
@DimaRostopira I already included my project SHA keys in the Firebase account. What else is there and how to add in the Manifest?
– arqam
Sep 4 '16 at 15:16
in Manifest? Nothing, it's required only on some other API. Just get new google-services.json. And check GoogleApiClient init, maybe you use API key here directly
– Dima Rostopira
Sep 4 '16 at 15:17
@DimaRostopira But I have already got the google-services.json from firebase after completing the process. Why to get a new one?
– arqam
Sep 4 '16 at 15:19
1
Yes, in Firebase Console press settings icon at the right of app name, choose project settings and you will see
– Dima Rostopira
Sep 4 '16 at 15:37
|
show 16 more comments
Add release keystore SHA1, get new API keys for it, set them in AndroidManifest if needed, and compile with new google-services.json
– Dima Rostopira
Sep 4 '16 at 15:13
@DimaRostopira I already included my project SHA keys in the Firebase account. What else is there and how to add in the Manifest?
– arqam
Sep 4 '16 at 15:16
in Manifest? Nothing, it's required only on some other API. Just get new google-services.json. And check GoogleApiClient init, maybe you use API key here directly
– Dima Rostopira
Sep 4 '16 at 15:17
@DimaRostopira But I have already got the google-services.json from firebase after completing the process. Why to get a new one?
– arqam
Sep 4 '16 at 15:19
1
Yes, in Firebase Console press settings icon at the right of app name, choose project settings and you will see
– Dima Rostopira
Sep 4 '16 at 15:37
Add release keystore SHA1, get new API keys for it, set them in AndroidManifest if needed, and compile with new google-services.json
– Dima Rostopira
Sep 4 '16 at 15:13
Add release keystore SHA1, get new API keys for it, set them in AndroidManifest if needed, and compile with new google-services.json
– Dima Rostopira
Sep 4 '16 at 15:13
@DimaRostopira I already included my project SHA keys in the Firebase account. What else is there and how to add in the Manifest?
– arqam
Sep 4 '16 at 15:16
@DimaRostopira I already included my project SHA keys in the Firebase account. What else is there and how to add in the Manifest?
– arqam
Sep 4 '16 at 15:16
in Manifest? Nothing, it's required only on some other API. Just get new google-services.json. And check GoogleApiClient init, maybe you use API key here directly
– Dima Rostopira
Sep 4 '16 at 15:17
in Manifest? Nothing, it's required only on some other API. Just get new google-services.json. And check GoogleApiClient init, maybe you use API key here directly
– Dima Rostopira
Sep 4 '16 at 15:17
@DimaRostopira But I have already got the google-services.json from firebase after completing the process. Why to get a new one?
– arqam
Sep 4 '16 at 15:19
@DimaRostopira But I have already got the google-services.json from firebase after completing the process. Why to get a new one?
– arqam
Sep 4 '16 at 15:19
1
1
Yes, in Firebase Console press settings icon at the right of app name, choose project settings and you will see
– Dima Rostopira
Sep 4 '16 at 15:37
Yes, in Firebase Console press settings icon at the right of app name, choose project settings and you will see
– Dima Rostopira
Sep 4 '16 at 15:37
|
show 16 more comments
6 Answers
6
active
oldest
votes
up vote
30
down vote
accepted
Update: Google changed behaviour of uploading APK, check answer below!
Release APK and debug APK has different SHA1 and different API keys for google services. Both of them must be added in Firebase Console -> Project settings. Then download google-services.json from here, add it to project and recompile with release keystore using option "Build signed APK". That should work
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
1
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
2
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
|
show 2 more comments
up vote
119
down vote
When you upload an apk to the play store then play store creates a new SHA1 key called "App signing certificate". You get that SHA1 and save in your console or firebase account (as you need).
New SHA1 will be found at Released Management->App Sigining on your play console.
[
]
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
10
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
2
Thanks @Prinkal for pointing outReleased Management->App Sigining
– Abhishek Singh
Jun 7 '17 at 6:59
1
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
4
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
1
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
|
show 21 more comments
up vote
2
down vote
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of project overview] (top of the screen) >> Project Settings >> General [Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:48
Alan Nelson
3311317
add a comment |
up vote
1
down vote
There are three types of SHA1 is required for an app lifecycle when you are using firebase
-debug SHA1
-release SHA1
-signing SHA1 (it getting from play store)
You need to add signing SHA1 to firebase after publish your application here i am attaching two screen shots please have a look . The red marked certificates is must be required
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
add a comment |
up vote
1
down vote
Issue happens because
1) when you create / publish an app through google play console, there is an option for enable Google Play App Signing. if you enable it will show
Google Play App Signing is enabled for this app.
then your Upload certificate details will change and you need to rewrite SHA-1 etc. certificate details in respective places.
2) You provided debug key store / SHA-1 certificate details instead of RELEASE certificate details
3) error while generating certificates.
Solution
1) Go to google play console
Relese management -> App signing
then you can see two types of certificate
1- Upload certificate ( your app certificate provided when generating signed apk)
2- App signing certificate ( because you enabled Google Play App Signing, so they provided new certificate details for your published apk)
you need to change uploaded certificate details with new details
provided by google play where ever you used it before. such as
Integrating google sign in (change SHA-1 of OAuth client),
facebook login (change key Hash (generate key hash using SHA-1
use this link or copy the key hash provided by facebook login
error screen), firebase etc.
2) provide release SHA-1 / keyHash
create / use Keystore details of signed apk.
using command prompt:
google / firebase SHA-1 :
keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
facebook release key hash:
keytool -exportcert -alias <user alias name> -keystore < keystore path> | <openssl-path> sha1 -binary | <openssl-path> base64
if asked for password enter your signed apk keystore password.
edited Dec 7 at 7:27
Moritz
57.2k19131184
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
add a comment |
up vote
0
down vote
To add on existing responses, once you have the newly created SHA1:
Goto https://console.firebase.google.com:
- Select project
- Project Overview
- Project Settings
ADD FINGERPRINT - enter SHA1 to Certificate fingerprint- Save
answered Oct 21 at 10:04
RonTLV
1,1051823
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f39318370%2fgoogle-sign-in-not-working-after-publishing-in-play-store%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
30
down vote
accepted
Update: Google changed behaviour of uploading APK, check answer below!
Release APK and debug APK has different SHA1 and different API keys for google services. Both of them must be added in Firebase Console -> Project settings. Then download google-services.json from here, add it to project and recompile with release keystore using option "Build signed APK". That should work
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
1
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
2
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
|
show 2 more comments
up vote
30
down vote
accepted
Update: Google changed behaviour of uploading APK, check answer below!
Release APK and debug APK has different SHA1 and different API keys for google services. Both of them must be added in Firebase Console -> Project settings. Then download google-services.json from here, add it to project and recompile with release keystore using option "Build signed APK". That should work
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
1
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
2
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
|
show 2 more comments
up vote
30
down vote
accepted
up vote
30
down vote
accepted
Update: Google changed behaviour of uploading APK, check answer below!
Release APK and debug APK has different SHA1 and different API keys for google services. Both of them must be added in Firebase Console -> Project settings. Then download google-services.json from here, add it to project and recompile with release keystore using option "Build signed APK". That should work
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
Update: Google changed behaviour of uploading APK, check answer below!
Release APK and debug APK has different SHA1 and different API keys for google services. Both of them must be added in Firebase Console -> Project settings. Then download google-services.json from here, add it to project and recompile with release keystore using option "Build signed APK". That should work
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
edited Sep 2 '17 at 12:58
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
answered Sep 4 '16 at 16:24
Dima Rostopira
3,3633252
3,3633252
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
1
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
2
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
|
show 2 more comments
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
1
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
2
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
Yes it worked perfectly.
– arqam
Sep 4 '16 at 16:25
1
1
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@arqam great ;) Thanks for accepting answer
– Dima Rostopira
Sep 4 '16 at 16:29
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
@DimaRostopira Can you please explain me how to add "API Keys" for debug and release mode? i have created project in firebase console.
– Maulik patel
Sep 1 '17 at 13:34
2
2
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
@Maulikpatel behaviour has changed, check answer below
– Dima Rostopira
Sep 2 '17 at 12:57
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
I have also generated sha1 for release apk but still after publishing the app on play store google login not working,
– Lovekush Vishwakarma
Sep 22 '17 at 6:15
|
show 2 more comments
up vote
119
down vote
When you upload an apk to the play store then play store creates a new SHA1 key called "App signing certificate". You get that SHA1 and save in your console or firebase account (as you need).
New SHA1 will be found at Released Management->App Sigining on your play console.
[]
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
10
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
2
Thanks @Prinkal for pointing outReleased Management->App Sigining
– Abhishek Singh
Jun 7 '17 at 6:59
1
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
4
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
1
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
|
show 21 more comments
up vote
119
down vote
When you upload an apk to the play store then play store creates a new SHA1 key called "App signing certificate". You get that SHA1 and save in your console or firebase account (as you need).
New SHA1 will be found at Released Management->App Sigining on your play console.
[]
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
10
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
2
Thanks @Prinkal for pointing outReleased Management->App Sigining
– Abhishek Singh
Jun 7 '17 at 6:59
1
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
4
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
1
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
|
show 21 more comments
up vote
119
down vote
up vote
119
down vote
When you upload an apk to the play store then play store creates a new SHA1 key called "App signing certificate". You get that SHA1 and save in your console or firebase account (as you need).
New SHA1 will be found at Released Management->App Sigining on your play console.
[]
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
When you upload an apk to the play store then play store creates a new SHA1 key called "App signing certificate". You get that SHA1 and save in your console or firebase account (as you need).
New SHA1 will be found at Released Management->App Sigining on your play console.
[]
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
edited Feb 13 at 6:15
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
answered Jun 2 '17 at 13:22
Prinkal Kumar
1,2552412
1,2552412
10
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
2
Thanks @Prinkal for pointing outReleased Management->App Sigining
– Abhishek Singh
Jun 7 '17 at 6:59
1
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
4
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
1
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
|
show 21 more comments
10
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
2
Thanks @Prinkal for pointing outReleased Management->App Sigining
– Abhishek Singh
Jun 7 '17 at 6:59
1
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
4
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
1
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
10
10
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
Thanks man you saved my life!!
– Shashank Verma
Jun 7 '17 at 6:56
2
2
Thanks @Prinkal for pointing out
Released Management->App Sigining– Abhishek Singh
Jun 7 '17 at 6:59
Thanks @Prinkal for pointing out
Released Management->App Sigining– Abhishek Singh
Jun 7 '17 at 6:59
1
1
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
@Abhisek great :) Thanks for accepting answer
– Prinkal Kumar
Jun 8 '17 at 10:54
4
4
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
Thanks you legend! After 5 hours of pain I found your answer
– Sam Matthews
Jul 19 '17 at 15:38
1
1
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
@PrinkalKumar after uploading an apk to playstore, and adding SHA1 of App signing to firebase console with debug SHA1. Do I need to re-download the google-services.json file and publish the signed apk again? Do reply.
– Pankaj Lilan
Aug 3 '17 at 4:46
|
show 21 more comments
up vote
2
down vote
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of project overview] (top of the screen) >> Project Settings >> General [Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:48
Alan Nelson
3311317
add a comment |
up vote
2
down vote
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of project overview] (top of the screen) >> Project Settings >> General [Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:48
Alan Nelson
3311317
add a comment |
up vote
2
down vote
up vote
2
down vote
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of project overview] (top of the screen) >> Project Settings >> General [Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:48
Alan Nelson
3311317
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of project overview] (top of the screen) >> Project Settings >> General [Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:48
Alan Nelson
3311317
answered Nov 12 at 7:48
Alan Nelson
3311317
answered Nov 12 at 7:48
Alan Nelson
3311317
answered Nov 12 at 7:48
Alan Nelson
3311317
3311317
add a comment |
add a comment |
up vote
1
down vote
There are three types of SHA1 is required for an app lifecycle when you are using firebase
-debug SHA1
-release SHA1
-signing SHA1 (it getting from play store)
You need to add signing SHA1 to firebase after publish your application here i am attaching two screen shots please have a look . The red marked certificates is must be required
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
add a comment |
up vote
1
down vote
There are three types of SHA1 is required for an app lifecycle when you are using firebase
-debug SHA1
-release SHA1
-signing SHA1 (it getting from play store)
You need to add signing SHA1 to firebase after publish your application here i am attaching two screen shots please have a look . The red marked certificates is must be required
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
add a comment |
up vote
1
down vote
up vote
1
down vote
There are three types of SHA1 is required for an app lifecycle when you are using firebase
-debug SHA1
-release SHA1
-signing SHA1 (it getting from play store)
You need to add signing SHA1 to firebase after publish your application here i am attaching two screen shots please have a look . The red marked certificates is must be required
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
There are three types of SHA1 is required for an app lifecycle when you are using firebase
-debug SHA1
-release SHA1
-signing SHA1 (it getting from play store)
You need to add signing SHA1 to firebase after publish your application here i am attaching two screen shots please have a look . The red marked certificates is must be required
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
answered Nov 29 at 7:09
Muhammed Fasil
1,8511413
1,8511413
add a comment |
add a comment |
up vote
1
down vote
Issue happens because
1) when you create / publish an app through google play console, there is an option for enable Google Play App Signing. if you enable it will show
Google Play App Signing is enabled for this app.
then your Upload certificate details will change and you need to rewrite SHA-1 etc. certificate details in respective places.
2) You provided debug key store / SHA-1 certificate details instead of RELEASE certificate details
3) error while generating certificates.
Solution
1) Go to google play console
Relese management -> App signing
then you can see two types of certificate
1- Upload certificate ( your app certificate provided when generating signed apk)
2- App signing certificate ( because you enabled Google Play App Signing, so they provided new certificate details for your published apk)
you need to change uploaded certificate details with new details
provided by google play where ever you used it before. such as
Integrating google sign in (change SHA-1 of OAuth client),
facebook login (change key Hash (generate key hash using SHA-1
use this link or copy the key hash provided by facebook login
error screen), firebase etc.
2) provide release SHA-1 / keyHash
create / use Keystore details of signed apk.
using command prompt:
google / firebase SHA-1 :
keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
facebook release key hash:
keytool -exportcert -alias <user alias name> -keystore < keystore path> | <openssl-path> sha1 -binary | <openssl-path> base64
if asked for password enter your signed apk keystore password.
edited Dec 7 at 7:27
Moritz
57.2k19131184
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
add a comment |
up vote
1
down vote
Issue happens because
1) when you create / publish an app through google play console, there is an option for enable Google Play App Signing. if you enable it will show
Google Play App Signing is enabled for this app.
then your Upload certificate details will change and you need to rewrite SHA-1 etc. certificate details in respective places.
2) You provided debug key store / SHA-1 certificate details instead of RELEASE certificate details
3) error while generating certificates.
Solution
1) Go to google play console
Relese management -> App signing
then you can see two types of certificate
1- Upload certificate ( your app certificate provided when generating signed apk)
2- App signing certificate ( because you enabled Google Play App Signing, so they provided new certificate details for your published apk)
you need to change uploaded certificate details with new details
provided by google play where ever you used it before. such as
Integrating google sign in (change SHA-1 of OAuth client),
facebook login (change key Hash (generate key hash using SHA-1
use this link or copy the key hash provided by facebook login
error screen), firebase etc.
2) provide release SHA-1 / keyHash
create / use Keystore details of signed apk.
using command prompt:
google / firebase SHA-1 :
keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
facebook release key hash:
keytool -exportcert -alias <user alias name> -keystore < keystore path> | <openssl-path> sha1 -binary | <openssl-path> base64
if asked for password enter your signed apk keystore password.
edited Dec 7 at 7:27
Moritz
57.2k19131184
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
add a comment |
up vote
1
down vote
up vote
1
down vote
Issue happens because
1) when you create / publish an app through google play console, there is an option for enable Google Play App Signing. if you enable it will show
Google Play App Signing is enabled for this app.
then your Upload certificate details will change and you need to rewrite SHA-1 etc. certificate details in respective places.
2) You provided debug key store / SHA-1 certificate details instead of RELEASE certificate details
3) error while generating certificates.
Solution
1) Go to google play console
Relese management -> App signing
then you can see two types of certificate
1- Upload certificate ( your app certificate provided when generating signed apk)
2- App signing certificate ( because you enabled Google Play App Signing, so they provided new certificate details for your published apk)
you need to change uploaded certificate details with new details
provided by google play where ever you used it before. such as
Integrating google sign in (change SHA-1 of OAuth client),
facebook login (change key Hash (generate key hash using SHA-1
use this link or copy the key hash provided by facebook login
error screen), firebase etc.
2) provide release SHA-1 / keyHash
create / use Keystore details of signed apk.
using command prompt:
google / firebase SHA-1 :
keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
facebook release key hash:
keytool -exportcert -alias <user alias name> -keystore < keystore path> | <openssl-path> sha1 -binary | <openssl-path> base64
if asked for password enter your signed apk keystore password.
edited Dec 7 at 7:27
Moritz
57.2k19131184
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
Issue happens because
1) when you create / publish an app through google play console, there is an option for enable Google Play App Signing. if you enable it will show
Google Play App Signing is enabled for this app.
then your Upload certificate details will change and you need to rewrite SHA-1 etc. certificate details in respective places.
2) You provided debug key store / SHA-1 certificate details instead of RELEASE certificate details
3) error while generating certificates.
Solution
1) Go to google play console
Relese management -> App signing
then you can see two types of certificate
1- Upload certificate ( your app certificate provided when generating signed apk)
2- App signing certificate ( because you enabled Google Play App Signing, so they provided new certificate details for your published apk)
you need to change uploaded certificate details with new details
provided by google play where ever you used it before. such as
Integrating google sign in (change SHA-1 of OAuth client),
facebook login (change key Hash (generate key hash using SHA-1
use this link or copy the key hash provided by facebook login
error screen), firebase etc.
2) provide release SHA-1 / keyHash
create / use Keystore details of signed apk.
using command prompt:
google / firebase SHA-1 :
keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
facebook release key hash:
keytool -exportcert -alias <user alias name> -keystore < keystore path> | <openssl-path> sha1 -binary | <openssl-path> base64
if asked for password enter your signed apk keystore password.
edited Dec 7 at 7:27
Moritz
57.2k19131184
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
edited Dec 7 at 7:27
Moritz
57.2k19131184
edited Dec 7 at 7:27
Moritz
57.2k19131184
edited Dec 7 at 7:27
Moritz
57.2k19131184
57.2k19131184
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
answered Dec 7 at 5:31
Adarsh Vijayan P
611212
611212
add a comment |
add a comment |
up vote
0
down vote
To add on existing responses, once you have the newly created SHA1:
Goto https://console.firebase.google.com:
- Select project
- Project Overview
- Project Settings
ADD FINGERPRINT - enter SHA1 to Certificate fingerprint- Save
answered Oct 21 at 10:04
RonTLV
1,1051823
add a comment |
up vote
0
down vote
To add on existing responses, once you have the newly created SHA1:
Goto https://console.firebase.google.com:
- Select project
- Project Overview
- Project Settings
ADD FINGERPRINT - enter SHA1 to Certificate fingerprint- Save
answered Oct 21 at 10:04
RonTLV
1,1051823
add a comment |
up vote
0
down vote
up vote
0
down vote
To add on existing responses, once you have the newly created SHA1:
Goto https://console.firebase.google.com:
- Select project
- Project Overview
- Project Settings
ADD FINGERPRINT - enter SHA1 to Certificate fingerprint- Save
answered Oct 21 at 10:04
RonTLV
1,1051823
To add on existing responses, once you have the newly created SHA1:
Goto https://console.firebase.google.com:
- Select project
- Project Overview
- Project Settings
ADD FINGERPRINT - enter SHA1 to Certificate fingerprint- Save
answered Oct 21 at 10:04
RonTLV
1,1051823
edited Oct 21 at 10:21
answered Oct 21 at 10:04
RonTLV
1,1051823
answered Oct 21 at 10:04
RonTLV
1,1051823
answered Oct 21 at 10:04
RonTLV
1,1051823
1,1051823
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f39318370%2fgoogle-sign-in-not-working-after-publishing-in-play-store%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Add release keystore SHA1, get new API keys for it, set them in AndroidManifest if needed, and compile with new google-services.json
– Dima Rostopira
Sep 4 '16 at 15:13
@DimaRostopira I already included my project SHA keys in the Firebase account. What else is there and how to add in the Manifest?
– arqam
Sep 4 '16 at 15:16
in Manifest? Nothing, it's required only on some other API. Just get new google-services.json. And check GoogleApiClient init, maybe you use API key here directly
– Dima Rostopira
Sep 4 '16 at 15:17
@DimaRostopira But I have already got the google-services.json from firebase after completing the process. Why to get a new one?
– arqam
Sep 4 '16 at 15:19
1
Yes, in Firebase Console press settings icon at the right of app name, choose project settings and you will see
– Dima Rostopira
Sep 4 '16 at 15:37