Android Question [Solved]FireBase Auth: Different package names same SHA-1 fingerprint?

[KMatle]

Maybe it's to hot here to think clear but...

So far I've signed all my apps (private key) with the same key/different package name to Google Play. All working fine.

Today I've added a new project in the firebase console. To use the auth service I've added the SHA-1 fingerprint. It was rejected because it was used in my other project.

I thought different package names with the same private key will lead to a different SHA-1 fingerprints. Am I wrong here?

 

[Erel]

The SHA-1 hash is not related to the package name, only the signing key. If firebase doesn't allow two projects to use the same hash then you will need to use a different key.

You can use #SignKeyFile and #SignKeyPassword to manage the keys.

 

[KMatle]

you will need to use a different key

Thank's. Will this cause any problems uploading it to Google Play? (I thought same key = same developer).

 

[DonManfred]

Today I've added a new project in the firebase console

I guess you should add a new APP to your project instead of making a new project. i have 6 apps in my project. All working fine

 

[KMatle]

I guess you should add a new APP to your project instead of making a new project.

Nice! I didn't think that way. I assumed 1 project = 1 app. Now everything works. Thank's...

PS: It seems that Google has added the check recently. I had already two projects with the same SHA-1