blocks|key|124552|text|我也有同样的问题，我注意到当我的server_client_id包含一些不正确的值时，返回了12501代码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|124553|由于没有详细的消息，并且此错误代码的文档也相当糟糕，我不知道您的问题是否与我的问题具有相同的原因。|124554|124555|我的应用程序基于this+example+(IdTokenActivity类)的安卓代码。为了让它工作，我还需要在我的应用程序中使用integrate+Google+sign-in：|124556|124557|生成的json配置文件启用了谷歌登录|unordered-list-item|124558|在我的gradle文件中添加了谷歌插件和依赖项|124559|为此应用程序创建了OAuth客户端ID并将其保存在我的项目中|124560|124561|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/googlesamples/google-services/tree/master/android/signin|1|https://developers.google.com/identity/sign-in/android/start-integrating^0|G|G|0|0|0|8|C|0|1U|O|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|17|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]|$9|1C|A|1D|1|1E]]|E|$]]|$1|K|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1G|8|@]|D|@]|E|$]]|$1|O|3|P|5|N|7|1H|8|@]|D|@]|E|$]]|$1|Q|3|R|5|N|7|1I|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]|11|$5|W|X|Y|E|$Z|12]]]]

I had the same problem and I noticed that 12501 code was returned when my <code>server_client_id</code> contained some incorrect value.

Since there is no detailed message and the documentation of this error code is rather poor I don't know if your problem has the same cause as mine.

<hr>

My application is based on Android code from <a href="https://github.com/googlesamples/google-services/tree/master/android/signin" rel="nofollow">this example</a> (class IdTokenActivity).
To make it work I also needed to <a href="https://developers.google.com/identity/sign-in/android/start-integrating" rel="nofollow">integrate Google sign-in</a> into my app:

<ul>
<li>generated json config file with enabled Google Sign-In</li>
<li>added Google plugin and dependency to my gradle file</li>
<li>created OAuth client ID for this app and saved it in my project as <code>server_client_id</code></li>
</ul>

blocks|key|123460|text|你的apk是否处于调试模式？我想它只适用于签名的apk。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|123461|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Is your apk in debug mode? I think it only works with a signed apk.

blocks|key|126010|text|想清楚怎么解决这个问题...我在尝试运行我的应用程序的调试版本时遇到此错误...要修复它，请在开发人员控制台和google-services.json上为您的调试应用程序添加凭据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126011|这为我解决了这个问题！|126012|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Just figure out how to solve this... I was getting this error while trying to run the debug version of my app... To fix it, add a credential for your debug app on the developer console and also on the google-services.json.

this fixed it for me!

blocks|key|123510|text|我遇到了完全相同的问题，我已经找到了解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|123511|如果您遵循此处提供的文档：https://developers.google.com/identity/sign-in/android/start-integrating|offset|length|123512|第一步是创建配置文件(它为您创建一个OAuth+2.0客户机ID并将其插入到google-services.json文件中)|123513|然后，它再次提到要创建Web2.0客户机ID，但这一次它说您必须为+OAuth应用程序执行此操作|style|BOLD|123514|这就是令人困惑的部分！(至少对我来说是这样)，因为我只是采用了为android+OAuth创建的客户端id，而不是为Web应用程序创建一个新的客户端id(我认为文档只是多余的或者别的什么)|123515|正如它所说的，它就是这个，而且只有这个才是您必须用作requestIdToken或requestServerAuthCode方法的参数的那个。|123516|忘记在此方法中使用Android+OAuth+ID，因为这样您将始终得到丑陋的状态码响应12501。|123517|我认为主要的问题是文档对此有点混乱。或者可能是因为您必须创建两个OAuth+is这一事实有点奇怪。|123518|总之，您需要两个OAuth+ID，一个用于安卓，另一个用于web应用程序，并且您必须将每个ID设置在正确的位置。|123519|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/identity/sign-in/android/start-integrating^0|0|D|20|0|0|0|X|A|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@$D|1A|E|1B|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1E|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1F|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1G|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]]]

I had exactly the same problem and i have found the solution.

If you follow the documentation found here:
<a href="https://developers.google.com/identity/sign-in/android/start-integrating">https://developers.google.com/identity/sign-in/android/start-integrating</a>

The first step tells you to create the configuration file (which creates an OAuth 2.0 client ID for you and inserts it into the google-services.json)

Then later, it says again about creating a OAuth 2.0 client ID, but this time it says that you have to do it for Web application

And this is the confusing part! (at least for me) because i was just taking the client id created for the android OAuth and not creating a new one for Web application (I thought the documentation was just redundant or something)

As it says, it is this one, and only this one the one you have to use as a parameter of the methods requestIdToken or requestServerAuthCode.

Forget about using the Android OAuth ID in this methods because then you will get all the time the ugly status code response 12501.

I think the main problem is that the documentation is a bit confusing about this. Or maybe because it is a bit strange the fact that you have to create two OAuth IDs.

So as a summary, you need TWO OAuth IDs, one for android and one for web application, and you have to set each one in the correct place.

blocks|key|126072|text|我遇到了同样的问题，这是因为我创建了应用程序类型为Android的客户端ID|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126073|​|126074|📷|atomic|offset|length|126075|126076|相反，我删除了它，并创建了web应用程序类型的客户端ID，我摆脱了这个问题。|126077|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/fba170326a35f6a2db48b50a84871a67.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

I was getting the same issue, it was because I created client ID of application type Android

<img src="https://i.stack.imgur.com/xF2FZ.png" alt="">

Instead, I deleted it and created client ID of type web application and I got rid of this issue.

blocks|key|2893730|text|我也遇到过同样的问题，在研究解决方案后，发现server_client_id包含了一些不正确的值，或者您的google_services.json没有包含注册到您的密钥库的oauth_client和client_id。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893731|requestIdToken(getString(R.string.server_client_id))|code-block|syntax|javascript|2893732|R.string.server_client_id将OAuth+2.0客户端ID用于网络应用程序。和安卓在google_services.json中使用的OAuth客户端ID|offset|length|style|CODE|BOLD|2893733|通常我们使用2个keystore，1个使用debug+keystore，1个使用签名keystore进行发布。因此，如果我们想在调试和发布模式下需要，为安卓注册两次OAuth客户端ID，一次使用调试密钥库中的SHA1，另一次使用签名密钥库中的发布。|2893734|我的google_services.json中的一个小示例|2893735|++"oauth_client":+[
++++{
++++++"client_id":+"xxx-client-id.com",
++++++"client_type":+1,
++++++"android_info":+{
++++++++"package_name":+"com.app.android",
++++++++"certificate_hash":+"xxxhash"
++++++}
++++},
++++{
++++++"client_id":+"yyy.client-id.com",
++++++"client_type":+1,
++++++"android_info":+{
++++++++"package_name":+"com.app.android",
++++++++"certificate_hash":+"yyyhash"
++++++}
++++}
++],|2893736|entityMap^0|0|0|0|P|16|6|1E|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|X|8|@$I|Y|J|Z|K|L]|$I|10|J|11|K|M]|$I|12|J|13|K|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|U|$]]

I had the same problem, after research solution it's resumed that server_client_id contained some incorrect value or your google_services.json didn't include oauth_client with client_id that registered with your keystore.

<pre><code>requestIdToken(getString(R.string.server_client_id))
</code></pre>

<code>R.string.server_client_id</code> use OAuth 2.0 client ID for Web Application. And OAuth Client ID for Android use in google_services.json

Usually we use 2 keystore, 1 using debug keystore and 1 using signed keystore for published. So if we want to need in debug &amp; publish mode, register your OAuth Client ID for Android twice, 1 using SHA1 from debug keystore and 1 from signed keystore for published.

