google-play - 关于 Google Play 帐户和 Firebase 的问题

Question

如果我有这个像 abcd@gmail.com 这样的电子邮件并登录 Firebase 并创建一个 Android 应用程序，我会设置身份验证和数据库并下载 google-services.json 文件。该应用程序在我构建 APK 时有效。

我现在可以拥有一个帐户 xxxx@gmail.com 并登录 Google Play 开发者并发布该应用程序吗？会发生什么？

我实际上是这样做的，然后我无法在我测试的两台设备上使用 Google 帐户登录 Firebase。我收到错误“Google 登录错误 12500”。

使用电子邮件登录 Firebase 有效，所以我猜这不是 Firebase 问题。使用 Google 凭据登录适用于调试版本和 APK 发布版本，因此只有在为 Google Play 应用程序包 (.aab) 构建时，Google 凭据签名才会给出“Google 登录错误 12500”。我没有 flavor 构建只有不同的构建类型

有任何想法吗？

为 Google Play (.aab) 文件构建时，proguard minifyEnabled 的工作方式是否不同？也许它删除了一些文件

Answer 1

奇迹般地，我在 Thanks to @HadrienPierart 找到了答案

引用@HadrienPierart 写作:

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