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
Related
In the recent try for uploading a new version of apk for existing application to PlayStore, threw an warning message as mentioned below
So the question is, is it mandatory to upload only aab files to PlayStore or normal apk file can also be updated.
If aab file has to be uploaded, then how to sign the aab file before uploading.
I referred this Link for Goolge App signing. Is this also required ?
Note:
The application developed is a cordova application. So if the above mentioned things are mandatory is the procedure different to build for cordova application ?
Thanks in advance !
"Important: In the second half of 2021, new apps will be required to
publish with the Android App Bundle on Google Play. New apps larger
than 150 MB must use either Play Feature Delivery or Play Asset
Delivery".
Taken from
https://developer.android.com/guide/app-bundle
So the question is, is it mandatory to upload only aab files to PlayStore or normal apk file can also be updated
Normal APK can also be uploaded / updated. This is just a warning and not an error message. Google Play will still allow you to continue
If aab file has to be uploaded, then how to sign the aab file before
uploading.
In Android Studio, when building signed APK / AAB, it will ask you to export an encrypted key. Take note of the location because you will use this exported key when you upload your AAB. See highlighted in yellow
I referred this Link for Goolge App signing. Is this also required ?
Nope, it's optional. Quoting Google Play Support:
Using app signing by Google Play is optional. You can still upload an APK and manage your own keys instead of using an app bundle. However, if you lose your keystore or it becomes compromised, you won’t be able to update your app without publishing a new app with a new package name. https://support.google.com/googleplay/android-developer/answer/7384423
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 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.
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.
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.