This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
I lost my .keystore file!
I have an app on the android market for 5 months now. I haven't updated it in probably 2 months, so yesterday I went to work coding it. I finish my coding, go to export the app and it asks for my Keystore. The only problem is that when I try the use existing keystore option, THERE ARE NONE!!! So, I go through the long process of creating a new keystore and get the application exported and try to update the app and it tells me the keystores don't match, which is true.
This is the same computer I developed the first version of the app with, using the original keystore so where did it go? How do I retrieve it? My app has 500-1,000 downloads and it's $0.99 so I really don't want to piss 500 people off by removing the app and uploading a new one.
Any suggestions?
I'd suggest contacting the Google team and see if they can retrieve it for you?
Related
This question already has answers here:
Android Keystore File Lost [duplicate]
(4 answers)
Anyway to change Keystore or Keystore's Info on android without publish new app
(1 answer)
Closed 9 years ago.
Is there anyway to get the keystore file from .apk, Unfortunately the keystore file is missed now i need to update my app which is there is Google Play.
Please help, Thnx in advance
No, it's not. Imagine the huge security breach that would be. In addition to the already existing problem with code decompilation and recompilation, hackers could even sign a modified APK with the original key and pretend it to be original.
This question already has answers here:
I have forgotten my keystore password and I want to install my apk on Google Play. What do I do?
(6 answers)
Closed 9 years ago.
I updated the adt plugin for eclipse and it deleted the keystore that held my private key for my app that is already on the app store. This was the only copy of the private key. Is there any way to restore or rebuild this key for an update to the play store?
No.
Try to get some utilities that recover files on your computer and if you're lucky you can restore the keystore.
Considering you lost the complete file, and not only the password; NO. You can't update this version of the app anymore, unfortunately. If you'd still have the file and not the password you might be able to run some kind of smart brute-force (still very unfeasible).
You could try some tools that recover deleted files though, but I can't help with that as I have no experience there.
You will not be able to update your app in the Play Store without it being signed by the identical key, and there is NO way around this.
Your best hope is to somehow recover the keystore you used to sign your app.
This question already has answers here:
I lost my .keystore file?
(12 answers)
Closed 8 years ago.
I don't know how to solve my issue.
We published an android app on the Android market. After fixing a few issue, we are not able to release it as a next version of the app in marketplace because we have lost the private key used to sign that build. If the update version is not signed by same key, android is not accepting the build.
For this application, few users have already purchased it on the market. If we upload the same application with different package name, purchased users will be unable to get the updated version. How can I solve the issue ? Any suggestions regarding this ?
Thanks in advance...
There's no way to recover your key. I once accidently deleted mine and faced the same problem. I ended up emailing the few users who had already purchased my app about my mistake and told them to let me know who they are and that I would refund their purchase of the app again, if that's what they wanted. Since then, I've made several copies of my key. Once again, there is no way to recover this.
On the other hand, you could try doing a system restore, on your computer, to a previous date in which you haven't misplaced or deleted your key yet.
We had the same problem once. As stated above there's no way to recover your key. But you could try brute force to recover it.
This thread was particularly helpful: Forgot Keystore password, thinking of Brute-Force detection. will it corrupt the keystore?
You should at least have a small idea of what your key should be. Lets say you know that the key have android, app and 2012. The scripts will try every combination of these three words plus others. In our case we recovered it in our first attempt.
Good luck.
This question already has answers here:
This version of the application is not configured for billing through Google Play
(21 answers)
Closed 8 years ago.
Firstly I have been googling for goodness knows how long and have followed several other question's answers to no avail.
I have an Android application with in-app purchases, using the test keys (android.test.purchased) everything works fine. Using my actual product I get the following error:
This version of the application is not configured for billing through Google Play.
I have followed the steps outlined by both Google and various StackOverflow answers:
Upload a signed APK to Google Play (not published)
Setup an in-app item (published)
Install the same APK onto the phone.
Ensure your google account (from the phone) is listed as a tester in Google Play.
Add public key to billing code.
Wait for some time just in-case!
I still get the problem mentioned above. What could I be missing??
Edit:
A thought that has come to mind, does it matter what you use to sign the exported APK with?
I never like to answer my own questions, as it always looks like I'm after the rep which I am not!!
After much trying I finally managed to get this to work, it appears that you need to wait around 6 hours for an apk to be recognized as valid for in-app purchases. What is strange is that if you upload the APK during the early morning (UK time) it gets through the system faster (US/UK lag!?).
So to sum up for anyone that may have come across this answer, just be patient!!
There is one obvious thing missing: setting your public key in the billing library code.
Edit: A thought that has come to mind, does it matter what you use to sign the exported APK with?
Yes, you must sign it in release mode [1]. Export the application in Eclipse, and when it prompts you for a certificate, point to your .keystore file. Follow the steps and you'll have your apk signed with your release key.
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.