I'm developing an application which will have quick version updates.
For example, today I uploaded an app with version 1.0, I made changes for the next release and after 2 days I want to upload it with version 1.1. But it seems very hard to me to always upload the new versions with changes.
So my idea is to check for version(with a service call for version check) if the version is below the latest version, I want to show an alert with a mandatory update or an optional update.
The problem is, how can I manually download the latest changes within the app without navigating to the app store.
Is it possible or is there any way to do this.
Thanks in advance.
Related
Apple AppStore makes in possible for users who don't or can't run the minimum required version iOS by an app to download an older version of the app that's compatible with their device (if available).
The user is presented a question:
The current version requires iOS 15.0 or later, but you can download the last compatible version.
This is great, but I'm in an awkward situation that I need to issue a patch to my 'old' users who are running an older version of the app because of a third-party API change.
I don't want to patch the old version and just submit it as a new one to the AppStore because that would effectively downgrade all of my 'new' users who are running a much newer version of the app and just happen to click the 'Update' button in the meantime.
Is there a solution for this problem?
I've just published an app on Apple's store and I'm wondering about having multiple versions of the same app for testing on TestFlight. Of course dev doesn't stop when publishing... from now on I'll have to update the app store version (v1.0.0) with bug fixes (v1.0.1, v1.0.2, ...) and before doing so I'd like to check them in test flight to ensure the fix was appropriate.
My problem is that I'm already starting to develop the next version with further functionalities of the app which will become v1.1
So ideally I'd like to have my app available both for my bug fixes, for instance v1.0.2 and also my next version v1.1.0 (this will include all bug fixes made to the store version and also many new features, refactors, redesign, etc)
I know that if I build and upload to the apple store connect a build with v1.1.0 (next version) I won't be able to upload one for a built with a bug fix on the current app store version (v1.0.2) since this version would be lower than the one I uploaded (next version)
Is there a way to accomplish this? I've read this article https://savvyapps.com/blog/using-testflight-to-distribute-multiple-versions-ios-app which solution is to create extra applications in iTunes with different app ids and bind them to different certificates. But what will happen when the next release is ready to be in the store? I would have to release it and then disable the previous one? How may this affect my users? Will they have to re-install a new app rather than updating it?
I really need to start testing and checking the next release of my app in TestFlight and also support the current one with updates if something pops up. Thanks in advance!
I am able to upload multiple versions of the app to TestFlight. Each upload requires a higher version/build number, but you can switch the TestFlight test version between them as need be for testing.
Once I submit a particular build for release, however, I seem to lose the TestFlight access to the old builds.
In short, you can have many builds available in TestFlight, but once you submit the app for release, you have to start over making builds for TestFlight.
You keep talking about numbers like v1.0.1. That looks like a public-facing version string, with a major, minor, and patch number.
But that is not what TestFlight cares about. Well, it cares to some extent. But all TestFlight really cares about is that every new build you upload has a new build number. This is just an integer which you simply increment every time you submit a new build.
So you could have v1.0.1(23) on the App Store, and then on TestFlight you could upload v1.0.2(24) which starts moving forward toward version 1.0.2, but also upload v1.0.2(25) which is actually an attempt at a prospective version 1.1. TestFlight doesn't know or care what these different builds signify. They can all exist simultaneously on TestFlight. Keeping them all straight and on their individual trajectories is up to you.
I have a React Native app in the Apple App Store and recently released a new version. I'm getting reports from existing users who already had the previous version of the app installed that their new install is either partially upgrading or not upgrading at all, even though the app store is showing that the new version is installed.
In the app store they are seeing the new version number. They do the upgrade and then see the Open button, indicating that the upgrade is complete.
Some users are reporting that they see the old versions splash screen and then the new version of the app is there. Others are reporting that the old app hasn't changed at all even though, as I mentioned, the app store is showing the new one is installed. If the user deletes the app and installs it clean then it is always properly installing the new version.
Any idea why this may be happening? I would think that an upgrade scenario would be simply keeping the app data around while removing the old binary and replacing with the new binary.
I did switch the splash screen loading method from Launch Screen in the old version to Launch Images in the new one. And I have had many javascript changes and new native libraries installed. And my redux store has some different data structures. But I don't know why any of these things would result in a partial upgrade.
i have uploaded my app on iTunes but it have some errors now i need to upload newer version of the app and force user to update to that version. How can i do this .. I need help on this..Thanks in advance
If you already uploaded you app, this is not possible. You need to implement this yourself. Basically check against some server where you get the current version from. If the app version doesn't match this one, just show an error message.
In iTunesConnect you can specify that the old version will appear in iCloud, see this doc: https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ReplacingYourAppWithANewVersion.html#//apple_ref/doc/uid/TP40011225-CH14-SW3
But note that this doesn't affect people who have already downloaded your app.
Currently when making a new release android customers are given a notification that a new version of the is available for download.
I have searched for solutions on here (stackoverflow) but the only related answers are for apps developed in xcode.
How can I notify customers when releasing a new version of the app to itunes?
You could store the current app version in your database and use appVersion plugin to get the installed version on the device. Then you can compare the versions (on start-up e.g.) and notify the user somehow that there is a new version available. You can even provide add link to your app in App Store.
I'm using this plugin: https://github.com/WellBload/cordova-plugin-app-version/blob/4234061/README.md
It does require some maintenance because you have to update your database every time the update has been released. The choice is yours.