If you want to run a global closed beta test while your app is available in some countries in production.If your app has an existing beta release, you can launch a production release in a subset of countries while continuing to beta test in other countries.If your app has an existing production release, you can launch a beta release in a new country without expanding your production release to the new country.Here are some situations where you might find country targeting helpful: If you look at HarshitG's answer on this Android thread concerning the same issue, you can see a picture of where you can get the certificate information on the Play Console.When you roll out an app to the Production, Alpha, or Beta track, you can target your release in each track to users in specific countries. If you are not using Firebase, you will have to add the Oauth credential to your backend as well. Once you locate the certificate, you need to use the SHA1 key, and generate a new Android Oauth Credential, and then add that to your google-services.json. You can access the keys with which the release version is signed from the console, under Release Management -> App signing -> App signing certificate. What this does is, after you sign your app with your keystore and upload it to the Play Console, Google will actually sign your app with a generated keystore and roll that version out. When you first signed up on the Google Play Console, you probably opted into Google's app signing service. Your app probably does not have the correct Google credentials for the Token API.

Google app builder release