small example in my google_services.json

<pre><code> "oauth_client": [
 {
 "client_id": "xxx-client-id.com",
 "client_type": 1,
 "android_info": {
 "package_name": "com.app.android",
 "certificate_hash": "xxxhash"
 }
 },
 {
 "client_id": "yyy.client-id.com",
 "client_type": 1,
 "android_info": {
 "package_name": "com.app.android",
 "certificate_hash": "yyyhash"
 }
 }
 ],
</code></pre>

blocks|key|2681964|text|如果以上选项都不起作用，请检查您在app+build.gradle中的applicationId是否与您的包名相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2681965|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If none of the above options work, do check whether you applicationId in app build.gradle is same as you package name.

blocks|key|2893803|text|在我的例子中，我还必须检查debug+SHA-1是否被添加为有效的OAuth+Android客户端。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893804|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, I also had to check that the debug SHA-1 was added as a valid OAuth Android client.

blocks|key|123629|text|现在我明白了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|123630|因此，首先你必须按照上面的答案说：|123631|123632|在谷歌开发者控制台中为web应用程序创建一个OAuth+client-id，并在requestIdToken()中使用它(去掉状态码12501)|ordered-list-item|offset|length|style|CODE|123633|如果你为你的生产散列键创建了一个Android+OAuth客户端id，那么为你的调试散列键创建一个新的Android+OAuth客户端id，并将它集成到你的google-services.json中。(摆脱状态代码12500)|123634|123635|不再是有效的，下面是最后一部分:+3.不能同时调用requestIdToken()和requestEmail()。至少在我的例子中，我通过删除requestEmail()摆脱了Result:+Status{statusCode=INTERNAL_ERROR,+resolution=null}。|BOLD|123636|所以祝你好运。|123637|entityMap^0|0|0|0|14|G|0|0|0|0|6|P|G|16|E|1Z|E|2G|1M|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|11|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|13|8|@$H|14|I|15|J|Q]|$H|16|I|17|J|K]|$H|18|I|19|J|K]|$H|1A|I|1B|J|K]|$H|1C|I|1D|J|K]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1E|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|U|$]]

Now I got it.

So first you must follow the upper answers saying:

<ol>
<li>create a OAuth client-id for web applications in the Google Developers Console and use it in <code>requestIdToken()</code>
(get rid of status code 12501)</li>
<li>if you created a Android OAuth client-id for your production hash key, create a new Android OAuth client-id for your debug hash key and integrate it into your google-services.json.
(get rid of status code 12500)</li>
</ol>

No longer valid
And here comes the last Part:
 3. you can not call <code>requestIdToken()</code> and <code>requestEmail()</code> at once. At least in my case I got rid of <code>Result: Status{statusCode=INTERNAL_ERROR, resolution=null}</code> by deleting <code>requestEmail()</code>.

So good luck...

blocks|key|2893983|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893984|遵循模棱两可的谷歌文档。|ordered-list-item|2893985|将google-services.json放到您的项目目录中，并将您的gradle设置为string.xml中的|2893986|+server_client_id。这是您的web客户端id，而不是android客户端|offset|length|style|BOLD|2893987|<代码>G212|2893988|entityMap^0|0|0|0|M|8|0|0^^$0|@$1|2|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|Q|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|R|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|S|7|@$H|T|I|U|J|K]]|8|@]|9|$]]|$1|L|3|M|4|5|6|V|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|W|7|@]|8|@]|9|$]]]|O|$]]

<ol>
<li>Follow the ambiguous google's document.</li>
<li>Put google-services.json to your project directory </li>
<li>Set your gradle as <a href="https://stackoverflow.com/a/35216421/5886475">https://stackoverflow.com/a/35216421/5886475</a></li>
<li>Set server_client_id in string.xml .It's your web client id not android client</li>
</ol>

blocks|key|123686|text|在遵循了谷歌关于Automatically+signing+your+app的说明后，我也遇到了这个问题。如果使用此方法对应用程序进行签名，则需要在API凭据中包含生成的密钥库指纹。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|123687|123688|在项目浏览器上，右键单击您的应用程序，然后选择打开模块设置。|blockquote|123689|123690|123691|​|123692|📷|atomic|123693|123694|我发现将.jks文件放在我的项目的/app目录中不那么容易混淆。在任何情况下都可以在上面运行这一行。|style|CODE|123695|keytool+-list+-v+-keystore+/home/user/keystores/android.jks|code-block|syntax|javascript|123696|系统将提示您输入密码。不确定是Key+Password还是Store+Password，因为我的是一样的。：|123697|控制台会吐出一堆证书指纹。获取SHA1+one并在Google+API+Developer's+Console处将其输入到您的API凭证中。你需要在安卓客户端OAuth+2.0+client+IDs中输入它，即使你在你的应用程序中并不实际使用该client_id。如果您使用的是其他适用于安卓的API，请在API+keys下的相应密钥凭证中也放入相同的SHA1。|123698|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/tools/publishing/app-signing.html#sign-auto|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/bba50ee0b354dccfb4ae05f7b9a042f5.png|imageAlt|2|https://console.developers.google.com/apis^0|8|U|0|0|0|0|0|0|0|0|1|1|0|0|4|4|H|4|0|0|F|C|T|E|0|27|K|49|8|P|U|2|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|D|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1N|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|L|3|M|5|N|7|1R|8|@]|9|@$A|1S|B|1T|1|1U]]|C|$]]|$1|O|3|K|5|6|7|1V|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1W|8|@$A|1X|B|1Y|R|S]|$A|1Z|B|20|R|S]]|9|@]|C|$]]|$1|T|3|U|5|V|7|21|8|@]|9|@]|C|$W|X]]|$1|Y|3|Z|5|6|7|22|8|@$A|23|B|24|R|S]|$A|25|B|26|R|S]]|9|@]|C|$]]|$1|10|3|11|5|6|7|27|8|@$A|28|B|29|R|S]|$A|2A|B|2B|R|S]]|9|@$A|2C|B|2D|1|2E]]|C|$]]|$1|12|3|-4|5|6|7|2F|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]|1A|$5|1B|16|1C|C|$1D|1E|1F|-4]]|1G|$5|15|16|17|C|$18|1H]]]]

I had this problem too, after following Google's instructions for <a href="http://developer.android.com/tools/publishing/app-signing.html#sign-auto" rel="nofollow noreferrer">Automatically signing your app</a>. If you are using this method to sign your apps, you will need to include the generated keystore fingerprint in your API credentials. 

<blockquote>
 On the project browser, right click on your app and select Open Module
 Settings.
</blockquote>

<a href="https://i.stack.imgur.com/EmLbf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/EmLbf.png" alt="Screenshot of Open Module Settings | app | signing | config "></a>

I found it less confusing to put the <code>.jks</code> file in my project's <code>/app</code> directory. In any case run this line on it. 

<pre><code>keytool -list -v -keystore /home/user/keystores/android.jks
</code></pre>

You will be prompted for a password. Not sure if it's the <code>Key Password</code> or <code>Store Password</code> because mine are the same. :|

The console will spit out a bunch of certificate fingerprints. Take the SHA1 one and punch it into your API credentials at the <a href="https://console.developers.google.com/apis" rel="nofollow noreferrer">Google API Developer's Console</a>. You will need to enter it for the Android client <code>OAuth 2.0 client IDs</code> even though you don't actually use that client_id in your app. If you are using other APIs for android, put the same SHA1 in the appropriate key credentials under <code>API keys</code> too.

