blocks|key|124761|text|您可能缺少开发控制台注册。开发人员通常会有多个签名证书配置:调试密钥库、测试环境签名证书、生产签名证书。签名证书SHA1+%2B包名唯一标识安卓客户端，需要在开发控制台单独注册。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124762|要了解更多关于OAuth客户端注册的信息，请参阅下面的博客：|124763|http://android-developers.blogspot.com/2016/03/registering-oauth-clients-for-google.html|offset|length|124764|或者看看这篇文章：Test+google+signin+on+Android+in+development+phase|124765|entityMap|0|LINK|mutability|MUTABLE|url|1|https://stackoverflow.com/questions/34811645/test-google-signin-on-android-in-development-phase/35075641#35075641^0|0|0|0|2G|0|0|9|1E|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@$F|V|G|W|1|X]]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]|Q|$5|M|N|O|A|$P|R]]]]

You are probably missing dev console registration. It's very common developers will have multiple signing cert configuration: debug key store, test environment signing cert, production signing cert. signing cert SHA1 + package name uniquely identifies an Android client and needs to be registered individually in dev console. 

See below blogpost to understand more about OAuth clients registration:

<a href="http://android-developers.blogspot.com/2016/03/registering-oauth-clients-for-google.html" rel="noreferrer">http://android-developers.blogspot.com/2016/03/registering-oauth-clients-for-google.html</a>

Or see this post:
<a href="https://stackoverflow.com/questions/34811645/test-google-signin-on-android-in-development-phase/35075641#35075641">Test google signin on Android in development phase</a>

blocks|key|2890876|text|我也有同样的问题，这是由于|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2890877|apply+plugin:+'com.google.gms.google-services'|code-block|syntax|javascript|2890878|而不是在应用程序build.gradle的底部。|2890879|通过查看Gradle控制台就知道了。未引发任何错误。|2890880|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same problem and it was due to 

<pre><code>apply plugin: 'com.google.gms.google-services'
</code></pre>

not being at the bottom of the app build.gradle.

Figured it out by looking at the Gradle Console. No errors were raised.

blocks|key|2890895|text|原因可能是：-你可能正在使用一个未签名的apk来测试你的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2890896|转到Build->Generate+Signed+APK+->，使用您用来获取SHA1指纹的密钥对其进行签名，以便在谷歌开发人员控制台上进行clientID|offset|length|style|BOLD|2890897|运行app-debug.apk就完成了！！|2890898|entityMap^0|0|2|T|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Reason for the can be:
- You might be using an unsigned apk to test you app.

Go to Build->Generate Signed APK -> sign it with the key you used to get your SHA1 Fingerprint to make clientID on google developer console

Run app-debug.apk and its done!!

blocks|key|2890910|text|编辑的|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2890911|答案来自this，因为它也适用于这个问题|2890912|我把答案附在这里|2890913|该问题是由于签名证书和SHA-1证书指纹造成的。将以下SHA-1证书添加到您的googleApi凭据中。有两个案例|2890914|1.如果您在调试模式下运行，请添加由以下命令生成的SHA-1指纹|2890915|"C:\Program+Files\Java\jre1.8.0_101\bin\keytool"+-list+-v+-keystore+"%25USERPROFILE%25\.android\debug.keystore"+-alias+androiddebugkey+-storepass+android+-keypass+android|code-block|syntax|javascript|2890916|2.如果您已配置签名配置，则使用通过以下方式生成的SHA-1指纹|2890917|"C:\Program+Files\Java\jre1.8.0_101\bin\keytool"+-list+-v+-keystore+"[youKeyPath]\youKey.jks"|2890918|我建议您在googleApi凭据中添加这两个SHA-1指纹|2890919|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/40508344/6082645^0|0|3|0|4|4|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|H|3|I|5|6|7|1D|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1G|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1H|8|@]|D|@]|E|$]]|$1|U|3|V|5|P|7|1I|8|@]|D|@]|E|$Q|R]]|$1|W|3|X|5|6|7|1J|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]]]

