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.
Related
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
I lost the keystore of my Android app. The app was only published in the Alpha Track for a limited list of testers. No Production Track yet.
I contacted Google about it and they told me to
unpublish the app, which I did
change the package name, which I did in the Android manifest
In the Alpha track I still see the previous release with the status of fully implemented
After that I did the following
Clicked on Make Release
Clicked on Upload APK
Uploaded the new APK
RESULT: I get the error that I uploaded an APK that has been signed with another certificate than previous APKs.
What am I missing here? Do I need to change the package name somewhere else as well? Or do I also have to change the android:versionCode and android:versionName?
Thanks!
Ok, I found the way to solve this. For anyone who has the same question, here are the steps that you should follow:
Unpublish the app in the Google Play Console
In the store listing tab, change the name of your app
Create a new app
Re-use the same name for that new app by putting it in the store listing form
That's it. Hopefully you don't have too many (or none) users who already downloaded your app. Otherwise you'll have to let them know about the change.
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.
Sorry, I was a noob on this field. I use an eclipse to make an android app, and I need an answer about how to update the version of my app. Also, does the update replace everything in the project?
You go to the Google Play Developer Console just like the first time, and upload a new .apk.
This means you're completely replacing the app, but not anything else you've set up in the console, such as preview images and description text.
All you have to do is publish your newly built APK in your Android Developer Console. The old APK is replaced with the new one. Remember to update the android:versionCode element in your manifest. You have to increment it by +1. This way when your users open the Play Store app on their devices, they will receive a notification that the application needs to be updated.
Go to Developer console page and upload the new .apk file.
Make sure in the new apk, android:versionCode (in Manifest file) is bumped. Otherwise you will get an error.
In the Developer console page both versions will be available. You can choose which app version you want in the field.
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.