blocks|key|126725|text|显然，首先要检查一下您的release+sha1密钥是否正确。但如果它仍然不能工作，并且您使用的是google+play服务8.4.0+(i.e.compile+'com.google.android.gms:play-services:8.4.0')，)，则可以通过修改GoogleSignInOption对象来解决此问题。而不是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126726|GoogleSignInOptions+gso+=+new+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
++++++++++++++++++++.requestEmail()++
+++++++.requestIdToken("YOUR_WEB_API_ID.apps.googleusercontent.com")
++++++++++++++++++++.build();|code-block|syntax|javascript|126727|你必须使用：|126728|GoogleSignInOptions+gso+=+new+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
++++++++++++++++.requestScopes(new+Scope(Scopes.PLUS_LOGIN))
++++++++++++++++.requestScopes(new+Scope(Scopes.PLUS_ME))
++++++++++++++++.requestEmail()
++++++++++++++++.build();|126729|这解决了返回statusCode=INTERNAL_ERROR或statusCode=Error+12501或statusCode=Error+12500的错误。然后这个gso对象可以用来创建GoogleApiClient，如下所示：|126730|+mGoogleApiClient+=+new+GoogleApiClient.Builder(this)
++++++++++++++++.enableAutoManage(this,+this)
++++++++++++++++.addApi(Auth.GOOGLE_SIGN_IN_API,gso)
+++++++++++++++//+.addApi(Plus.API,+null)
++++++++++++++++.addConnectionCallbacks(this)
++++++++++++++++.addOnConnectionFailedListener(this)
+++++++++++++++//+.addScope(Plus.SCOPE_PLUS_LOGIN)
++++++++++++++++.build();+|126731|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Oviously first check your release sha1 key is correct or not. But if still it is not working and you ar using google play services 8.4.0 (i.e.compile 'com.google.android.gms:play-services:8.4.0'), the issue could be solved by modifying GoogleSignInOption object.
Instead of:

<pre><code>GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestEmail() 
 .requestIdToken("YOUR_WEB_API_ID.apps.googleusercontent.com")
 .build();
</code></pre>

You have to use :

<pre><code>GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestScopes(new Scope(Scopes.PLUS_LOGIN))
 .requestScopes(new Scope(Scopes.PLUS_ME))
 .requestEmail()
 .build();
</code></pre>

This solves error returning statusCode=INTERNAL_ERROR OR statusCode=Error 12501 OR statusCode=Error 12500.
Then this gso object could be used for creating GoogleApiClient as shown below:

<pre><code> mGoogleApiClient = new GoogleApiClient.Builder(this)
 .enableAutoManage(this, this)
 .addApi(Auth.GOOGLE_SIGN_IN_API,gso)
 // .addApi(Plus.API, null)
 .addConnectionCallbacks(this)
 .addOnConnectionFailedListener(this)
 // .addScope(Plus.SCOPE_PLUS_LOGIN)
 .build(); 
</code></pre>

blocks|key|2682238|text|将网络应用程序用作server_client_id而不是安卓应用程序|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2682239|entityMap^0|1|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Use Web application as server_client_id not Android application

blocks|key|124885|text|我也遇到了同样的问题，我用以下解决方案解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124886|124887|按照说明创建配置文件(google-services.json)，并使用Web应用程序客户端ID+|ordered-list-item|124888|方法将其放入/app项目目录中(如其他答案中所述)。|124889|我的主要问题是，如果您在调试模式下工作，请签署您的应用程序，如下所示：|124890|<代码>G29|124891|124892|+signingConfigs+{+release+{+storeFile文件(“myreleasekey.keystore”)+storePassword+"password“keyAlias+"MyReleaseKey”keyPassword+"password“}}+buildTypes+{+release+{+...+}调试{+...signingConfig+signingConfigs.release+}+}|blockquote|124893|124894|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|X|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|Z|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I had the same problem, and I solved with the following solution:

<ol>
<li>Create configuration file (google-services.json) as described <a href="https://developers.google.com/identity/sign-in/android/start-integrating#get-config" rel="noreferrer">here</a> and place in your /app project directory</li>
<li>(As mentioned in other answers) Using Web application Client ID for <code>requestIdToken</code> method.</li>
<li>[My main problem] Sign your app if you work on debug mode like below:</li>
</ol>

<blockquote>
<pre><code> signingConfigs {
 release {
 storeFile file("myreleasekey.keystore")
 storePassword "password"
 keyAlias "MyReleaseKey"
 keyPassword "password"
 }
 }

 buildTypes {
 release {
 ...
 }
 debug {
 ...
 signingConfig signingConfigs.release
 }
 }
</code></pre>
</blockquote>

blocks|key|2682472|text|我在这件事上苦苦挣扎，几乎浪费了一个星期。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2682473|这就是我让它工作的方式。|offset|length|style|BOLD|2682474|AndroidStudio|2682475|Create调试密钥库中的project.|unordered-list-item|2682476|
|2682477|Create+keystore.|2682478|2682479|Using导入项目对于使用debug+Console.|2682480|2682481|Generate+Project.|2682482|2682483|Now，签名的项目，请在+Developer+Console.|2682484|Generate+a+Google配置文件中注册您的应用程序以进行SHA1登录。(放在安卓工作室的应用程序文件夹中)|ordered-list-item|2682485|在安卓Project.|2682486|Now，中使用来自|2682487|+2.0凭据的OAuth客户端ID，生成项目的调试版本(+APK+)。复制此签名的调试版本的APK并安装it.|2682488|，然后对系统中的设备进行|2682489|2682490|Mount。|2682491|2682492|最后三个步骤6、7和8，是您实际需要注意的。如果你直接运行项目，那么实际上并没有用调试密钥库签名，谷歌根本不会识别它。|2682493|entityMap^0|0|0|C|0|0|0|0|0|0|0|0|0|0|0|V|0|0|1M|0|0|B|0|0|9|0|0|1J|0|0|C|0|0|0|6|0|0|0|1N|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1M|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1N|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1O|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|1P|8|@]|9|@]|A|$]]|$1|Q|3|N|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|R|3|S|5|L|7|1R|8|@]|9|@]|A|$]]|$1|T|3|N|5|6|7|1S|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|1T|8|@]|9|@]|A|$]]|$1|W|3|N|5|6|7|1U|8|@]|9|@]|A|$]]|$1|X|3|Y|5|L|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|Z|3|10|5|11|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|12|3|13|5|11|7|21|8|@$D|22|E|23|F|G]]|9|@]|A|$]]|$1|14|3|15|5|11|7|24|8|@$D|25|E|26|F|G]]|9|@]|A|$]]|$1|16|3|17|5|11|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|18|3|19|5|6|7|2A|8|@$D|2B|E|2C|F|G]]|9|@]|A|$]]|$1|1A|3|N|5|6|7|2D|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|L|7|2E|8|@$D|2F|E|2G|F|G]]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2I|8|@$D|2J|E|2K|F|G]]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]]|1H|$]]

I was struggling with this and wasted almost a week in it. 

This is how I got it worked.