EDITED

The answer is derived from <a href="https://stackoverflow.com/a/40508344/6082645">this</a>, as it will applicable for this problem also

I am Enclosing the Answer here

The problem is due to the Signing Certificate and the SHA-1 certificate fingerprint. Add the following SHA-1 certificates into your googleApi credentials. there are 2 cases

1.If you are running in debug mode add the SHA-1 fingerprint generated by the following

<pre><code>"C:\Program Files\Java\jre1.8.0_101\bin\keytool" -list -v -keystore "%USERPROFILE%\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android
</code></pre>

2.If you have configured Signing Config then use SHA-1 fingerprint generated by following

<pre><code>"C:\Program Files\Java\jre1.8.0_101\bin\keytool" -list -v -keystore "[youKeyPath]\youKey.jks"
</code></pre>

I recommend you to add both the SHA-1 fingerprints in your googleApi credentials

blocks|key|124861|text|除了上面的答案之外，我还遇到了一个问题，是由于配置与google-services.json文件不匹配而导致的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124862|也有可能是在GoogleSignInOptions生成器中专门指定了clientId，如下所示：|124863|++++String+serverClientId+=+"xxxxx-yyyy.apps.googleusercontent.com";
++++GoogleSignInOptions+gso+=+new+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
++++++++++++.requestEmail()
++++++++++++.requestIdToken(serverClientId)
++++++++++++.build();|code-block|syntax|javascript|124864|如果是这种情况，可以删除对serverClientId和requestIdToken调用的引用，如下所示：|124865|++++GoogleSignInOptions+gso+=+new+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
++++++++++++.requestEmail()
++++++++++++.build();|124866|这将依赖于google-services.json，而不是配置期间的硬编码值。|124867|我希望它能为其他人省去我试图诊断项目故障的麻烦。|124868|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

In addition to the above answers, I came across one case where the problem was caused due to the configuration was mismatched to the google-services.json file:

It is also possible that the clientId was specifically assigned in the GoogleSignInOptions Builder as shown below:

<pre><code> String serverClientId = "xxxxx-yyyy.apps.googleusercontent.com";
 GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestEmail()
 .requestIdToken(serverClientId)
 .build();
</code></pre>

If this is the case, it is possible to remove the reference to the serverClientId and the requestIdToken call as shown below:

<pre><code> GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestEmail()
 .build();
</code></pre>

This would then rely on the google-services.json as opposed to the hard-coded value during configuration.

I hope it saves someone else the trouble that I had trying to diagnose the fault with my project.

