I want to change package name of an android project/apk so that i can have different version's of an application.
For this i have gone through some stackoverflow' questions for this { link1 , link2}. My project is build with gradle. In these stack's answer's i was not cleared where to change in [roject's build.xml or sdk's build.xml.
Is this possible to change package name with "–rename-manifest-package" and release application on google play store? or i need to do somthing else.
For different version, change version on gradle file and make another apk then release it on google plays store. There is an option on google store it should be release new version or something like that.
However, it is not possible to change current application's package name which is on google play store.
If you cannot do, I'll try to add step by step guide.
EDIT:
At first you need to change your app's version in here which is build.gradle(Module: app)
and then you need to create new signed apk since you want to publish it;
After creating signed apk you need to access your developer account and click APK section first and then upload new version of your application.
Related
I published the wrong update for an app on the play store by the new Play Developer Console.
I need to rollback my update, simply REMOVING it and re-publishing the previous version.
I cannot understand 2 things:
how remove it from the apps versions menu
re-publish the previous one
In previous versions of Google Developer Console this could be possible unpublising the last .apk and enable to production your desired version
but now it can´t be possible.
Note that rollbacks aren’t supported due to the app versioning requirements of the Android platform. If you need to rollback, consider launching a previous APK with a new version number. However, this practice should be used only as a last resort, as users will lose access to new features and your old app may not be forward-compatible with your server changes or data formats, so be sure to run alpha and beta tests of your updates.
You can see the previous releases but you can´t enable again:
You need to create and publish a new release with a consecutive versionCode.
Click on Create Release Like you release a new version, but instead of uploading an apk click "Add From Library", Here you will get all the previous versions of your app, select the version you want to rollback to, then release it after review button.
Just build old app version with new versionCode and old versionName and publish it
Reviving this but for those that are looking for something similar but for Android App Bundles.
As it's not as clear cut as when doing it for .apk.
For .aab's you need to:
unpack the aab (its just a zip file)
decode the AndroidManifest which is a binary proto message with protoc
to decode you will need the .proto file found in the aapt2 tool
alter the version code/version name of the decoded android manifest
encode it again with protoc using the .proto files used in step 2
pack the aab with zip, but be careful not to zip directories and to remove the path prefix that you might add unwillingly
sign the zipped file with your store credentials, using jarsigner
zipalign the signed zipped file
rename the zipped, aligned and signed to the final .aab file
You can find these same steps in the following gist, with some of the work prepared before hand.
https://gist.github.com/Farious/e841ef85a8f4280e4f248ba8037ea2c0
I tried to avoid hardcoding anything and to bulletproof it, but it might not be yet.
in play store classic version , developer console gives an option for Halt rollout . if you will Halt rollout than current version of your app , will be unpublished from play store. Now we can published new version of app.
I generate sign APK and published it successfully.
When I open my Android studio again. My project open and when I click on RUN then this window opens : http://prntscr.com/gn2dt7 Don't know what I write in these fields?
And When I click the fix then this window opens : http://prntscr.com/gn2gvu also don't know what I write in these fields?
Guide Me Please About These Two Files.
Yes you need to run the project once again, before making it as a signed apk change the version name and version number in build.gradle, then go to the playstore where you have published your previous signed apk, at the same place click again to upload apk and publish it. After uploading the apk it shows the update in playstore(it takes some time to show the button update).
You need to update the versionCode (this be always a number and must self-increase) and the versionName in the gradle, after that you only need to build de apk.
Based on my experience it is good to create one key file for every application you will create and you must take care of it .
When you publish new APK file from your project you must change only version number and version name , but you must use existing key filethat you created it before to sign your application's new version .
Inside of the Android Developer Console I would like to have 2 applications, MyAppName and MyAppName-Staging. The only differences between these two apps would be:
The API environment they point (prod vs. staging)
One would be for external Play Store release while the other (MyAppName-Staging) would be intended only for internal users in my company.
Would I be allowed to use the same package/app ID for both of these or would I need to change the package ID for each one? My assumption is I would need to change it, if thats the case can I use the same code base but just change the app ID and rebuild the apk to achieve this?
For additional context I've built this app using Nativescript. So all packaging info is handled through a package.json file and code signing must be done through the CLI. I just want to make sure I can't code sign myself into a situation where I can't release my build to production (the MyAppName build) Thanks for any guidance.
From my experience, Google Play Store doesn't allow 2 apps having the same package name to be published. You would need to either:
Change your package name
or if you want to have the same package name regardless,
Upload your staging app (with the same package name) to the beta channel of your live app then select users to be invited to the beta.
The developer console has the concept of beta builds that you can distribute to list of members or open to play store. You could build with same package name but pointing at different environment and distribute through there.
Then point back to prod when you release your official build.
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
I have hosted an Android application on play store.I have somehow managed to corrupt the source project and I am using Page on eclipse. My question is if I create a new fresh project using same package name, with same name of Application and use same Keystore file for signing the application and just version update. Can I add it to the Play store as an update to the existing hosted application?
Yes, you can.
Below is what Google Developer help section says.
The Package Name of the updated APK need to be the same as the current version.
The Version Code needs to be greater than that current version. Learn more about versioning your applications.
The updated APK needs to be signed with the same signature as the current version.
If you pass these requirement, it doesn't matter how many times you have created the same project. So don't worry!
Yes , You can. If your using same application Id and signing key store and app version code +1
I trying to add an updated version of one of older apps (ver 10.0) but when I try to add the apk to the existing apk list I get the message
The apk must be signed with the same certificates as the prebious version
I'm definitely using the correct keystore as I have only the one in that folder but I then tried to unpublish the old one and add a new application. I update the Version Code to 11 and
the Version Name to 10.1 created a new apk file but when I tried to add as new i then got the message
If you have another application on Google Play with the same package name (org.MyApp). Go to that application and click upgrade
I don't know what to try next as every entry I've seen with this problem tells me I'm using the wrong keystore but I'm not. How can I get around the second error, if I just change the package name it crashes when I download it
It definetely sounds as if you're using the wrong keystore. This needs to be the same you used when you first published the app.
You can't publish a new app with the same package name as google requires every app to have a unique package name.
If you were to publish the original app with the new package name you would have to tell your existing users to move to the new app.