您指定的指纹已被该项目或其他项目中的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 view签名报告中显示的SHA1编号与我原来的编号不同.我以为可能是一年前更换计算机引起的.我的游戏应用程序仍然能够访问排行榜和成就.当我进入Google API仪表板时，我注意到"OAuth客户端"使用的是旧版SHA1.它不允许我将其更改为新的SHA1，尽管我没有其他客户端，但说它已被该客户端或其他客户端使用".神秘的"Anroid客户端1"和"Android客户端2"都没有新旧SHA1.在"OAuth客户端"下面是"OAuth客户端(由Google服务自动创建)"，该客户端具有我的新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.

编辑3/30-尽管我(希望)它仅影响我的排行榜和成就，而不影响Firebase，Inapp购买或广告，但看来我可能永久失去了这个数字.无论如何，我都可以在Firebase中发布自己的排行榜和成就.包名称不同的新项目在Gradle signingReport中为我提供了相同的不可用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 Play Android Developer"中，位于"Google API"旁边的最顶部的下拉列表中.在返回并从"Google Play Android开发者"中删除"OAuth客户端"之前，我仍然无法添加当前的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屋！