Question about Google play accounts and Firebase
If I have this email like abcd@gmail.com and sign into Firebase and create an Android app, I set up authentication and databas and download the google-services.json file. The app works when I build an APK.
Can I now have an account xxxx@gmail.com and sign into Google play developer and release that app? What will happen?
I actually did this and then I could not sign into Firebase using a Google account on the two devices that I tested on. I got the error "Google Sign In error 12500".
Signing in to Firebase using e-mail worked so I guess it´s not a Firebase issue. Signing in using Google credentials works on the debug build and the APK release build, so it's only when building for the Google Play app bundle (.aab) that Google credentials signing gives "Google Sign In error 12500". I have no flavor build only different build types
Any ideas?
Does proguard minifyEnabled work different when build for Google Play (.aab) files? Maybe it removed some files
google-play google-cloud-firestore asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
add a comment |
If I have this email like abcd@gmail.com and sign into Firebase and create an Android app, I set up authentication and databas and download the google-services.json file. The app works when I build an APK.
Can I now have an account xxxx@gmail.com and sign into Google play developer and release that app? What will happen?
I actually did this and then I could not sign into Firebase using a Google account on the two devices that I tested on. I got the error "Google Sign In error 12500".
Signing in to Firebase using e-mail worked so I guess it´s not a Firebase issue. Signing in using Google credentials works on the debug build and the APK release build, so it's only when building for the Google Play app bundle (.aab) that Google credentials signing gives "Google Sign In error 12500". I have no flavor build only different build types
Any ideas?
Does proguard minifyEnabled work different when build for Google Play (.aab) files? Maybe it removed some files
google-play google-cloud-firestore asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
add a comment |
If I have this email like abcd@gmail.com and sign into Firebase and create an Android app, I set up authentication and databas and download the google-services.json file. The app works when I build an APK.
Can I now have an account xxxx@gmail.com and sign into Google play developer and release that app? What will happen?
I actually did this and then I could not sign into Firebase using a Google account on the two devices that I tested on. I got the error "Google Sign In error 12500".
Signing in to Firebase using e-mail worked so I guess it´s not a Firebase issue. Signing in using Google credentials works on the debug build and the APK release build, so it's only when building for the Google Play app bundle (.aab) that Google credentials signing gives "Google Sign In error 12500". I have no flavor build only different build types
Any ideas?
Does proguard minifyEnabled work different when build for Google Play (.aab) files? Maybe it removed some files
google-play google-cloud-firestore asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
If I have this email like abcd@gmail.com and sign into Firebase and create an Android app, I set up authentication and databas and download the google-services.json file. The app works when I build an APK.
Can I now have an account xxxx@gmail.com and sign into Google play developer and release that app? What will happen?
I actually did this and then I could not sign into Firebase using a Google account on the two devices that I tested on. I got the error "Google Sign In error 12500".
Signing in to Firebase using e-mail worked so I guess it´s not a Firebase issue. Signing in using Google credentials works on the debug build and the APK release build, so it's only when building for the Google Play app bundle (.aab) that Google credentials signing gives "Google Sign In error 12500". I have no flavor build only different build types
Any ideas?
Does proguard minifyEnabled work different when build for Google Play (.aab) files? Maybe it removed some files
google-play google-cloud-firestore google-play google-cloud-firestore asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
edited Nov 15 '18 at 20:07
Erik Hellberg
asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
asked Nov 15 '18 at 16:00
Erik HellbergErik Hellberg
6811921
6811921
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Miraculously i found the answer at Thanks to @HadrienPierart
quoite @HadrienPierart writing:
I got stuck on this one for several days until I figured how what was
wrong. I relay with most of the situation described above :
Works fine in debug/local If I build the release package and install
it through adb install it works fine If I check the SHA1 of the
package/keystore, everything is in order and matches the config in
Firebase and the google-services.json And then, once deployed in beta
or released on the store : the google signin fails miserably... And I
noticed that in the App signing part of the Google Play account :
screenshot from 2018-10-26 12-18-57
I checked the play account (important thing to mention at this point :
I did not configure the play account) : And sure enough, my package
was being RE-SIGNED by google play certificate...
When you go to the Release Management > App Signing, you will see the
SHA1 of the keystore being used by Google after yours. Pick it, paste
it in Firebase, update your google-services.json file, redeploy and
VOILA !
I really hope this help others to avoid all the hair pulling I've been
doing these last few days :D
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
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',
autoActivateHeartbeat: false,
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%2f53323330%2fquestion-about-google-play-accounts-and-firebase%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Miraculously i found the answer at Thanks to @HadrienPierart
quoite @HadrienPierart writing:
I got stuck on this one for several days until I figured how what was
wrong. I relay with most of the situation described above :
Works fine in debug/local If I build the release package and install
it through adb install it works fine If I check the SHA1 of the
package/keystore, everything is in order and matches the config in
Firebase and the google-services.json And then, once deployed in beta
or released on the store : the google signin fails miserably... And I
noticed that in the App signing part of the Google Play account :
screenshot from 2018-10-26 12-18-57
I checked the play account (important thing to mention at this point :
I did not configure the play account) : And sure enough, my package
was being RE-SIGNED by google play certificate...
When you go to the Release Management > App Signing, you will see the
SHA1 of the keystore being used by Google after yours. Pick it, paste
it in Firebase, update your google-services.json file, redeploy and
VOILA !
I really hope this help others to avoid all the hair pulling I've been
doing these last few days :D
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
add a comment |
Miraculously i found the answer at Thanks to @HadrienPierart
quoite @HadrienPierart writing:
I got stuck on this one for several days until I figured how what was
wrong. I relay with most of the situation described above :
Works fine in debug/local If I build the release package and install
it through adb install it works fine If I check the SHA1 of the
package/keystore, everything is in order and matches the config in
Firebase and the google-services.json And then, once deployed in beta
or released on the store : the google signin fails miserably... And I
noticed that in the App signing part of the Google Play account :
screenshot from 2018-10-26 12-18-57
I checked the play account (important thing to mention at this point :
I did not configure the play account) : And sure enough, my package
was being RE-SIGNED by google play certificate...
When you go to the Release Management > App Signing, you will see the
SHA1 of the keystore being used by Google after yours. Pick it, paste
it in Firebase, update your google-services.json file, redeploy and
VOILA !
I really hope this help others to avoid all the hair pulling I've been
doing these last few days :D
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
add a comment |
Miraculously i found the answer at Thanks to @HadrienPierart
quoite @HadrienPierart writing:
I got stuck on this one for several days until I figured how what was
wrong. I relay with most of the situation described above :
Works fine in debug/local If I build the release package and install
it through adb install it works fine If I check the SHA1 of the
package/keystore, everything is in order and matches the config in
Firebase and the google-services.json And then, once deployed in beta
or released on the store : the google signin fails miserably... And I
noticed that in the App signing part of the Google Play account :
screenshot from 2018-10-26 12-18-57
I checked the play account (important thing to mention at this point :
I did not configure the play account) : And sure enough, my package
was being RE-SIGNED by google play certificate...
When you go to the Release Management > App Signing, you will see the
SHA1 of the keystore being used by Google after yours. Pick it, paste
it in Firebase, update your google-services.json file, redeploy and
VOILA !
I really hope this help others to avoid all the hair pulling I've been
doing these last few days :D
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
Miraculously i found the answer at Thanks to @HadrienPierart
quoite @HadrienPierart writing:
I got stuck on this one for several days until I figured how what was
wrong. I relay with most of the situation described above :
Works fine in debug/local If I build the release package and install
it through adb install it works fine If I check the SHA1 of the
package/keystore, everything is in order and matches the config in
Firebase and the google-services.json And then, once deployed in beta
or released on the store : the google signin fails miserably... And I
noticed that in the App signing part of the Google Play account :
screenshot from 2018-10-26 12-18-57
I checked the play account (important thing to mention at this point :
I did not configure the play account) : And sure enough, my package
was being RE-SIGNED by google play certificate...
When you go to the Release Management > App Signing, you will see the
SHA1 of the keystore being used by Google after yours. Pick it, paste
it in Firebase, update your google-services.json file, redeploy and
VOILA !
I really hope this help others to avoid all the hair pulling I've been
doing these last few days :D
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
answered Nov 15 '18 at 21:03
Erik HellbergErik Hellberg
6811921
6811921
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.
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%2f53323330%2fquestion-about-google-play-accounts-and-firebase%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