<ol>
<li>Import Project in AndroidStudio</li>
<li>Create debug keystore for project.</li>
<li>Create SHA1 signature for project using debug keystore.</li>
<li>Using SHA1 signature, register your app for Google Signin on Google Developer Console.</li>
<li>Generate a Google Configuration file there.(Put in Android Studio's app folder)</li>
<li>Use Web Client ID from OAuth 2.0 credentials in your Android Project.</li>
<li>Now, from Android Studio, generate debug build(APK) of your project. </li>
<li>Mount the device in your system -> copy this signed debug version of APK and install it.</li>
</ol>

Last three steps 6, 7 and 8, are what you actually need to take care of. If you directly run the project then APK is not actually signed with the debug keystore and google does not recognise it at all.

blocks|key|2894537|text|不知道为什么，android+studio中的SHA1会自动更改，这就是为什么我收到这个错误的原因。为了解决这个问题，我用我的android+studio的新SHA1更新了我的firebase项目设置的SHA1，它又开始工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2894538|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Don't know why but SHA1 in android studio is changed automatically and that's why I am getting this error. To solve this I updated the SHA1 of my firebase project settings with the new SHA1 of my android studio and it started working again.

blocks|key|125036|text|这是一个新的。我花了6个小时用我的公司Google+Apps域名中的id登录模拟器，但没有用，得到了12501个错误。凭直觉，我试了试我的个人gmail+id，它起作用了。如果我用我的公司id在我的手机上尝试，情况也是如此。事实证明，模拟器没有正确的移动设备管理设置来允许我的公司id登录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|125037|因此，如果我想使用此公司id在模拟器上进行测试，我必须安装Google+Play+Store，然后安装MDM软件，并对其进行配置。|125038|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Here is a new one. I was trying for 6 hours to login on the emulator with the id from my corporate Google Apps domain, to no avail, getting 12501 errors. On a hunch, I tried my personal gmail id and it worked. Ditto if I tried on my phone with my corporate id. It turns out the emulator did not have the proper Mobile Device Management settings to allow my corporate id to login. 

So If I want to test on the emulator with this corporate id, I have to install Google Play Store, then the MDM software, and configure it.

blocks|key|2894639|text|我遇到的一个问题是，我生成的SHA-1别名不正确。别名密钥必须是androiddebugkey。所以我把Android的OAuth+ID放在google-service.json文件中。我已经将网络客户端Id放入requestIdToken()。在我的特定示例中，我生成了带有androiddebugkey别名的SHA-1。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2894640|google-services.json|2894641|"oauth_client":+[
++++{
++++++"client_id":+"ANDROID+OAUTH+ID-.....apps.googleusercontent.com",
++++++"client_type":+1,
++++++"android_info":+{
++++++++"package_name":+"br.com.packagename",
++++++++"certificate_hash":+"SHA-1+HASH"
++++++}
++++},{
++++++"client_id":+"WEB+CLIEND+ID......apps.googleusercontent.com",
++++++"client_type":+3
++++}
+]|code-block|syntax|javascript|2894642|签名部分：|2894643|GoogleSignInOptions+gso+=+new+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
++++++++++++++++.requestIdToken("WEB+CLIEND+ID......apps.googleusercontent.com")
++++++++++++++++.requestEmail()+
++++++++++++++++.build();+|2894644|entityMap^0|3U|F|0|0|K|0|0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

A problem I had is that the SHA-1 I generated as with the incorrect alias.
The alias MUST BE androiddebugkey .
So I have put the Android OAuth ID at my google-service.json file. I have put the Web Client Id to requestIdToken().
And in my specific case, I generated the SHA-1 with androiddebugkey alias.

google-services.json:

<pre><code>"oauth_client": [
 {
 "client_id": "ANDROID OAUTH ID-.....apps.googleusercontent.com",
 "client_type": 1,
 "android_info": {
 "package_name": "br.com.packagename",
 "certificate_hash": "SHA-1 HASH"
 }
 },{
 "client_id": "WEB CLIEND ID......apps.googleusercontent.com",
 "client_type": 3
 }
 ]
</code></pre>

Signing part:

<pre><code>GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestIdToken("WEB CLIEND ID......apps.googleusercontent.com")
 .requestEmail() 
 .build(); 
</code></pre>

blocks|key|126598|text|在我的例子中，我在Google+APIs+Console上的Client+ID+for+Android凭据只包含我的发行版签名的APK的SHA-1。Android+Studio使用默认的调试密钥库来签署我的调试版本，在这种情况下，调试密钥库SHA-1与在线Android客户端SHA-1不匹配。我的解决方案是简单地使用发布密钥库对调试构建进行签名。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|126599|在Android+Studio中，Build/Edit+Build+Types...，然后选择您的调试构建类型，并确保签名配置设置为您的发布证书。|126600|​|126601|📷|atomic|126602|126603|entityMap|0|LINK|mutability|MUTABLE|url|http://console.developers.google.com/|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/fae2589698d7bbc172514ee681cc3ccb.png|imageAlt^0|U|L|9|J|0|0|H|P|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|M|3|I|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|W|R|X|E|$Y|Z|10|-4]]]]

In my case, my Credentials for <code>Client ID for Android</code> on <a href="http://console.developers.google.com" rel="nofollow noreferrer">Google APIs Console</a> only contained the SHA-1 for my release signed APK. Android Studio was using the default debug keystore to sign my debug builds, and in that case the debug keystore SHA-1 did not match the Android client SHA-1 online. My solution was to simply sign the debug builds with the release keystore.

In Android Studio, <code>Build/Edit Build Types...</code>, then select your debug build type and make sure Signing Config is set to your release certificate.

<a href="https://i.stack.imgur.com/bcpBs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/bcpBs.png" alt="Signing Config set to release"></a>

blocks|key|125144|text|只需使用R.string.default_web_client_id代替R.string.server_client_id即可。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|125145|当您将google-services.json文件复制到应用程序中时，它会自动创建此字符串值。您不需要将密钥从google-services.json复制到string.xml，它对我有效。|BOLD|125146|entityMap^0|4|U|10|P|0|3|K|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|J|$]]

In place of <code>R.string.server_client_id</code> , just use <code>R.string.default_web_client_id</code> .

When you copy the google-services.json file into the app, it creates this string value automatically. You don't need to copy the key from google-services.json to string.xml
It worked for me.

blocks|key|127042|text|从我与这个错误的奇怪经验，我可以说，您还需要尝试重新启动您的手机，以摆脱这个错误:)我是实现谷歌登录使用G套件帐户，其中有一个通过谷歌管理分配的设备策略。所以在第一次登录时，它需要安装设备策略应用程序。在所有后续步骤完成后，它只是抛出了12501错误。同一时间，同一个应用程序在其他手机上运行良好。所以只有重启才有帮助。但也有帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|data|127043|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

From my weird experience with this error, I can say that you also need to try to reboot your phone in order to get rid of this error :)
I was implemented Google Sign In using G Suite accounts which have a device policy assigned via Google Admin. So on the first sign in it was requiring to install Device Policy app. After all later steps completed, it was just throwing 12501 error. Same time the same app was working fine on other phones. So only reboot helped. But helped

blocks|key|127050|text|虽然这个问题已经有很多正面的答案，但我还是很难理解其中的逻辑。所以，我提出了我的研究。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|127051|使用正确的证书包名称创建应用程序&签名证书指纹https://developers.google.com/mobile/add?platform=android&cntapi=signin|offset|length|127052|Enable+SHA-1+sign-in|unordered-list-item|127053|
|127054|Generate+|127055|配置文件。|style|BOLD|127056|127057|127058|要获取SHA-1，请在终端中运行以下命令：|127059|keytool+-exportcert+-keystore+path-to-debug-or-production-keystore+-list+-v|code-block|syntax|javascript|127060|关于OAuth+2.0+client+IDs|CODE|127061|适用于web的签名证书指纹(在应用程序中用作server_client_id)|127062|OAuth+for+android+(需要使用正确的包名称和签名证书指纹SHA-1).|127063|
创建|127064|如果您使用不同的密钥库进行调试和发布，则需要使用各自的包名&+|127065|+-1创建单独的OAuth+2.0+client+IDs。|blockquote|127066|127067|127068|您可以在此处https://console.developers.google.com/apis/credentials?project=创建或编辑OAuth+2.0+client+IDs|127069|127070|导航到您的应用程序。|ordered-list-item|127071|如果您已经有安卓版OAuth，请单击其名称并检查包名称&SHA-1。|127072|127073|我们可以使用相同的密钥库进行调试和发布，方法是将密钥库的详细信息保存在全局(本地，而不是项目内部)+gradle.properties中，并将其保存在build.gradle中，如下所示。|127074|def+key_alias+=+""
def+key_password+=+""
def+store_file+=+""
def+store_password+=+""

