[英]Failure to login using firebase auth on Android in release mode. DEBUG mode is OK. Code=10, message=10,mPendingCredential=null
I can run from android studio through a wire to my device and login using firebase auth to gmail successfully - with 2 gmail accounts I have.我可以通过电线从 android 工作室运行到我的设备,并使用 firebase 身份验证成功登录到 gmail - 我有 2 个 gmail 帐户。
When I push a release version to testers (mainly in India) they cannot login - error message is"当我将发布版本推送给测试人员(主要在印度)时,他们无法登录 - 错误消息是“
IdpResponse{mUser=null, mToken='null', mSecret='null', mIsNewUser='false', mException=f.f.a.a.e: Code: 10, message: 10: , mPendingCredential=null}
I am convinced it is related to the SHA Certificate fingerprints.我确信它与 SHA 证书指纹有关。 I have 2 fingerprints in the firebase console - (SHA1 and SHA256 ) that match the gradle signing report in android studio.
我在 firebase 控制台中有 2 个指纹(SHA1 和 SHA256)与 android 工作室中的 gradle 签名报告相匹配。 The release 'variant' is the same key as the debug - if this should be different how do I create a 'release' key (as opposed to a debug one) just for the release version and add it when I upload.
发布“变体”与调试是相同的密钥 - 如果这应该不同,我如何为发布版本创建一个“发布”密钥(而不是调试密钥)并在我上传时添加它。
NOTES: I do use the screen - Generate Signed Bundle or APK - which points to the a store path created a long time ago by another developer.注意:我确实使用了屏幕 - Generate Signed Bundle or APK - 它指向另一个开发人员很久以前创建的商店路径。 The code must be correct because debug login works.
代码必须正确,因为调试登录有效。 Some Stackoverflows mentions 3 keys - where is the 3rd from?
一些 Stackoverflows 提到了 3 个键——第 3 个键从哪里来? Also NOTE Play App Signing is enabled.
另请注意 Play App Signing 已启用。
This is the last bug to fix before go live - so any help would be appreciated.这是在 go 上线之前修复的最后一个错误 - 因此我们将不胜感激。
Firebase console: Firebase 控制台:
Thanks John Goodstadt谢谢约翰·古德施塔特
This became solved by me doing 1 thing.我做了一件事就解决了这个问题。 In the Firebase Settings for the project select the 'Integrations' TAB.
在 Firebase 项目 select 的“集成”选项卡的设置中。 And click 'Manage', See image - bottom left box 'Google Play'.
然后点击“管理”,查看图片 - 左下框“Google Play”。 After this the login was fixed.
在此之后登录是固定的。 Many other things were tried.
尝试了许多其他的东西。 Before this make sure that the latest google-services.json file is downloaded - it has a copy of secure keys.
在此之前,请确保已下载最新的 google-services.json 文件 - 它具有安全密钥的副本。
Thanks John Goodstadt谢谢约翰·古德施塔特
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.