其他OAuth2客户端已使用的SHA1指纹 [英] SHA1 fingerprint already used by another OAuth2 client

问题描述

不久前，我在Google Developers Console中为Android应用程序创建了一个项目，该项目的Oauth2客户ID为程序包名称和SHA1指纹.以某种方式创建的项目没有项目ID，这使我无法将其部署到App Engine.我删除了该项目，重新创建了该项目，现在尝试添加具有相同程序包名称和SHA1指纹的新客户端ID.删除原始项目一个月后，我收到您指定的签名指纹已被另一个Android OAuth2客户端使用". 有没有办法在新项目中重用软件包名称和SHA1指纹?

Some time ago I created a project in Google Developers Console with Oauth2 client id for android app with package name and SHA1 fingerprint. Somehow the project got created without project id, which prevented me from deploying it to App Engine. I deleted the project, recreated it and now trying to add a new client id with the same package name and SHA1 fingerprint. A month after deleting the original project I'm getting "The signing fingerprint you specified is already used by another Android OAuth2 client". Is there a way to reuse package name and SHA1 fingerprint with the new project?

推荐答案

这听起来不像是可以解决的问题.

This doesn't sound like a SO resolvable issue.

您的SHA1指纹似乎仍与已删除的项目相关联(可能处于不确定状态). Google支持是唯一可以帮助您的人.

It seems like your SHA1 fingerprint is still associated with a deleted project (which is probably in limbo). Google Support is the only one who can help you.

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