您指定的指纹已被此项目或其他项目中的 Android OAuth2 客户端 ID 使用 [英] The fingerprint you specified is already used by an Android OAuth2 client ID in this project or another project

问题描述

我注意到我在 android studio 中的 gradle 视图签名报告中显示的 SHA1 编号与我原来的不同.我想可能是因为一年前换了电脑.我的游戏应用程序仍然可以访问排行榜和成就.我在使用 Google API 仪表板时注意到OAuth 客户端"有我的旧 SHA1.它不会让我将其更改为我的新 SHA1，并说它已被该客户或其他客户使用"，尽管我没有其他客户.神秘的Anroid 客户端 1"和Android 客户端 2"既没有旧的也没有新的 SHA1.在OAuth 客户端"下面是OAuth 客户端(由谷歌服务自动创建)"，它有我的新 SHA1.我继续删除了那个，尽管它警告我它在上周已经使用了 147 次(我认为这是我即将衰老的证据).似乎我必须删除它才能释放不是自动创建的OAuth 客户端"的号码.

I noticed my SHA1 number showing from the gradle view signing report in android studio was different from the one I had originally. I thought maybe it was from changing computers a year ago. My game app was still able to access leaderboards and achievements. I when to my Google API dashboard I noticed the 'OAuth client' had my old SHA1. It wouldn't let me change it to my new SHA1, saying it 'had already been used by this client or another client', although I had no other clients. The mysterious 'Anroid client 1' and 'Android client 2' had neither the old or new SHA1. Underneath the 'OAuth client' was 'OAuth client (auto created by google service)' which had my new SHA1. I went ahead and deleted that one, despite a warning it gave me that it had been used 147 times in the last week (evidence of impending senility on my part I suppose). It seemed I had to delete it to free up the number for my 'OAuth client' that was not auto created.

现在看来我搞砸了，因为当我尝试更改 SHA1 时它仍然给我已经在使用的消息"，而我的游戏应用程序根本无法再访问 Google Play 服务.我想我应该删除OAuth 客户端".我能从中恢复吗?随着时间的推移它会释放吗?另一个帖子建议删除客户端 7 天，但我没有看到删除整个客户端的按钮，并且担心删除同一页面上的 API 代码.

Now it appears I'm screwed, as it still gives me 'the already in use message' when I try to change the SHA1, and my game app can no longer access Google Play Services at all. I'm thinking I should have deleted the 'OAuth client' instead. Can I recover from this? Will it free up over time? Another post suggested 7 days for clients to be removed, although I don't see a button to delete the whole client, and am concerned over the deletion of the API codes on the same page.

EDIT 3/30 - 看起来我可能已经永久丢失了这个数字，尽管(我希望)它只影响我的排行榜和成就，而不是 Firebase、Inapp Purchasing 或 Ads.无论如何，我可以在 Firebase 中推出自己的排行榜和成就.具有不同包名称的新项目在 Gradle 签名报告中给我相同的无法使用的 SHA1.

EDIT 3/30 - It looks like I may have lost this number permanently, although (I'm hoping) it only affects my Leaderboards and Achievements, not Firebase, Inapp Purchasing, or Ads. I can roll my own Leaderboards and Achievements in Firebase anyway. New projects with different package names give me the same unusable SHA1 in the Gradle signingReport.

推荐答案

我终于通过电子邮件收到了来自 Google 支持的有用回复，提供了有关如何开始恢复过程的线索:

I finally got a useful response from Google support through email, providing just a clue on how to start the recovery process:

I understand you're receiving a Client ID error when trying to link your app to a Game Services project. This error message is displayed because your package ID and SHA1 are already in use by another Client ID.

To resolve this issue, please use the steps below to delete the Client ID from your Google Developers Console (formerly Cloud Console).

Important: Do not delete the Google Developers Console project before deleting the Client ID. If you’ve already deleted the project, you will need to undelete it from your Projects list.

1. Use the following URL to access the project - https://console.developers.google.com/project/186639667931
2. Select APIs & auth > Credentials
3. Under "Client ID for Android application" click the "Delete" button.
4. Try linking your app in the Play Console again. If you’re unable to view or undelete the project linked in step 1, please try accessing it while logged in with the primary email address on your Play developer account.

没有Android 应用程序的客户端 ID"，但在OAuth 2.0 客户端 ID"下有一个OAuth 客户端"，所以我删除了它.那仍然有一个旧的 SHA1 号码，因为它不会占用我当前的号码.所以我并没有真正删除我当前号码的某些内容，而是删除了整个客户端并显示了一个空白屏幕.这里有一个陷阱.我将我当前的 SHA1 号码添加到该屏幕，它接受了.现在我可以从我的应用程序中再次获得来自 Google Play 站点的响应，尽管它的响应始终是无法访问服务".

There was no 'Client ID for Android application', but there was an 'OAuth Client' under 'OAuth 2.0 client IDs', so I deleted that. That still had an old SHA1 number as it wouldn't take my current one. So I wasn't really deleting something with my current number, but deleting this deleted the whole client and brought up a blank screen. Here there was a bit of a trap. I added my current SHA1 number to that screen, which it accepted. Now I was able to get a response from the Google Play site again from my app, although its response always was 'Cannot access services'.

事实证明，此屏幕是默认屏幕，即Google Play Android Developer".我得研究一下这是什么，但我需要添加一个 SHA1 到我的实际应用程序名称.我最终发现隐藏在最顶部的下拉列表中，旁边是Google API"，其中包括我下载的示例应用程序和Google Play Android Developer".在我返回并从Google Play Android Developer"中删除OAuth Client"之前，我仍然无法将当前的 SHA1 添加到其中.这买了相同的默认屏幕，所以我回到下拉菜单，选择我的应用程序名称，然后终于能够将我当前的 SHA1 添加回它.

As it turns out, this screen was the default screen, which is 'Google Play Android Developer'. I'll have to research what this is for sometime, but what I needed to add a SHA1 to was my actual app name. I ultimately found buried in the dropdown list at the very top, next to 'Google APIs', among example apps I had downloaded and 'Google Play Android Developer'. I still couldn't add my current SHA1 to it until I went back and deleted the 'OAuth Client' from 'Google Play Android Developer'. This bought the same default screen back, so I went back to the dropdown, selected my app name, and then was able to finally add my current SHA1 back to it.

因此，删除 SHA1 似乎不是 Play 服务的永久流放，只是重新建立它的棘手过程的开始.

So deleting a SHA1 appears not to be a permanent exile from Play Services, just the start of a tricky process to get it reestablished.

这篇关于您指定的指纹已被此项目或其他项目中的 Android OAuth2 客户端 ID 使用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！