try+{
++++key_alias+=+YOUR_KEY_ALIAS
++++key_password+=+YOUR_KEY_PASSWORD
++++store_file+=+YOUR_KEYSTORE_PATH
++++store_password+=+YOUR_KEYSTORE_PASSWORD
}+catch+(Exception+exception)+{
++++throw+new+IllegalStateException('Failed+to+find+key+store+details.+Social+Login+is+disabled');
}

android+{
++++signingConfigs+{
++++++++config+{
++++++++++++keyAlias+key_alias
++++++++++++keyPassword+key_password
++++++++++++storeFile+file(store_file)
++++++++++++storePassword+store_password
++++++++}
++++}

++++buildTypes+{
++++++++debug+{
++++++++++++signingConfig+signingConfigs.config
++++++++++++//+...
++++++++}
++++++++release+{
++++++++++++signingConfig+signingConfigs.config
++++++++++++//+...
++++++++}
++++}
}|127075|您可以使用下面的代码片段|127076|@Override
protected+void+onActivityResult(int+requestCode,+int+resultCode,+Intent+data)+{
++++super.onActivityResult(requestCode,+resultCode,+data);
++++if+(requestCode+==+REQUEST_CODE_GOOGLE_SIGN_IN)+{
++++++++GoogleSignInResult+result+=+Auth.GoogleSignInApi.getSignInResultFromIntent(data);
++++++++if+(result.isSuccess())+{
++++++++++++//+...
++++++++}+else+if+(result.getStatus().getStatusCode()+==+CommonStatusCodes.NETWORK_ERROR)+{
++++++++++++//+No+internet+connection
++++++++}+else+if+(result.getStatus().getStatusCode()+==+CommonStatusCodes.DEVELOPER_ERROR)+{
++++++++++++//+Wrong+server+OAuth+key(server_client_id)
++++++++}+else+if+(result.getStatus().getStatusCode()+==+12501)+{
++++++++++++//+Wrong+app+signing-certificate+fingerprint+SHA1
++++++++}+else+{
++++++++++++Log.e("Google+sign+in+error",+result.getStatus().toString());
++++++++}
++++}
}|127077|127078|注意:如果在生成配置文件时只启用了谷歌登录，则不需要在项目中添加google-servies.json文件。(生成该文件将执行必要的配置步骤)。|127079|127080|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/mobile/add?platform=android&cntapi=signin|1|https://console.developers.google.com/apis/credentials?project=^0|0|N|1Z|0|0|0|0|0|0|5|0|0|0|0|L|0|0|0|M|2|K|0|0|13|M|G|0|0|17|0|1|2|0|0|V|0|0|T|8|K|0|0|0|0|2M|22|K|6|1R|1|0|0|0|A|0|0|Y|0|0|0|2M|1E|H|23|C|0|0|0|C|0|0|0|0|20|W|J|0|0^^$0|@$1|2|3|4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2B|8|@]|9|@$D|2C|E|2D|1|2E]]|A|$]]|$1|F|3|G|5|H|7|2F|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|2G|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|2H|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|2I|8|@$D|2J|E|2K|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2N|8|@$D|2O|E|2P|O|P]]|9|@]|A|$]]|$1|U|3|V|5|W|7|2Q|8|@]|9|@]|A|$X|Y]]|$1|Z|3|10|5|6|7|2R|8|@$D|2S|E|2T|O|P]|$D|2U|E|2V|O|11]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2W|8|@$D|2X|E|2Y|O|P]|$D|2Z|E|30|O|11]]|9|@]|A|$]]|$1|14|3|15|5|H|7|31|8|@$D|32|E|33|O|P]]|9|@]|A|$]]|$1|16|3|17|5|6|7|34|8|@$D|35|E|36|O|P]]|9|@]|A|$]]|$1|18|3|19|5|6|7|37|8|@$D|38|E|39|O|P]]|9|@]|A|$]]|$1|1A|3|1B|5|1C|7|3A|8|@$D|3B|E|3C|O|P]|$D|3D|E|3E|O|11]]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3H|8|@$D|3I|E|3J|O|P]|$D|3K|E|3L|O|11]]|9|@$D|3M|E|3N|1|3O]]|A|$]]|$1|1H|3|-4|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|1K|7|3Q|8|@$D|3R|E|3S|O|P]]|9|@]|A|$]]|$1|1L|3|1M|5|1K|7|3T|8|@$D|3U|E|3V|O|P]]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|3W|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3X|8|@$D|3Y|E|3Z|O|P]|$D|40|E|41|O|11]|$D|42|E|43|O|11]]|9|@]|A|$]]|$1|1Q|3|1R|5|W|7|44|8|@]|9|@]|A|$X|Y]]|$1|1S|3|1T|5|6|7|45|8|@$D|46|E|47|O|P]]|9|@]|A|$]]|$1|1U|3|1V|5|W|7|48|8|@]|9|@]|A|$X|Y]]|$1|1W|3|-4|5|6|7|49|8|@]|9|@]|A|$]]|$1|1X|3|1Y|5|1C|7|4A|8|@$D|4B|E|4C|O|P]|$D|4D|E|4E|O|11]]|9|@]|A|$]]|$1|1Z|3|-4|5|6|7|4F|8|@]|9|@]|A|$]]|$1|20|3|-4|5|6|7|4G|8|@]|9|@]|A|$]]]|21|$22|$5|23|24|25|A|$26|27]]|28|$5|23|24|25|A|$26|29]]]]

Though already many upvoted answers exist in this question, I struggled to understand the logic.
So, I come up with my research.

<ul>
<li>Create a app using correct package name &amp; Signing-certificate fingerprint SHA-1 <a href="https://developers.google.com/mobile/add?platform=android&amp;cntapi=signin" rel="nofollow noreferrer">https://developers.google.com/mobile/add?platform=android&amp;cntapi=signin</a></li>
<li>Enable google sign-in</li>
<li>Generate the configuration file.</li>
</ul>

To get SHA-1, run this in terminal:

<pre><code>keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
</code></pre>

About <code>OAuth 2.0 client IDs</code> 

<ul>
<li>OAuth for the web (In app this is used as <code>server_client_id</code>)</li>
<li>OAuth for android (This needs to be created using correct package name &amp; Signing-certificate fingerprint SHA-1).</li>
</ul>

<blockquote>
 If you are using the different keystore for debug &amp; release, you need to create separate <code>OAuth 2.0 client IDs</code> using respective package name &amp; SHA-1.
</blockquote>

You can create or edit your <code>OAuth 2.0 client IDs</code> here <a href="https://console.developers.google.com/apis/credentials?project=" rel="nofollow noreferrer">https://console.developers.google.com/apis/credentials?project=</a>

<ol>
<li>Navigating to your app.</li>
<li>If you already have a OAuth for Android, click in its name &amp; check the package name &amp; SHA-1.</li>
</ol>

We can use the same keystore for both debug &amp; release by saving the keystore details in global(local, not inside project) <code>gradle.properties</code> &amp; getting it in <code>build.gradle</code> as below.

<pre><code>def key_alias = ""
def key_password = ""
def store_file = ""
def store_password = ""

try {
 key_alias = YOUR_KEY_ALIAS
 key_password = YOUR_KEY_PASSWORD
 store_file = YOUR_KEYSTORE_PATH
 store_password = YOUR_KEYSTORE_PASSWORD
} catch (Exception exception) {
 throw new IllegalStateException('Failed to find key store details. Social Login is disabled');
}

