Android Google Services: Api Key And Sha-1 Fingerprint For Release And Debug
Solution 1:
It's a little bit confusing, I think the best solution to get rid of such scenarios is to add an applicationIdSuffix
so you (and any other service) could distinguish between builds: com.myapp.beta
for build and com.myapp
for release.
I'd recommend you to take a look at this detailed tutorial: http://medyo.github.io/2015/different-android-app-resources-gradle-build-type/
Hope that answers your question
Solution 2:
OK - after some investigations, yes, you do put your package name twice and then you put the SHA-1 fingerprint for the release and debug version separately. This will make PLACES work.
Also, from my investigations, I noticed that the APP_INVITE error pointed to no client ID found for the package. Please note that this is referring to your OAuth 2.0 client IDs which can be found under your API keys in your Google Developer Console. Changing that SHA-1 key (there is no option to put in a development SHA-1 and a debud SHA-1in this case) will result in APP_INVITE working.
Post a Comment for "Android Google Services: Api Key And Sha-1 Fingerprint For Release And Debug"