问题描述
我正在使用Firebase身份验证在我的应用程序中对用户进行身份验证.
I am using Firebase Authentication for authenticating user in my application.
一切正常，直到我开始为应用程序进行调试构建.但是，一旦我将签名的apk上传到playstore中，我的用户身份验证服务就会始终失败，并显示"Developer Error"消息.
Everything was working fine till I was working on debug build of my application. But the moment I have uploaded the signed apk in playstore, my user authentication service always fails with "Developer Error" message.
在一些网络研究中，我发现我还需要为签名的apk生成SHA证书.我已经使用本地创建的".jks"文件生成了SHA，在上载之前，我曾使用该文件在本地对我的应用程序进行了签名.我已将生成的SHA密钥添加到firebase项目控制台，并生成了新的google-services.json文件.即使这种方法也没有帮助我.
On some web research, I find out that I need to generate SHA certificate for my signed apk also. I have generated SHA with locally created ".jks" file, which I have used to sign my application locally before uploading. I have added the generated SHA keys to firebase project console and generated new google-services.json file. Even this approach has not helped me.
我怀疑这是因为我正在使用"Google Play应用签名( https://developer.android.com/studio/publish/app-signing.html )"，它将再次更改证书.谁能帮助我，让我知道更新发行版APK的SHA密钥的正确过程是什么.
I am suspecting that this is happening because I am using "Google Play App Signing (https://developer.android.com/studio/publish/app-signing.html)" which is again changing the certificate. Can anyone please help me and let me know what is the right process for updating SHA keys for release apk.
如果Play商店正在进行应用程序签名，那么它如何成为"google-services.json"的一部分，必须事先提到SHA键?
If play store is doing the app-signing, then how can it be the part of "google-services.json" where SHA keys must be mentioned beforehand?
请帮助！！！
推荐答案
Google Play控制台中的打开应用签名"部分，并获得应用签名证书的 SHA1
Open App signing section in Google Play Console, and get SHA1 of app signing certificate
这篇关于Firebase身份验证失败，并显示“开发人员错误".将APK上传到Google Play商店后的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！