android {
 signingConfigs {
 config {
 keyAlias key_alias
 keyPassword key_password
 storeFile file(store_file)
 storePassword store_password
 }
 }

 buildTypes {
 debug {
 signingConfig signingConfigs.config
 // ...
 }
 release {
 signingConfig signingConfigs.config
 // ...
 }
 }
}
</code></pre>

You can use below snippet

<pre><code>@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
 super.onActivityResult(requestCode, resultCode, data);
 if (requestCode == REQUEST_CODE_GOOGLE_SIGN_IN) {
 GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);
 if (result.isSuccess()) {
 // ...
 } else if (result.getStatus().getStatusCode() == CommonStatusCodes.NETWORK_ERROR) {
 // No internet connection
 } else if (result.getStatus().getStatusCode() == CommonStatusCodes.DEVELOPER_ERROR) {
 // Wrong server OAuth key(server_client_id)
 } else if (result.getStatus().getStatusCode() == 12501) {
 // Wrong app signing-certificate fingerprint SHA1
 } else {
 Log.e("Google sign in error", result.getStatus().toString());
 }
 }
}
</code></pre>

<blockquote>
 Note: If you enabled only Google Sign-In when you generated the configuration file, you need not to add the <code>google-servies.json</code> file in your project.(generating the file performs the necessary configuration steps).
</blockquote>

blocks|key|2894883|text|我有相同的问题和错误12501，上面的都不适用于我。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2894884|我的问题是，我使用的是为我生成的google默认web+api。在创建了我自己的web+api之后，错误消失了，并且工作正常！|2894885|以下是工作步骤：|2894886|2894887|首先我创建了SHA1调试密钥并添加到Firebase控制台。从here.|ordered-list-item|2894888|create创建SHA1从here|2894889|get创建web+api和安卓OAuth+2.0客户端ID从Firebase控制台生成google-service.json并将其放入应用程序文件夹中。GoogleSignnOption|CODE|2894890|的|2894891|放了这段代码|unordered-list-item|2894892|2894893|如下所示：|2894894|gso+=+new+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN).requestIdToken
++++++++++++++++("put+the+web+app+client+Id+that+get+from+the+link+in+developer+console+")
++++++++++++++++.requestEmail().build();|code-block|syntax|javascript|2894895|提示1:我发现你应该同时创建android和web应用程序客户端Id才能工作。|2894896|提示2:如果你来自伊朗，像我一样，你可以从谷歌获得用户，但你不能AuthWithGoogle和结果将fail在auth.signInWithCredential(credential)中，你必须使用一些代理返回真。|2894897|这是github中FireBaseAuthDemo的完整工作源码：|2894898|​|2894899|📷|atomic|2894900|2894901|希望能帮上大忙|2894902|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/android/guides/client-auth|1|https://console.developers.google.com/projectselector/apis/credentials|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1838e0fa91662fcc3621c77b0f20782f.png|imageAlt^0|A|5|0|0|0|0|I|8|V|4|0|0|D|4|1|0|U|8|17|J|24|H|0|0|0|0|0|0|0|4|0|0|4|W|E|1E|4|1J|11|0|0|0|0|1|2|0|0|0^^$0|@$1|2|3|4|5|6|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|22|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|23|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|24|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|25|8|@$9|26|A|27|B|C]]|D|@$9|28|A|29|1|2A]]|E|$]]|$1|N|3|O|5|M|7|2B|8|@]|D|@$9|2C|A|2D|1|2E]]|E|$]]|$1|P|3|Q|5|M|7|2F|8|@$9|2G|A|2H|B|C]|$9|2I|A|2J|B|R]|$9|2K|A|2L|B|R]]|D|@]|E|$]]|$1|S|3|T|5|6|7|2M|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|2N|8|@]|D|@]|E|$]]|$1|X|3|-4|5|6|7|2O|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2P|8|@]|D|@]|E|$]]|$1|10|3|11|5|12|7|2Q|8|@]|D|@]|E|$13|14]]|$1|15|3|16|5|6|7|2R|8|@$9|2S|A|2T|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|2U|8|@$9|2V|A|2W|B|C]|$9|2X|A|2Y|B|R]|$9|2Z|A|30|B|R]|$9|31|A|32|B|R]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|33|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|6|7|34|8|@]|D|@]|E|$]]|$1|1D|3|1E|5|1F|7|35|8|@]|D|@$9|36|A|37|1|38]]|E|$]]|$1|1G|3|1C|5|6|7|39|8|@]|D|@]|E|$]]|$1|1H|3|1I|5|6|7|3A|8|@]|D|@]|E|$]]|$1|1J|3|-4|5|6|7|3B|8|@]|D|@]|E|$]]]|1K|$1L|$5|1M|1N|1O|E|$1P|1Q]]|1R|$5|1M|1N|1O|E|$1P|1S]]|1T|$5|1U|1N|1V|E|$1W|1X|1Y|-4]]]]

I had the same problem and error 12501 and non of of above did work for me.

My problem was I using google Default web api that generated for me. after creating my own web api error disappeared and worked fine!

these are working steps:

<ol>
<li>first I created SHA1 debug key and add to Firebase console. creating SHA1 from <a href="https://developers.google.com/android/guides/client-auth" rel="nofollow noreferrer">here</a>.</li>
<li>create both web api and android OAuth 2.0 client ID from <a href="https://console.developers.google.com/projectselector/apis/credentials" rel="nofollow noreferrer">here</a></li>
<li>get generated <code>google-service.json</code> from Firebase console and put in app folder. </li>
<li>put this code for <code>GoogleSignnOption</code></li>
</ol>

like this:

<pre><code>gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN).requestIdToken
 ("put the web app client Id that get from the link in developer console ")
 .requestEmail().build();
</code></pre>

tip 1: I find out that you should create both android and web app Client Id to work.

tip 2: if you from Iran like me you can get the user from google but you can not <code>AuthWithGoogle</code> and result will <code>fail</code> in <code>auth.signInWithCredential(credential)</code> and you had to use some proxy for returning true.

this is the working full source of FireBaseAuthDemo in github: 

<a href="https://github.com/mahdit83/FireBaseAuthDemo" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VG0SK.png" alt="enter image description here"></a>

hope help full

blocks|key|2683070|text|尝试执行以下步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2683071|在https://developers.google.com/identity/sign-in/android/start|offset|length|2683072|Use++client+(由|unordered-list-item|2683073|服务自动创建)上克隆以下项目并将其添加到requestIdToken(...)|ordered-list-item|2683074|2683075|2683076|Google+gso+=+GoogleSignInOptions+GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)+.requestEmail()+.requestIdToken("YOUR_WEB_API_ID.apps.googleusercontent.com")+.build()；|2683077|确保您使用的密钥库与添加到谷歌项目中的密钥库相同。例如，如果您使用以下命令生成SHA-1密钥|2683078|2683079|keytool+-exportcert+-list+-v+-alias+android+debug.keystore+-keystore+~/.android/debug.keystore+|2683080|然后在安卓内部的应用/build.gradle文件中添加以下代码{+...+}解决了我的问题|2683081|2683082|signingConfigs+{+debug+{+storeFile文件(“/home/ashwin/.android/debug.keystore”)+storePassword+"android“keyAlias+"androiddebugkey”keyPassword+"android“}+buildTypes+{+release+{+minifyEnabled+false+proguardFiles+proguard+RULE.PRO‘}+debug+{+signingConfig+signingConfigs.debug+}+}|2683083|注意:您的keyPassword和keyAlias必须与生成SHA-1证书时使用的相同。|2683084|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/identity/sign-in/android/start^0|0|1|1O|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@$D|1B|E|1C|1|1D]]|A|$]]|$1|F|3|G|5|H|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1F|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1I|8|@]|9|@]|A|$]]|$1|P|3|Q|5|H|7|1J|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1L|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|1M|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1P|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]]]

