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.
Related
I am trying to upload a new version of our app (first time being exposed to android) and am dealing with this error when trying to upload the .aab file. I assume it means I don't have the original signing key file, I do not have access to it either, how can I get past this to upload?
You should find the old version of app and keyStore file that was first uploaded with your previous update, if you create and upload new keystore google will always prompt with this error, i hope you find the old keystore file used for previous version update
I have an Android project in my Google Play Developer Console. I managed to automate uploading of nightly build to the Alpha channel but I also need to download the APK to get its md5 hash for my internal purposes.
I can't get md5 hash before uploading because App Signing by Google Play is enabled for this app so each APK file that I upload is re-signed with Google's keystore.
Is there a way to download APK file from Alpha channel for my own project?
You can download original and re-signed APKs from the Play Console, in the Artifact Library.
There isn't an API to download re-signed APKs today unfortunately.
Pierre's answer is correct. However, taking an MD5 hash of your APK is probably a mistake. In particular if you use this for verification you will probably introduce a bug. This is because of Google Play security metadata. This won't be consistent on all versions of your APK, and in particular can change with time without you republishing.
If you need to check the authenticity of your app, can I recommend the primary thing you check is the app signing certificate hash. This should be enough for almost anyone and is what major app developers do. If this is not good enough, please check the hash of any particular section of your app you are worried about (eg the classes.dex or a particular resource file). Please don't check the whole APK, you will cause yourself problems.
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 purchase the certificate for eclipse from play store and publish one Application that was made in eclipse.
Now I am working on android studio and publish app on old certificate.
Is this possible or not?
Yes its possible, Use the same keystore certificate file to sign the build on Android studio.
This is possible, you have to use your old keystore file to build the sign APK.
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.