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.
Related
I'm using google drive api in my app which works fine on both debug and release builds when I install it using .apk file.
But if I publish the same release .apk on playstore and then download it from there I can't sign in to Google.
All I can find regarding the issue is that people aren't using release keystore to generate credentials on Google's developer console, which is not the case for me.
I found a problem:
Check if you have been enrolled in App Signing program under Release Management. If yes, there must be two certificates - upload and App signing.
Copy Sha1 of App Signing certificate and create new OAuth client ID in developer console.
Then go to Firebase Project settings, add copied fingerprint to your app and download google-services.json.
Replace your existing google-services.json in android studio with downloaded one and you are good to go.
I have no idea when or why I enabled this thing. It replaces signing certificate of your uploaded application with the new one.
I have app in google play made from app inventor but i would like to replace the app inventor version into android studio made version. when i upload the .apk to google play it has error because it was a different version. Is there anyone out there have done this successfully?
""""""""
Upload failed
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate.
""""""""
You have to contact Google Play Developer Support reagarding this issue, a developer can not upload an update that has been signed with a different certificate than the previous version.
If Google is not able to resolve the issue you will have to change the package name of the app and upload it again.
I have a publish app on Google Play Store, Now I have made some changes in the application and I want to release the update version.
I have signed the .apk using same keystore, alias and password which I used for first upload.
But the problem is when the new release get published, it does not show 'update' option on the play store.
I am using eclipse.
Any solution?
Thanks in advance.
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.