I have an android app which is available on google play.
While creating an apk for release, there was a keystore that was created for signing.
My question is, if after the release, I have some enhancements underway (like facebook or google+ integration), which requires that the dev registers his app using the keystore, which keystore do I use?
Should it be the debug keystore (~/.android/debug.keystore) or the one that was created while packaging my app?
EDIT
Thanks for the answers so far.
To confirm, from the below answers I understand that, when testing this enhancement (before deploying the app to play store) & to register my app at facebook, I will be using the keystore that was used for signing the first apk file for this app and NOT the 'debug.keystore'. Correct?
But, while testing, wouldn't my app be sending 'debug.keystore', if I am building on eclipse platform? Or does the 'debug.keystore' become invalid once I have a new keystore generated for creating the previous apk file?
It's rather too confusing, and want to be clear with this...
You have to use, keystore which is used for generating apk file for playstore. Dont use another keystore, becoz it will give new one but wont updated the old one.
debug keystore (~/.android/debug.keystore) is not going to work for you.
As you mention that your application is already available in Google Play, that means while singing your application it ask Create new Keystore or use Existing one
Then choose Use existing keystore
Give your existing keystore path, and password.
This will give you a build that you can release in Google Play..
Before that make sure that increase the android:versionCode and android:versionName
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="YOUR_PACKAGE"
android:versionCode="1"
android:versionName="1.0" >
Hope this help you.
Plz ask if having any sort of problem.
You have to use your signing keystore which you used while uploading your app to developer console. The one that was created while packaging your app
only used for your signing keystore because already you release the application in play store so you can use new key that time is not release for updated version it's a one of the new application so you can use previous kestore for your updated appp.
Related
Hello all I have an APP on play store and I uploaded the bundle file first time and kept the keystore save it and then uploaded to playstore. After some time I updated the APP with version 2 and used the keystore app signing key which I created in the first time it got uploaded
But now I am doing the same and the playstore say
your Android App Bundle is signed with the wrong key. Ensure that your
app bundle is signed with the correct signing key and try again
I don't know what to do here, its so bad I am stuck here This is my first APP and I already have this signing issue can you suggest me how to upload the new versions of APP on playstore and fix this signing key issue.
Check for the key store you use with the app is correct and no changes made on it.Try again.And also ensure that the key store you are using is of the same app not of any other app.
There a different approaches to overcome this problem. See also the link code4rox provided though nothing of these proposals worked for me and I wasted many days and nerves. My suggestion to you would be:
Reset the old keystore with the support of Google Play Developer Support (Play Console)
Create a new keystore with your IDE
Convert the new keystore to a .pem file with JDK's command line tool "keytool" or use "KeyStore Explorer" (open source GUI replacement for the Java command-line utilities keytool and jarsigner)
Send the .pem file to Google Play Developer Support.
Two days later you can update your App with the new keystore.
I am trying to upload an APK built in Unity3D to the Play Store, but it says I can't upload it because it's signed as debug mode. However, it's not! I've done absolutely everything in every forum:
Development checkbox unchecked.
Keystore set
Microsoft Visual Studio switched from Debug to Release
In the android manifest I had "debuggable=true", I removed it.
What else must I do? I think that's all.
Hello friends if you already publish your app and you want to do an update follow this.
If you are sure about your keystorage settings and if development
build is not active continue with second part.
If you are using Facebook SDK or some Google services there's a
configuration problem. Go to Assets > Plugins > Android >
AndroidManifest.xml and find android:debuggable= and just set it
false like:
android:debuggable="false"
That's all guys. Thank you and bye bye!
Okay, so in order to sign the app for distribution via Play Store you also have to add a key and sign your apk with it. To do this:
Find the Publishing Settings under Player Settings
Create a new keystore by selecting a keystore name and password (confirm the password), select "browse" to save the keystore
Select "Create a new key" under Key Alias
A new window opens; enter the necessary information.
Select the newly created key.
Build
Your app is now signed, you can upload it to Play Store
All the Play store does is look at your APK using public tools. You can reproduce exactly what it does.
To check the signing key (which will need to match to update the app):
`keytool -list -printcert -jarfile app.apk`
To look at the manifest you use a tool called aapt which comes with the android SDK. This stackoverflow question tells you how to use it to tell if your APK is debuggable.
If your APK is debuggable as defined by the method above then you haven't changed everything you need.
I have published my app on Google play a few days​ ago and since then i had to uninstall and reinstall my Android studio. Now I don't have the signing key anymore. Is is possible to make the exact same or i can't update my anymore on Google play?
Signing key is a jks file independent from AS.
If you have lose that file, you can't update your app anymore.
As mentioned in this other answer
You can create a new keystore, but the Android Market wont allow you
to upload the apk as an update - worse still, if you try uploading the
apk as a new app it will not allow it either as it knows there is a
'different' version of the same apk already in the market even if you
delete your previous version from the market
Do your absolute best to find that keystore!!
When you find it, email it to yourself so you have a copy on your
gmail that you can go and get in the case you loose it from your hard
drive!
You have to save the jks file in a directory different from the Android Studio one. It is not related to Android Studio
I suppose if you change pakage name and app name it shouldn't give you any problem on google play console. But you can't update that one, sorry. Try your best to recover the jks file!
I have created an Android app and used Android google Maps API v2. and generated signed .Apk file, I have a question for you that when I made changes in my project it does not update my signed .Apk file. For example when I change API key in my AndroidManifest.xml Android Studio does not update it in signed APK file. How it is possible to make changes in signed apk file. ? I am new in Android and StackOverFlow, and excuse for all mistakes in asking question, thankx
When you added API key that generated from your .keystore then you must built signed .apk with the same keystore for publishing the app in store.
and when you provide any updates then there is no need to change the API key again but you must built signed .apk with the same keystore again.
I made an Android App and posted it in Android market, and now I'm made some updates on my Apps and trying to give a next version of the same app. The problem is I missed my KeyStore file I generated previously. But I'm having my old vesion APK file. Now I'm not able to upload the next version, the developer console says
The apk must be signed with the same certificates as the previous version.
as error. May I get any help to make new version for my android app now..?
There's currently no way of retrieving a lost signing key. What you can do is get a new one, pull your app from the market, and upload your update using a different package name.
Sorry, as far as i know you are not allowed to update your application now.
To update existing application on market, you must have that KeyStore file and also remember the password.
Your best bet is to unpublish the old apk and publish a new apk signed using a new keystore.
Please make sure that you have the previously used key store file with you
As per the documentation available on developer.andoird.com you must do the followings
Before uploading the updated application, be sure that you have
incremented the android:versionCode and android:versionName attributes
in the element of the manifest file. Also, the package name
must be the same as the existing version and the .apk file must be
signed with the same private key. If the package name and signing
certificate do not match those of the existing version, Google Play
will consider it a new application, publish it as such, and will not
offer it to existing users as an update.