Android private key issues. - android

i developed a app in android and released a first version. but now i lost my previous (private key)debug.keystore . Now im going to release a second version with a different private key. but this second version didn't install in phone. how can i resolve this problem? thanks in advance.

You will have to uninstall the old version and then install the new one, as Android doesn't allow updates to be installed if they have a different signature.
Additionally, all of your users will have to do the same, and App stores like Google Play won't allow you to use an update signed with a different key. You will have to publish your app again under a different package name.

Just change your Package Name and change that in androidManifest file also and Upload with new KeyStore. No other way. Because google won't allow you to upload another application having same Package name.

Related

Fix for "You need to use a different package name" in Google Play?

I'm attempting to upload a build of an Android app to Google Play. I created a new keystore and signed it, but I get this error "You need to use a different package name" when I try to upload it.
I suspect that what happened is that another member of my team did this already but failed to commit their keystore file to version control. The app has never been published before, it is a new app.
I need a quick fix for this -- I won't be able to reach the team member who may have done this for several days. I tried removing the build that had been uploaded, but that didn't help.
Can I delete the entire app from Google Play and start over?
Can I change the package name? I've heard that this will work, but I'm not really sure what it entails. Do I have to actually change the package name of every class in my source code?
Thanks,
Frank
You can delete the application in the following cases
- Published apps or games that haven't been installed on any devices
- Published apps or games that no users are entitled to re-install
from here
also google does not allow uploading an app with a different signature and the same package name. What you can do now is to change the entire package name and this can be done easily in Android studio
More details
https://support.google.com/googleplay/android-developer/answer/9023647

Uploading a new APK after unpublishing older app

There is an app created and was published on Google Play store. Then it was not getting updated because of missing keystore. So the exiting app was unpublished and a new apk was created with new package name and version number.
Then, even if the new signed apk was created with newer version code and package name, still an error is appearing "you should either add a new apk or deactivate an existing apk to create a new release".
Can someone help out ? Is anything missed in the process ?
You can only update the existing Apk of an unpublished app with the new version code, in google play console you cannot add an Apk with a different package name.
You can add Apk having the same package name and keystore as previously. you can also see this document for further details.
https://support.google.com/googleplay/android-developer/answer/7159011?hl=en
From my point of knowledge I think google play store doesn't support changing the apk for the same project .You should create another app project in play console for the new apk and add it to release.
I'am sure that you have uploaded the app and filled the content rating. Then you should have to go to edit release and create your release. Re uploading was your problem.Or post the error image to help you more
As many others have answered I will repeat, but try to repeat more clearly.
Every app has a package name sometimes called an application id. It's the string like com.google.android.gm. As far as Google Play is concerned, it doesn't care what you do in your project in Android Studio, or Unity or any other development platform. If the app has the same package name, it is the same app. If it has a different package name, it is a different app.
You say you are trying to create a new release with a different package name. This can't be done. As far as Google is concerned, you are creating a brand new app.
Have you uploaded your APK with your new package name? If you have, can you provide a screenshot? Then people might be able to more clearly see what the problem is.
In my case, I also changed the name of the package via Refractor in Android Studio. I wanted to upload the same app with a new package. And it was still giving me the error that the package already exists, so I had to change the applicationId in build.grade App:module.
After this, it does not replace the old app on phone. Instead, it creates a new one, also Playstore uploaded the app.

Android app releases issue

Currently I have a hybrid app in the play store and recently I have developed a native app for that, by improving and adding more functions.
So I would like to roll out that as next update
I have following issues in mind:
Do I have to sign this using the new app with same key-store file?
Do I have to use same package name?
Will changing version number be enough?
After little search I found out the procedure to release an app by
Google but it doesn't address my doubts so can someone explain the procedure to how to release the app and clear my doubts.
Just change the version number to +1 and use same package google play store will take this apk .but you have to declare target version and compiled version same or updated.
If you have same key and package name is same play store will take your Apk.
update your version number and put target and build version same or latest.
Please find my answers below:
do i have to sign this using the new app with same key-store file ?
Yes, if you want to publish update of existing app, won't allow you to publish if different key-store used
do i have to use same package name ?
Yes, if you want to publish update of existing app, will be considered new app otherwise
will changing version number enough ?
Yes but version number should be greater than the version number of existing app

Reupload the apk with a different package name after publishing the app on google play - Ionic

I have published an Ionic app to google play and it's working fine. But, I had to make a change to its package name and now when I try to reupload it, it says the package name should be the same as previous version.
Your APK needs to have the package name com.mypackagename.
You need to use a different version code for your APK because you already have one with version code 'myversioncode'.
I'm happy to take down the whole app and upload the newer version but I don't think google would allow me to do it.
How can I work around this? Should I update the version code as well?
Think of the packagename as kind of a unique id for you app. If you look closely, a playstore-link is always a combination of the url and your packagename, like https://play.google.com/store/apps/details?id=COM.YOUR.PACKAGENAME.
When you create a new app project in the developer console, and upload the first apk, this project is permanently linked to the given package name.
I think the reason for this is androids app update scheme. By comparing the package names it checkts if you have a certain app installed, and if the installed version has a lower versioncode then the one available, it detects that you could update it.
So basically you have two options:
A) keep the old package name and do a regular update
B) change the package name and create a new app project in the developer console. publish your "new" app. Keep in mind that this app starts at zero, so your previous downloads and ratings are gone
You can not update the same app with different package name instead disable the previous app and upload new app with a new package name.

Changing package to an android application published

I am working in the 1.1 version of an app which first version (1.0) was made for a consulting company. That company published the app in Play using a package like com.thatcompany.mycompany. Our problem is that currently we want to deliver the 1.1 version as com.mycompany. As long as I know if we try to do that (change the package) our app don't be perceived for Play market as an upgrade of the last version but as a different application. Does exist some way to do package change and still being the same application on Play in order to the user be encouraged to update? Thanks.
As far as i know, you can't.
Your app is signed.
Signing uses your keystore and the package name.
If you change any of these the Play store will recognize it as a different application.
I believe it has something to do with security.
You cannot.
An application is uniquely identified in the market place with its package name, therefore you cannot change the package name anymore (the same goes with the key).
You cannot change either the package name or keystore used to sign your app.
To confirm what everyone else says, you CANNOT modify your package once your app has been published.

Categories

Resources