I have uploaded an APK to the Google Play store. However, after making it live, I have found an issue in the APK. My current APK version is 1.5 and I want to cancel this APK and reinstate the previous version (1.4) in the store. Is this possible?
Thanks for all your help.
There is no rollback feature.
The only way is to take your good APK (1.4), increase its versionCode (e.g. to 1.6), then re-sign it and re-publish it in a new release.
Related
I have published two versions of my app apks to Google Play Console.(1.3, 1.4)
But later I realised that there is a minor issue in my newest version(1.4) that I have uploaded. So now I need to un-publish the newest version(1.4) and publish the older version(1.3) again.
How can I do that?
This was already answered here:
https://stackoverflow.com/a/29549730
It's not possible. You'll have to rebuild the older state and upload again under a new version number.
Basically I have my first app in beta channel some people download it but I have the doubt if when i launch in production channel those people have to uninstall the beta's apk and install the new one or is a different process to do that?
Thanks in advance
If you promote the APK from beta to production, then they won't have to download it again since it's the same APK (with the same versionCode).
If you upload a new APK with a higher versionCode on the production track, then yes, they would receive an update.
I need to distribute my apps to testers prior to submitting them to the store(s). Nativescript builds an apk file that is easily distributed to Android testers. Is TestFlight the recommended way to distribute iOS apps? And should I use the xcode project file to build the app in Xcode in order to submit it to TestFlight. That method seems counter intuitive.
Yes, ideally you would use TestFlight. It's also a perfect way for you to test your distribution build/signing etc since you would upload the exact same build that will end up on the App Store. In fact, if your testing goes well with your users, you can submit the same build that you've already uploaded for TestFlight to the reviewers for the App Store, you don't even need to upload a new build.
As #Dave Wood mentioned, yes, TestFlight should be the way to go forward as you do not need to re-build the app to submit for review to Apple.
Answer to your next question should I use the xcode project file to build the app in Xcode -
No
You can use the below commands to build and publish app to Apple store.
From the root folder of your app
tns build ios --release --for-device --bundle <Your Provision Profile>
this will show the path where it has created the .ipa file, then
tns publish ios --ipa <.ipa file>
this will ask your Apple ID and App Specific password and will process the actual App based on your appid mentioned in your package.json.
You can change the app version and App name in info.plist inside App Resources->ios folder.
Thanks. I realized this was the answer after I posted the question. I'm new to NativeScript, but not to iOS development. It occurred to me that once the app is uploaded to App Store Connect, I still control the activities of either posting or setting up TestFlight. Thank you.
Well we released an update for our app last month, that set the minSDK to 5.0. We did this because we had a server side change that would break those on below 5.0.
Is there anyway to release another app on Google Play that would only be for user on below 5.0?
If we were to release the 5.0 and below version for a few days and then release the 5.0 and above. Will the 5.0 and below user still see that "slightly newer" below 5.0 release?
Yes. This is known as "multi-APK". See this help page.
You have two options for making sure users get the right APK.
the simplest to understand option is to set maxSdkVersion in the manifest of your pre-5.0 APK, and minSdkVersion in your manifest for the post 5.0 APK.
another option to use version code. Google Play will always deliver the highest version code that is compatible with a user. So if you make sure your pre-5.0 APK always has a lower version code than your post-5.0 APK, then both types of users will get the correct APK.
I can't upload a new version of an APK to Google Play because it would supersede an existing version.
So, how do I retire an existing APK so I can upload a new one?
This is the error message that I get...
So, I have to remove version four. But how? The only option I can see to do this is to manually upload the APK to the console at the same time as deactivating the old. In which case, what's the point of the app publisher?
In the Play console you create a release as described here.
In it there are 3 options:
APKs to add
APKs to deactivate
APKs to release
By default your old APK is in the "APKs to deactivate", which is what you refer to as "retire". If it is giving you this warning it is probably that you have decided to retain it.
The purpose of this is to allow a more complicated "Multi-APK" configuration, where you have different APKs supporting different users, eg one for older phones and one for newer phones. If you don't need it, just put your old APK to be de-activated.
In particular (from the docs here)
In the "Apps to retain" section,
view details about app bundles or APKs from your previous release that will continue to be served to users.
Clicking Deactivate moves an artifact to the list of app bundles or APKs that will no longer be served to users.
In the "apps to deactivate" section,
In this section, view details about app bundles or APKs from your previous release that will no longer be served to users.
Clicking Retain moves an artifact to the list of app bundles or APKs that will continue to be served to users.
It sounds like you need to click Deactivate by one of the apps in your retain section.