All geek questions in one place

Getting duplicate fingerprint errors while updating SHA-1 fingerprint for oAuth2 client ID for Android

Just a few days ago, I changed my SHA-1 fingerprint (from signing to dev) for testing purposes. Now I want to go back to signing the SHA-1, but this does not allow me to add a live SHA-1 fingerprint. It gives me duplicate fingerprint error.

I am sure that we do not have another client ID already registered in the fingerprint application. We also do not have remote projects. My application is already in the store. I can't just change the package or keystore to make it work.

When I update the fingerprint SHA-1in the Google Cloud Platform Developer Console, I get the following popup:

Duplicate fingerprint

The fingerprint you specified is already being used by the Android OAuth2 client ID in this project or another project

Anyone who has a similar problem that has reached a solution?

+4
source share
2 answers

I found a fix for this problem.

When the console asks for the name SHA1 and Package for the new API that you use in the same application.

Just save the same SHA1 code and change the package name a little. For example: com.example.exampleapp to com.example.exampleapp 1 .

I know this is not a complete proof, but I have many different Google API calls in my application, just changing the package name a little.

, .

, .

0

API , OAuth, .

One of the previous projects that I had already deleted still contained it.
  • OAuth, " ", .

API, OAuth, , , .

This should really be changed!

+3

Source: https://habr.com/ru/post/1649991/

More articles:


All Articles