请求".requestServerAuthCode"时，Google登录8.3.0中的错误12500； [英] error 12500 in google sign in 8.3.0 when requesting ".requestServerAuthCode"

问题描述

使用新的Google标志8.3.0，登录将一直有效，直到请求".requestServerAuthCode(在Oauth 2.0客户端ID下从Web应用程序获取客户端ID")为止.

With the new google sign 8.3.0 the login works until requesting ".requestServerAuthCode("client id from web application under Oauth 2.0 client ids") .

类似于"10381xxxxx183-u8g0o9lig1qli29jxyytrrrewe5lhckfp.apps.googleusercontent.com"

Looks something like "10381xxxxx183-u8g0o9lig1qli29jxyytrrrewe5lhckfp.apps.googleusercontent.com"

如果我要求此服务器验证码，则我的onActivityResult状态为12500.没有它，登录将起作用，并且您将获得成功.

If I ask for this server auth code I get in onActivityResult status 12500. Without it the login works and you get succes.

推荐答案

我也遇到了同样的问题.如果添加了requestServerAuthCode方法，则无法登录.

I also struggled with the same problem. If I added requestServerAuthCode method, I was not able to sign in.

确保在方法requestServerAuthCode

问题出在SHA配置上.我创建了一个密钥库，并用它来生成SHA并在生成google-services.json时提供了它.但是在调试时，应用程序正在使用调试密钥库.

Problem was with SHA configuration. I created a keystore and used it to generate SHA and provided it while generating google-services.json . But while debugging, application was using debug keystore.

在将调试"版本配置为使用相同的密钥存储区之后，一切工作正常. Android Studio中的debug.keystore在哪里

Everything worked fine after I configured 'debug' version to use the same keystore. Where is debug.keystore in Android Studio

希望它会有所帮助. :)

Hope it helps. :)

这篇关于请求".requestServerAuthCode"时，Google登录8.3.0中的错误12500；的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！