I get strange problem. I app is available on play store. When app is install from eclipse, map is showing. While at same time, if app is install from play store, map is not seen. I do not know where i make mistake. Please help.
Link to app - https://play.google.com/stor/apps/details?id=netleon.sansar.childsafeapp
With the Eclipse you have a debug keystore, for google play store you have a different key store. You api key needs to match the keystore you have used to sign the application.
Related
Previously, I have downloaded a modded version of an app (minion rush, yeah hilarious) and want to be able to download the Google Play Store version afterwards, but instead it gives me an error message which someone has told me it was a signature error.
I've been trying to sign a different APK, that I found off a website, that is the latest original version of the app, and when I go to update it from the Play Store, it shows an error message. This does the same thing when I uninstall the apk and install the version from the Play Store. The message is the same thing that happened before, from when I downloaded the modded version the first time, deleted it, and went to download the Play Store version.
The APK doesn't work without being signed but works fine when it is (btw what I did to sign it was use MT Manager with V1+V2+V3). The only problem is that I can't log into my account on the app and receive my accounts progress.
So, is there any way I can install the app from the Play Store, or a way to allow myself to log into the signed APK?
Welcome to Stack Overflow. Short answer: You can't. Google Play or the developer of the app has signed the app with their private key (which you don't have) and after you've modded the app and resigned it with your own key it has a different signature. This is a safeguard to protect users from installing tampered apps. Imagine someone managed to update your installed and set up banking app with his tampered version. Yikes. The login probably does not work for the same reason with the game's servers denying access because of the different signature.
I created a game in Unity and uploaded it in the Google Play Store. I kept the Unity Publishing Settings like this, built the game and then uploaded it.
Later, I edited my game and built it again using the exact same publishing settings but I changed the version and bundle version to 2.0. While uploading the APK, I got the error:
You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode.
I really need to know what to do now.
I can't delete my game from play store.
Thanks in advance!
You need to select the same keystore that you selected the first time you uploaded your app. The error message suggests that you either selected a different one, or used the alias of a different key in the keystore.
If you have lost that keystore or the alias/password of the key in the keystore, then you have to create a new app if you're not enrolled in App Signing by Play, or if you are, then you can contact Google Play to reset your key.
Think something weird has happened with Google Plays auto App signing, I'm having the same issue:
https://forum.unity.com/threads/publish-update-failed-android-playmarket.543793/
Here I am developing Android app with android studio. I turned my google account into a google developer account and then published my app in the play store after signing that app within my computer. After a month I published an update for that app with the same package name. I also upgraded the "Version Name" & "Version Code". I checked the the situation by using a phone which has the initial release of the app, but after I released the update the specific page of that app in play store doesn't show an update button ("open"button is there).
How can I correct this?
Thanks.
If your phone with the "initial release" of the app didn't install it from the Play store, then the Play store won't update it. I suspect this will be your problem.
The Play store will only update apps for which it did the initial install (to avoid treading on the toes of app developers during development or other app stores).
The way it checks for "Did the Play store install this" is "Does the signature of the app match the signature in the Play store" and "does the user on the phone have a record of install from the Play store on their account on any device".
After updating an app on play store it can take several hours to be available on play store. Just wait for couple of hours.
So first of all you have to make sure the following three points are in place:
You are installing exactly the same variant from android studio compared to the one you published on google play store.
The app you installed from android studio has a lower "version code"
You are using exactly the same signing key.
Most likely the third point is what is stopping this from working. The problem is that if you are using app bundle as publishing format, that apk is not created yet when you upload the bundle and it will only be create and SIGNED at a later the stage, when the app is about to be distributed on a specific device.
Unfortunately, there is a chance, like in my case, that the signature still will not match perfectly even if you used exactly the same key to sign the app, reason being that if you have singed up for Google Play Store signing, google will add some metadata: "It does however insert a minuscule amount of metadata that helps with verifying the source and integrity of the distribution. This metadata comes in two flavors: For all apps uploaded to Google Play, Play has been adding security metadata after the signing block to enable features such as authorized P2P app sharing. We announced this originally in a blog post in 2017. For apps uploaded as app bundles, we will improve this security by introducing what is called a source stamp. This source metadata is inserted into the app’s manifest by bundletool. When the APK is generated on Play’s server, it’s also signed with a Google key in addition to your app signing key."
I yet have to solve this issue unfortunately
I have an issue which is related to an app that I have in Google Play, and I am planning to update it.
The issue that although I still have the previous key but I am not sure why Google Play Control is complaining that I don't have the same fingerprint
See below picture
Any idea how to solve it?
Use "Generate Signed APK" with the same key store, key alias with v1 and v2 checkbox. If you lost one of them, Google store will not accept it.
If you want to update unpublish app, you can remove it and create a new project.
If the app is published, it can't be removed from the store.
I have a problem about google map.
I did an app about include google maps.When i run the app with
Eclipse ,map is seeming everything is ok.
I signed the app and upload Android Market. When i dowload this app
for check i see the map blank.
I changed map key but it doesnt work?
Anybody know about that?
Have you changed the key of the google map component before sign? you must have a key for debug and another for published application.