Try following these steps:

<ol>
<li>Clone the following project <a href="https://github.com/googlesamples/google-services" rel="nofollow noreferrer">https://github.com/googlesamples/google-services</a></li>
<li>Follow the guide at <a href="https://developers.google.com/identity/sign-in/android/start" rel="nofollow noreferrer">https://developers.google.com/identity/sign-in/android/start</a></li>
<li>Use Web client (auto created by Google Service) and add it in requestIdToken(...)

<pre><code>GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestEmail() 
 .requestIdToken("YOUR_WEB_API_ID.apps.googleusercontent.com")
 .build();
</code></pre></li>
<li>Make sure you are using the same keystore used which is added to Google project. For instance, if you have used the following command to generate SHA-1 key

<pre><code>keytool -exportcert -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore 
</code></pre></li>
<li>Then add the following code in app/build.gradle file inside android { ... } [Solved my problem]

<pre><code>signingConfigs
{
 debug 
 {
 storeFile file("/home/ashwin/.android/debug.keystore")
 storePassword "android"
 keyAlias "androiddebugkey"
 keyPassword "android"
 }
}

buildTypes
{
 release
 {
 minifyEnabled false
 proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
 }
 debug
 {
 signingConfig signingConfigs.debug
 }
}
</code></pre></li>
</ol>

Note: Your keyPassword and keyAlias should be the same used during generation of SHA-1 certificate.

blocks|key|2894967|text|我通过在Android+Studio中单击Firebase支持解决了这个问题，这可能与非Firebase用户无关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2894968|Firebase身份验证转到菜单Tools->Firebase|2894969|Click将您的应用程序连接到Firebase，它将显示为已连接绿色一旦connection+is+successful|unordered-list-item|2894970|
|2894971|Click将|2894972|添加到您的应用程序按钮，它也将变为绿色。|ordered-list-item|2894973|2894974|2894975|注意:在这篇文章中有一大堆答案肯定会证实一件事。谷歌需要更新和保持文档的愚蠢证明。|2894976|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|Y|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

I solved this issue by Clicking Firebase Support in Android Studio, which may not be relevant to non-Firebase users.

<ol>
<li>Go to menu Tools->Firebase</li>
<li>Click Connect your app to Firebase, it will display as Connected in green once connection is successful</li>
<li>Click Add Firebase Authentication to your app button, it will also turn green.</li>
</ol>

NOTE: Having huge list of answers in this definitely confirm one thing. Google needs to update and keep the documentation fool proof.

blocks|key|126682|text|gradle+1.在文件中指定signingConfigs|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|126683|signingConfigs+{
++++++++config+{
++++++++++++keyAlias+'appalias'
++++++++++++keyPassword+'hunter123'
++++++++++++storePassword+'hunter123'
++++++++++++storeFile+file('path/to/keystore.jks')
++++++++}
}|code-block|syntax|javascript|126684|配置2.在项目结构中构建类型(在Android+Studio中)，并将signingConfigs指定为“”|126685|现在清理你的项目，然后重新构建。应该能行得通。|126686|如果上面的方法不起作用，那么下面就是你最后的选择。|126687|尝试第一步并进行构建和检查。如果它不工作，请转到下一步并尝试重新构建。|126688|126689|构建一个签名的apk+(选中了记住密码)。|ordered-list-item|126690|在签名之前，请检查keystore文件的文件名和您在签署apk时输入的文件名(在android+studio中)。|126691|在您的设备上安装签名的apk。|126692|等待五分钟。|126693|试着唱给谷歌听。如果还有12501要来，再等5分钟。在做这个的时候点击了gradle+sync。|126694|重试。它应该可以工作。|126695|126696|entityMap^0|A|2|0|0|1H|1|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1G|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1H|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1I|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]|$1|T|3|U|5|V|7|1K|8|@]|D|@]|E|$]]|$1|W|3|X|5|V|7|1L|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|V|7|1M|8|@]|D|@]|E|$]]|$1|10|3|11|5|V|7|1N|8|@]|D|@]|E|$]]|$1|12|3|13|5|V|7|1O|8|@]|D|@]|E|$]]|$1|14|3|15|5|V|7|1P|8|@]|D|@]|E|$]]|$1|16|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|17|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|18|$]]

1.Specify signingConfigs in your gradle file

<pre><code>signingConfigs {
 config {
 keyAlias 'appalias'
 keyPassword 'hunter123'
 storePassword 'hunter123'
 storeFile file('path/to/keystore.jks')
 }
}
</code></pre>

2.Go to Build Types in Project Structure (in Android Studio) and specify signingConfigs to "config"

Now clean your project and build again. It should work.

If the above doesn't work then below is your last resort. 
Try step one and build and check. If it's not working go to next step and try to build again. 

<ol>
<li>Build a signed apk (With remember password checked). </li>
<li>Before signing check the filename of the keystore file and the one yo give in while signing the apk (in android studio). </li>
<li>Install the signed apk in your device. </li>
<li>Wait for five minutes. </li>
<li>Try singing in to google. If still 12501 is coming wait five more minutes. While doing that hit gradle sync. </li>
<li>Try again. It should work.</li>
</ol>

blocks|key|2895026|text|由于应用程序从web视图请求Google登录，我们需要创建web应用程序auth+client+id+v2.0。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2895027|2895028|转到Google+API+Credentials|ordered-list-item|offset|length|2895029|2895030|从左上角选择您的Android项目|2895031|2|2895032|Click+on+Create+Credentials+-->+Firebase+Client+Id+-->选择Web+Application|unordered-list-item|2895033|
|2895034|Click+Ok+google-services.json+OAuth+Now，如果您已经与Firebase同步(已登录)，只需重建项目，否则下载更新的|style|BOLD|2895035|
文件并替换现有文件。|2895036|它应该可以正常工作。|2895037|entityMap|0|LINK|mutability|MUTABLE|url|https://console.developers.google.com/apis/credentials|1|https://i.stack.imgur.com/P3s7j.png^0|0|0|2|M|0|0|0|0|0|1|1|0|0|0|9|K|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1B|8|@]|9|@$F|1C|G|1D|1|1E]]|A|$]]|$1|H|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1G|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1H|8|@]|9|@$F|1I|G|1J|1|1K]]|A|$]]|$1|M|3|N|5|O|7|1L|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1M|8|@]|9|@]|A|$]]|$1|R|3|S|5|O|7|1N|8|@$F|1O|G|1P|T|U]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]|17|$5|12|13|14|A|$15|18]]]]

Since the app requests Google sign in from web view we need to create web application auth client id v2.0

<ol>
<li>Go to <a href="https://console.developers.google.com/apis/credentials" rel="nofollow noreferrer" title="Google API Credentials">Google API Credentials</a>

Choose your Android project from Top Left corner

<a href="https://i.stack.imgur.com/P3s7j.png" rel="nofollow noreferrer">2</a></li>
<li>Click on Create Credentials --> OAuth Client Id --> Choose Web
Application</li>
<li>Click Ok</li>
<li>Now , if you have synced Android Studio with Firebase (logged in)
just rebuild the project Otherwise Download updated
google-services.json file and replace the existing one.

It should work fine.</li>
</ol>

