The book can be significanly beneficial to the apprentices if it completes the Maps project with the needed Cloud/API/Billing setups to actually release it on the Google Play store. Only a gray area (though the Search button and all other functions worked fine!). You should get both the release and debug. I set all up, but still the App Release version of the app did not show the map upon launch on a real phone for alpha testing. Open a terminal and run the keytool utility provided with Java to get the SHA1 fingerprint of the certificate. Add a Billing account to the project in Google Cloud.Now to check this file copy your path up to. You can get to see in the below screenshot. After clicking on this option you will get to see the path for your debug.keystore file. Inside Tasks, navigate to android and double click on the signing report option. Update Google Cloud API Credentials (not sure if optional if an app does not need Restrictions?) After clicking on the app, Navigate to Tasks.Update the release google_maps_api.xml with the API key (not just the debug file, so 2 files must be updated).However, it seems to actually release a Google Maps API app thru the Google Play lifecycle, one needs: Keytool -list -keystore MyAppKeyStore.jks Select the App certificate tab, and then copy the SHA-1 to your firebase console. On the left menu, select Development tools > Internal app sharing. I tried the following in the key store folder of my app: Get SHA1 fingerprint certificate in Android Studio whatever by Adventurous Albatross on Comment 1 xxxxxxxxxx 1 keytool -list -v -keystore /.android/debug. To find the certificate Sign in to your Play Console. ‘ However, Section VI does not cover the ‘release’ SHA-1 or API keys for a Google Maps API based app. Chapter 13 P 241 states ‘getting the SHA1 key for release builds will be covered in Section VI, “Submitting Your App”.
0 kommentar(er)
