1) I have uploaded apk in play console 2) I have 2 sha1 in firebase console 3) I used Google signing in Google Play console.
Anyone know how to tackle with it?
Asked
Active
Viewed 37 times
-3
-
I think you need to see [this reference](https://stackoverflow.com/a/44672565/5860777) – Andy Developer May 30 '18 at 10:17
-
you need to add sha-1 key created from your sign apk(release apk) with the credentials that you used to create sign apk – Hitesh Sarsava May 30 '18 at 10:21
-
@AndyDeveloper I tried this, but whenever i copied it... it shows error something like "sha is already used in this project or other project....." – user9869564 May 30 '18 at 11:33
1 Answers
1
First thing please create SHA1 using your keystore which you are using for creating a release apk,
After generating SHA1 put in a console and download the google_services.json file again and put in your project after build again, Finally generate Release apk it will.
Dhaval Solanki
- 4,589
- 1
- 23
- 39
-
I tried this option also... I have added SH1 in firebase console (Now there are 2 SHA1..dont know which is which)... then downloaded the latest google_services.json file and replaced it in project...then released it...but still the problem remains same... – user9869564 May 30 '18 at 17:08
-
-
got the solution.... thanks@Andy Developer and @Dhaval Solanki....both of your answers worked for me.. mistakenly i had created duplicate project and it contains SHA1 from play apk signing... – user9869564 May 31 '18 at 05:05
-