blocks|key|126712|text|我也有同样的问题，解决方法如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126713|126714|blockquote|126715|126716|126717|I被要求删除之前认为的SHA1并创建并设置新的SHA1。|ordered-list-item|126718|生成新的google-services.json并将其设置到我的应用程序目录中|offset|length|style|CODE|126719|I正在使用google+developer+codes|126720|my在运行项目|126721|<代码>G214后返回true|126722|作为摘要，删除旧的sha1并创建新的sha1并下载新的google-services.json|BOLD|126723|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/identity/sign-in/android/start-integrating^0|0|0|0|0|0|0|4|K|0|5|M|0|0|0|0|0|1B|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|-4|5|D|7|18|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|1C|8|@$L|1D|M|1E|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|I|7|1F|8|@]|9|@$L|1G|M|1H|1|1I]]|A|$]]|$1|R|3|S|5|I|7|1J|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1K|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1L|8|@$L|1M|M|1N|N|X]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

I have same problem too, Was resolved as follows:

<blockquote>
 <ol>
 <li>I was made to delete the SHA1 previously thought and create and set new SHA1.</li>
 <li>generate new <code>google-services.json</code> and set into my app directory</li>
 <li>I was use exactly <a href="https://developers.google.com/identity/sign-in/android/start-integrating" rel="nofollow noreferrer">google developer codes</a></li>
 <li>my <code>result.isSucces()</code> returned true after running the project</li>
 </ol>
</blockquote>

as summary, delete old sha1 and create new sha1 and download new google-services.json

blocks|key|126730|text|如果您使用调试密钥库来构建项目，则需要在Firebase控制台上添加debug.keystore的SHA-1指纹。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|126731|126732|在您的Firebase控制台上，打开您的项目|ordered-list-item|126733|转到参数。选项卡在此页的末尾，控制台字段中有一个用于添加指纹SHA-1|126734|Paste+General|126735|At+SHA-1的字段。|126736|126737|获取debug.keystore的SHA-1：|126738|Mac/Linux+:|126739|keytool+-exportcert+-list+-v+-alias+androiddebugkey+-keystore+~/.android/debug.keystore|code-block|syntax|javascript|126740|窗口:|126741|+keytool+-exportcert+-list+-v+-alias+androiddebugkey+-keystore+%25USERPROFILE%25\.android\debug.keystore|126742|https://developers.google.com/android/guides/client-auth|126743|这就是全部！|126744|entityMap|0|LINK|mutability|MUTABLE|url^0|5|5|K|B|Y|E|0|0|3|B|0|S|7|0|6|7|0|0|0|0|0|B|0|0|0|3|0|0|0|1K|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|J|3|K|5|I|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|L|3|M|5|I|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|N|3|O|5|I|7|1V|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1X|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1Y|8|@$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|U|3|V|5|W|7|21|8|@]|D|@]|E|$X|Y]]|$1|Z|3|10|5|6|7|22|8|@$9|23|A|24|B|C]]|D|@]|E|$]]|$1|11|3|12|5|W|7|25|8|@]|D|@]|E|$X|Y]]|$1|13|3|14|5|6|7|26|8|@]|D|@$9|27|A|28|1|29]]|E|$]]|$1|15|3|16|5|6|7|2A|8|@]|D|@]|E|$]]|$1|17|3|-4|5|6|7|2B|8|@]|D|@]|E|$]]]|18|$19|$5|1A|1B|1C|E|$1D|14]]]]

If you are using the debug keystore to build the project, you need to add the SHA-1 fingerprint of debug.keystore on Firebase Console.

<ol>
<li>On your Firebase Console, open your Project</li>
<li>Go to Parameters. Tab General</li>
<li>At the end of this page, there is a field to add a Fingerprint SHA-1</li>
<li>Paste the SHA-1 in the console field.</li>
</ol>

To obtain SHA-1 of debug.keystore :

Mac/Linux : 

<pre><code>keytool -exportcert -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore
</code></pre>

Windows : 

<pre><code> keytool -exportcert -list -v -alias androiddebugkey -keystore %USERPROFILE%\.android\debug.keystore
</code></pre>

<a href="https://developers.google.com/android/guides/client-auth" rel="nofollow noreferrer">https://developers.google.com/android/guides/client-auth</a>

That's all !

blocks|key|125269|text|我也面临着同样的12501+status错误。这是由于版本APK和调试APK的SHA-1不匹配造成的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|125270|125271|生成签名的APK。要对APK进行签名，请选择用于创建SHA-1的密钥库的现有路径。例如：/.android/debug.keystore|ordered-list-item|125272|Give别名:+androiddebugkey|125273|storepass，密钥密码:android。|125274|125275|entityMap^0|8|C|0|0|18|O|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|J|3|K|5|I|7|X|8|@]|D|@]|E|$]]|$1|L|3|M|5|I|7|Y|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

I was facing the same <code>12501 status</code> error. This is due to SHA-1 mismatch of release APK and debug APK.

<ol>
<li>Make a signed APK. To sign an APK, choose existing path of the keystore you have used for creating SHA-1. e.g. <code>/.android/debug.keystore</code></li>
<li>Give alias-name : androiddebugkey</li>
<li>storepass and keypass : android.</li>
</ol>

blocks|key|2895197|text|我也有同样的问题。当我第一次创建google-services.json并将firebase添加到项目中时，我可能没有正确地遵循这些步骤，即使尝试了这里描述的所有步骤，我也无法解决这个问题。我最终按照here的描述从android+studio内连接到了firebase。我经历了前两个步骤，并再次编译，代码终于可以工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2895198|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/studio/write/firebase.html^0|2S|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had the same problem. I probably didn't follow the steps properly when I first created the google-services.json and added firebase to project, and even after trying all the steps described here I couldn't fix the problem.
I finally managed by connecting to firebase from within android studio as described <a href="https://developer.android.com/studio/write/firebase.html" rel="nofollow noreferrer">here</a>. I went through the first two steps and compiled again, the code finally worked.

blocks|key|125284|text|我已经开发了库来添加谷歌SignIn选项在您的应用程序中，只需几行代码。试试HiGoogle-+Google+SignIn+Made+Easy|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|125285|使用网络应用程序作为server_client_id，而不是安卓应用程序。在HiGoogle构造函数中传递它。|style|BOLD|125286|entityMap|0|LINK|mutability|MUTABLE|url|https://shivam301296.github.io/HiGoogle/^0|12|X|0|0|2|6|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

I have developed lib to Add Google SignIn option in your app with just few lines of code. Try <a href="https://shivam301296.github.io/HiGoogle/" rel="nofollow noreferrer">HiGoogle- Google SignIn Made Easy</a>

Use Web application as server_client_id not Android application. Pass it in the HiGoogle constructor.

I'm trying to get a user token ID using the new Google play services 8.3
and as documented I pass the server ID:
<pre><code>GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
 .requestIdToken(getString(R.string.server_client_id))
 .requestEmail()
 .build();
</code></pre>
but I'm still getting un successful result as below:
<pre><code>{statusCode=unknown status code: 12501, resolution=null}
</code></pre>
and documented here <a href="https://developers.google.com/android/reference/com/google/android/gms/auth/api/signin/GoogleSignInStatusCodes" rel="noreferrer"><code>GoogleSignInStatusCodes</code></a>
<blockquote>
The sign-in was cancelled by the user. i.e. the user cancelled some of the sign-in resolutions, e.g. account picking or OAuth consent.
Constant Value: 12501
</blockquote>
That is not my case, as I already picked an account. Any idea what could be the reason?

New Google sign in Android

移动设备管理

Android Studio

身份验证

服务器

Android

Web App

Linux

OAuth

我正在尝试使用新的Google play服务8.3获取用户令牌ID，并根据文档传递服务器ID：GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)    .requestIdToken...

问Android中的新Google登录
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android中的新Google登录EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android中的新Google登录
EN