Develop Reference

Google maps not showing on signed apk android

In my project the Maps and everything, but when I generate a signed APK it doesn't works, I already have the "google_maps_key" in my project, I went to Google Console and put any restriction so I could test not just from my Android Device and still nothing!

You should create a release key and add it to your project .
Release APK file not showing google maps
This link answers you proble. It's a common problem .
You should create a .jks file first and store it somewhere in you app folder.
Then Create a SHA1 Fingerprint n put it on the credentials site.

Change a signed apk version code

I have this signed APK and I need to change the version-code in the manifest, because I lost the keystore ( #*!$##&£!! ).
I've seen the question How can I update the version of an APK which I did not create myself , but no success... please help!

You could use apktool to decompile that apk then change the version in manifest. But the problem is you have to recompile it again then you need to sign the apk with jarsigner. There you need the keystore to sign the apk again. and to update the previous apk you need to use the same keystore.

You can not create new sign apk without KeyStore file.
if Your app new on google play and not more download.
then You want create new sign apk with different package name and new Keystore file.
and upload it on GooglePlayStore.
other options are available but i think it is risky.

Need previous keystore file

I now finished upgrading android app... and trying to upload this upgraded version to google appstore.
But the problem is we don't have keystore file which was used for previous version.
And google app store doesn't permit me to upload apk cause SHA1 is different.
And apparently my customers don't have previously used keystore file.
What should I do?

If you've lost your Keystore file then there is no way that you can update the app in Play Store.

Which keystore to use?

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.

The apk must be signed with the same certificates as the previous version

I have uploaded on apk file on the google play account,
apk i have created from eclipse by right click on the project and export and put following details in it
password,alias and developer units only.
and i have uploaded successfully on google play account.
But now problem is i have deleted this apk from local and also i am unable to uplaod any other apk if try to update 2nd apk with version code = 2 and version name = 1.0 then also it is giving me error that
The apk must be signed with the same certificates as the previous version.
So please help me to solve this issue now what can i do to upload a new updated apk in this application.

You are not using the same keystore file to sign your apks.
the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update.
Taken from here,
The apk must be signed with the same certificates as the previous version
The only way is to sign your update package apk with the same key which you have used for the previous version. No other go. Google is strict about it.

For the same application you are updating it's version. Then there is
no need of having previous apk file but there should be same keystore
which you have used to sign the first apk file which is on google
play. Also follow the same steps which you have done for first apk
file.
In case you don't have same keystore then :( you simply cannot update the same application as of now.