blocks|key|124875|text|根据this，您需要在Firebase项目设置中使用3+SHA1+keys|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|124876|在大多数情况下，问题出在的第三个密钥。|124877|124878|调试密钥|ordered-list-item|124879|124880|keytool+-list+-v+-alias+androiddebugkey+-keystore+~/.android/debug.keystore|CODE|124881|124882|发行版密钥|124883|124884|keytool+-list+-v+-alias+YOUR_RELEASE_KEY_ALIAS+-keystore+YOUR_RELEASE_KEY_PATH|124885|124886|谷歌Play应用签名密钥|124887|124888|https://play.google.com/apps/publish/|124889|新的play+publish+console的更新|124890|-+in+your+app's+`Release+menu`+>++`App+integrity`+>+`App+signing+certificate`|code-block|syntax|javascript|124891|旧的play发布控制台中的|124892|-+in+your+app's+`Release+management`+>++`App+signing`+>+`App+signing+certificate`|124893|这是SHA1密钥|124894|你需要三把钥匙才能找到一个谷歌SignIn。|124895|确保它始终是+SHA1，而不是SHA256|124896|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/googlesamples/google-services/issues/360#issuecomment-404681049|1^0|Q|B|2|4|0|0|C|6|0|0|0|0|0|23|0|0|0|0|0|26|0|0|0|0|0|11|1|0|N|2|0|0|0|B|0|0|0|8|0|0|M|0|0|6|7|E|0^^$0|@$1|2|3|4|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@$9|1U|A|1V|1|1W]]|E|$]]|$1|F|3|G|5|6|7|1X|8|@$9|1Y|A|1Z|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|20|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|21|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|22|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|23|8|@$9|24|A|25|B|O]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|Q|3|R|5|K|7|27|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|28|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|29|8|@$9|2A|A|2B|B|O]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|2C|8|@]|D|@]|E|$]]|$1|W|3|X|5|K|7|2D|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|2E|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2F|8|@]|D|@$9|2G|A|2H|1|2I]]|E|$]]|$1|11|3|12|5|6|7|2J|8|@$9|2K|A|2L|B|C]]|D|@]|E|$]]|$1|13|3|14|5|15|7|2M|8|@]|D|@]|E|$16|17]]|$1|18|3|19|5|6|7|2N|8|@$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|1A|3|1B|5|15|7|2Q|8|@]|D|@]|E|$16|17]]|$1|1C|3|1D|5|6|7|2R|8|@$9|2S|A|2T|B|C]]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|2U|8|@$9|2V|A|2W|B|C]]|D|@]|E|$]]|$1|1G|3|1H|5|6|7|2X|8|@$9|2Y|A|2Z|B|C]|$9|30|A|31|B|C]]|D|@]|E|$]]|$1|1I|3|-4|5|6|7|32|8|@]|D|@]|E|$]]]|1J|$1K|$5|1L|1M|1N|E|$1O|1P]]|1Q|$5|1L|1M|1N|E|$1O|10]]]]

As per <a href="https://github.com/googlesamples/google-services/issues/360#issuecomment-404681049" rel="nofollow noreferrer">this</a> you need 3 SHA1 keys in Firebase project settings
In most of the case, the problem is the third key.
<ol>
<li>The debug key
<code>keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore</code>
</li>
<li>The release key
<code>keytool -list -v -alias YOUR_RELEASE_KEY_ALIAS -keystore YOUR_RELEASE_KEY_PATH</code>
</li>
<li>Google Play App signing key
<a href="https://play.google.com/apps/publish/" rel="nofollow noreferrer">https://play.google.com/apps/publish/</a>
Update for new play publish console
<ul>
<li>in your app's <code>Release menu</code> &gt; <code>App integrity</code> &gt; <code>App signing certificate</code></li>
</ul>
In old play publish console
<ul>
<li>in your app's <code>Release management</code> &gt; <code>App signing</code> &gt; <code>App signing certificate</code></li>
</ul>
it's SHA1 key
</li>
</ol>
You need THREE keys to figure out ONE Google SignIn.
Make Sure it's always SHA1, not SHA256

I have been following this tutorial to get Google SignOn going:
<a href="https://developers.google.com/identity/sign-in/android/start-integrating">https://developers.google.com/identity/sign-in/android/start-integrating</a>

When I run my application locally with a virtual device it works fine but when I deploy it to my device via debugging or if I generate a signed jar file and copy it manual <code>GoogleSignInResult</code> always returns <code>false</code> with an <code>INTERNAL ERROR</code> message.

I'm struggling since quite a while to be able to use google login when deploying the application via debug to my device. Any help is highly appreciated!

Solution for My Issue:

Where you download the json file you have to copy past the code that you can generate with the java key tool. I totally missed that a few times in a row.

Android Google SignIn not working in debug mode: GoogleSignInResult is false

OAuth

Java

为了让谷歌SignOn上线，我一直在遵循这个教程：当我使用虚拟设备在本地运行我的应用程序时，它工作得很好，但是当我通过调试将它部署到我的设备上时，或者如果我生成一个签名的jar文件并手动复制它，GoogleSignInResult总是返回带有INTERNAL ERROR消息的false。当通过debug将应用程序部署到...

问Android Google SignIn无法在调试模式下工作: GoogleSignInResult为false
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android Google SignIn无法在调试模式下工作: GoogleSignInResult为falseEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android Google SignIn无法在调试模式下工作: GoogleSignInResult为false
EN