@Erel
Yes that's my question too, why use 2 keys? I also do not understand, and I just try it as shown picture below.
1. How do settings only use the same key during development with the one in publish?
2. What is the meaning of the image below? Why there are 2 keys
3. Why use 2 keys, the google maps can appear? if use 1 key, can't show the maps
4. How to fix this?
New apps Step 3: Upload your signed app
Follow the steps to prepare & rollout a release.
Before the app is delivered to users, Google Play will remove your upload key signature and re-sign with a new key.
This seems to be causing me to create 2 keys, does it have to be so? Have you ever tried uploading google map project to google play store?
Because from your tutorial here, I have done
No need to use Google AppSigning. Important: App Signing opt-in is permanent
Google Play App Signing is an optional program. If you prefer, you can continue managing your own keys.
No need to use Google AppSigning. Important: App Signing opt-in is permanent
Google Play App Signing is an optional program. If you prefer, you can continue managing your own keys.
@Erel
Yes that's my question too, why use 2 keys? I also do not understand, and I just try it as shown picture below.
1. How do settings only use the same key during development with the one in publish?
2. What is the meaning of the image below? Why there are 2 keys
3. Why use 2 keys, the google maps can appear? if use 1 key, can't show the maps
4. How to fix this?
Just wanted to add to this old post because I had the same issue and found the problem using information from this thread.
What I did to solve the problem had been to use the SHA-1 certificate fingerprint from the App signing certificate instead of the one I had been initially using from the Upload certificate for the Google API SHA-1 input value.