5

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.

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 - 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.

enter image description here

4

1 回答 1

1

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

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 网站的响应，尽管它的响应始终是“无法访问服务”。

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

因此，删除 SHA1 似乎不是从 Play 服务中永久流放，只是一个棘手的过程的开始，以使其重新建立。

于 2018-04-02T19:23:23.637 回答