1

I'm having a lot of trouble with this, it's been a few days.

I have successfully tested google maps on my simulator, but also on my personal device without any issues, everything was working perfectly. However, once i uploaded it to the store for internal testing, my testers are not able to see the map.

After some research, it seemed that the reason causing this problem was that I was using my debug certificate instead of my release certificate on my Google Cloud Platform. I changed the SHA-1 certificate on my existing API and now the map is not showing on neither my personal device (through Android Studio) nor my tester's devices - it is only working on my simulator.

Am I missing something? Should I have tried to create a new API instead of modifying the existing one? Does any of this can be related to the "OAuth consent screen" which I'm not familiar with at all?

Thanks for your help, any feedback would be really appreciated.

TheGix
  • 108
  • 1
  • 8
  • 1
    I hope this answer help you -> https://stackoverflow.com/questions/32544737/google-maps-are-not-showing-up-in-a-signed-apk ---- or this -- https://stackoverflow.com/questions/41437728/in-my-signed-apk-not-showing-google-map-need-step-by-step-process?noredirect=1&lq=1 – Anwar Elsayed Apr 01 '21 at 18:52
  • Thanks Anwar, it was indeed helpful, although i have seen those posts before, one answer (not selected) was the right answer. – TheGix Apr 01 '21 at 19:20

1 Answers1

1

It turns out that I have chosen Google Play App Signing, so the android studio SHA-1 was not the correct on to add for Google's API because Google removes your uploaded certificate and then sign the App with a new one.

So the new SHA-1 is actually available on the console:

enter image description here

Original answer: https://stackoverflow.com/a/44794349/7356056

TheGix
  • 108
  • 1
  • 8