This question already has answers here:
How to build an APK file in Eclipse?
(12 answers)
Closed 2 years ago.
I finished my android app now and i want to upload to the android market.. I have already bought the android license to upload i just want now to know what i need to do with my app.. I heard you need something signed and you need some key.. I can't remember all i heard but is there some complete guide for this or something i can read when i want to make my application into .apk and upload to market.. Im intrested in full guide so i might learn in the future how it works..
I did search the web before for this but they were so unclear guides how to do it.. Didn't help me much at all..
The Android publishing guide explains this step by step. You must sign your app with your private key and generate the signed .apk file, as explained in the linked guide.
The easiest way is to use Eclipse to sign your application. During the signing process you will be prompted to create a password. Make sure you write this down as you will need this to sign updates to your app. Once you've signed your APK, sign into the Android market (http://market.android.com/publish) and upload your binary.
Here's information on signing
http://developer.android.com/guide/publishing/app-signing.html#releasemode
Also, DO NOT lose the keystore file you need to create when signing your app. Without the original keystore file you will not be able to update your app to a newer version, because you won't be able to upload a newer version if it was not signed with the same certificate.
Related
This question already has answers here:
What is Android keystore file, and what is it used for?
(4 answers)
Closed 3 years ago.
I am new in android and I have made a app and I am thinking to publish it on play store but I do not know much about keystore and what is signed APK .
I did search on youtube and Google and also on stack overflow that help me
Stackoverflow link 1
Stackoverflow link 2
According videos and these link I am able to make .APK of android project but I am confused with some blog that say to make signed APK and save keystore in gradle file or something similar like that . Also some blog Says if you want to update your app you should store keystore locally
And I am getting very confused . Pleas explain me what is the process . Thank You .
It is necessary to generate signed apk while publish app on play store for that purpose you have to select path(key store path) where .jks file is generated that contain details app info(keystore file info) & other signing authority details
I'm working on a react native project and I generated a keystore and released the signed apk to play store few days ago.
While working I mistakenly copied another keystore into the android/app directory in the project and since then could not return to the older version anymore. Checking version history of the keystore also states it was created today rather than modified today.
How can I get the keystore back when I don't have a Time Machine setup?
If you've lost your keystore, there is no way you can update that application on Google Play. If the app is significant (millions of installs), you might get help from Google Play support.
You can't. Your only option is using software that analyses your hard drive for files that were not overwritten physically yet.
Update: the play store support might be able to help you if you used the key only for uploading with Google Play App Signing
I know it is heartbreaking, but there is no way out!
You will have to unpublish the app and try again with different package name,
If you wish that doesn't happen again you should enable google play app signin, with this you can upload the same app again with a different keystore(the process requires some good work though). But if you haven't done that already there is no help.
The same thing has happened to me, luckily my app was in alpha at that time so there were no inconveniences to my users.
I lost my android apk certificate. I formatted my mac mini and upgraded to a new MacBook Pro. Now I don't have access to the old mac. So there is no chance of retrieving the old keystore. And I am not enrolled in Google Play App Signing yet. If I enroll now, will I be able to update my app?
This is the error I get when I try update my app on play store :
You uploaded an APK that is signed with a different certificate to
your previous APKs. You must use the same certificate.
I know this is a duplicate question but I am asking it again because all the other questions are 3,4 years old. And I read somewhere that it is possible after May 2017 but I don't know how.
This is the comment I saw on quora (The link to the blog is broken):
https://www.quora.com/How-do-I-make-a-new-Certificate-Keystore-key-after-losing-the-key-of-my-Android-app
No need to Remove Your app from play Store You can Update Your app.
it’s Possible now, After May 2017 you can Update your app if you lost
your keystore or keystore password. Don’t lose Hope you can update
your app using new Keystore file please refer this blog http://geekcodehub.com/blog/
Code Hub here i wrote how to update apk if you lost your keystore
follow the step and create new keystore , I updated my app using this
step. you need to enable google play app signing on play store console
Is there any chance to update my current app? Without creating new app on playstore.
AFAIK it's not possible.
If you lose your keystore or think it may be compromised, Google Play
App Signing makes it possible to request a reset to your upload key.
If you're not enrolled in Google Play App Signing and lose your
keystore, you'll need to publish a new app with a new package name.
Source
Finally, I managed to retrieve the key. Here is How :
1- Download Disk Drill (Trial Version)
2- Download Hex Editor
Disk Drill shows all the files but you cannot recover without upgrading to Pro version, But don't worry there is a work around :)
Select the partition you want to recover. It will start getting a list of files which can be recovered. In the search bar write ".jks"
From the list select the .jks file which is around 2 kb. Ignore the other files. All jks file names will be like file000001.jks, file000002.jks...
In trial version you cannot recover it directly but you can view it. So, open the file you selected. Copy the Hex Code from it.
Open Hex editor, Paste the code in a new file. Save it with extension .jks
Run IDE (Visual Studio or any), Import the jks file and you are good to go.
In visual studio you can import .jks after archiving the android project. Select Ad Hoc and at the bottom there is an option to import an existing key.
I erased my drive completely from disk utilities and installed a new OS. But still I was able to recover the key. Never loose hope :)
The problem is the following:
I have been developing my game on my laptop until now without a keystore set in Unity editor but I was able to upload my apk file to the Play Store. Now I bought another computer and wanted to upload an update but it gets rejected because it is signed differently.
I tried copying my debug.keystore file from my old computer to my new one, but it also gets rejected because it's for debug.
So my question is: Does Unity or Google Dev Console use a default keystore which the Developer Console accepts? And if so, then where can I find it? Would it be better to publish my application again with a new keystore created by me? (It's only in closed beta, so it's not that big of a deal, but I want to know why this is happening.)
There's no way to recover your key.
I once faced a similar situation, since then,
I've made several copies of my key. Once again,
there is no way to recover this.
You need to create new a keystore and make a backup to prevent any issues in the future
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Is it possible to decompile an Android .apk file?
I have a question about Android APK signing. Here is a scenario:
There is some App on the market. I install it on my device. Extract the APk, decompile it. Then recompile it (making whatever changes i want) , sign it using my keystore and upload it to the Market and basically spoof that App. Is there anything (apart from the App itself checking who has signed the App) stopping someone from doing this?
On the play store every app has a unique package name. So you can't upload an app with the same package name. Besides that you have to agree to Google's agreements(and uploading someones app is definitely against their agreement), so If you want to get sued by the original developer then go ahead...
I'm assuming that you are asking because you are worried about this happening to you, not that you are planning to do this to someone else's app.
You won't be able to use the same package name as an app already in the market. Someone installing your app will not lose the other one. As far as the market is concerned, they are completely different apps. They will need to be published under different publisher accounts, since they are signed by different keys.
If you want to spoof at the surface level (which is all you can do anyway), there's a much easier way. Just write an app that has the same name and description as an app on the market. Someone looking for "Goofy Game" will find your ersatz title along with the real "Goofy Game" app. Caveat emptor.