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.
Related
I think this is not required, at my personal experience only new iOS specific features in my application will require a new release, but a personal client is asking me to confirm this.
With every new XCode release, do I have to rebuild and publish my application in order to make it available at the AppStore of new iOS Release?
If there is any official documentation that proves this will be appreciated!
You do not need to re-publish. Apps remain in the App Store until the developer pulls it (or very rarely, Apple pulls it due to policy violations).
There is likely not any documentation that explicitly states this, but consider a scenario where somebody gets the new iPhone 13 and opts to restore it from iCloud. Data is pulled from iCloud, but apps are restored by re-installing them from the App Store. If apps disappeared from the App Store because they haven't been re-compiled, then anybody who upgraded their phone would discover that a large number of their apps had disappeared.
Anecdotally, my company has apps in the App Store that haven't seen a new submission in over 2 years (since iOS 12). Those apps are still in the store.
You can test your iOS app using the new Xcode 13 and if you got some bug using the new iOS SDK, you can fix it and submit a new version to App Store using the new Xcode.
Its prudent to test your apps on each new OS (preferably before the public release) but in most cases no new release is necessary. Over time you may want to update your app to take advantage of new features or to better support new devices. No app will never last forever but you will likely be able to go some time before having to update.
I have an app up on the apple store written with Ionic v1, Cordova, and AngularJS. It's been up there for a few years now. We are planning a few more releases in the upcoming months. I got this email from the Ionic Team:
Hi Aubrey,
In just over one week’s time, Apple will begin rejecting new apps using UIWebView. We wanted to reach out with details on how to update your Ionic apps.
If you receive an email from Apple after uploading an app binary to the App Store, you’ll need to update the app. The email reads something like this:
We identified one or more issues with a recent delivery for your app, [App Name & version number]. Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90809: Deprecated API Usage – Apple will stop accepting submissions of apps that use UIWebView APIs. See https://developer.apple.com/documentation/uikit/uiwebview for more information.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.
You can find complete details including upgrade instructions on the Ionic blog, but here’s the summary:
Using Cordova? Update to cordova-ios 5.1.0 and above, install the WKWebView plugin, and update each Cordova plugin to the latest version.
Using Capacitor? Update to the latest version then sync the project.
Submit a new version of your app before the deadline to ensure that it has been updated correctly.
If you're an Ionic Enterprise customer, your Customer Success Manager should already be in touch. If you're not a customer and would like to learn more about Enterprise Support options, please reach out here for extra assistance. Our Enterprise Support team is available and able to help. We've already helped a number of our customers navigate this change quickly & easily.
Cheers,
The Ionic Team
The email says that they will reject new apps of they are using UIWebView.
Does this also mean that my future releases will be impacted? Will my next release of an existing app be rejected for using UIWebView?
This link provides the answer to both of your questions.
The bottom line: It’s time to update your apps! Apple will only accept submissions of Ionic-based iOS apps that contain references to UIWebView until April 2020 (new apps) and December 2020 (existing apps). To meet the new requirement, simply update to the latest version of Capacitor. If you’re using Cordova, see below.
- From link provided!
I have installed ordova-ios#5.1.1 and using plugins which may have some UIWebView references such as google-plus, facebook4 and social sharing.
Also I've added the right configuration to config.xml but still failed to successfully upload to App Store. They keep rejecting my first app and now my build number is 1.0.21 !!! 21 Tries I've made but still failing.
We have a browser application and this application is using by different clients. Each client is using separate database and service. Regularly(quarterly) we are releasing the upgrade with enhanced features. But some of the clients may not upgrade to the latest. So different clients are using different versions of our product. There is no issue with this because each clients are using their own Database and service. Recently we build up a iOS app for the same application. In app store we can upload only the latest version of our app, how the clients in lower version can install respective version of their app? Latest version app may not work with lower version of service and Database
Different clients needs to install different versions of same app from app store.
In App Store Connect (where you manage your apps in the App Store), you can choose which versions you want to remain in the App Store after you release a new version. The purpose of this is to allow an older version to be downloaded in case the user have an older device or iOS version that don't support the new app version. - So I guess this feature is not really helping in your case.
I would suggest you make the same version for everyone, and then within the App (I assume your clients have a login) based on their user selects what you want to present them. - Connecting to their old database and deactivating the new features as an example. This will also give you the opportunity to showcase that there is new features which they may want to opt-in on.
You can release a completely new app for each version. Ex. YourApp 1.0, YourApp 2.0 (This is not uncommon, but it's usually more if the same app is radically changed/improved, and you want the old version to remain for some time until you retire it completely).
Hope this clarifies a bit :)
I wonder if there is any way to distribute different versions of same app (same means same bundle id, same account) in Apple Appstore.
Lets say, I want to distribute, MyApp (com.stackoverflow.myapp) version v1.2 but there is already a version v1.1 open to public. Is it possible to keep both version open for public. And fixing issues and release different sub version like, v1.1.2 and v1.2.2.
As far as I know with single bundle its not possible. But still I am curious if there is any workaround.
When you release a new version on to the app store, you can now select an option for a "phased release", where the update is shown to current users incrementally over a 7 day period, but at the end of that seven day period the updated version is available to everyone. Also, new users will get the latest release when they install from the App Store.
You cannot maintain two "active" releases on the store.
If you want to test a new version or new features with a limited set of users then TestFlight may be an appropriate tool.
You can use whatever versioning system you want (such as semantic versioning), but you can't distribute multiple versions of an app at a time without uploading them to the App Store as 2 entirely different apps
I have pushed a version of my beta app to the itunes connect beta app service. I have gone through the beta app approval process, and have been accepted. I sent invites to a bunch of external users. I have pushed another version/build of my application. Not all of my external users have accepted the initial invitation for the application. I have had to disable the old version before I could push the new one into the approval process, which does not allow the previously invited users (ones that had not accepted ) to get the previous version or even see the app as available. I did change the version (from 0.1.3 to 0.1.4) if I only changed the build number instead of the version, would my previous external users be able to access the previous build while in the approval process for the new build?
Apple says that only one of the versions can be enabled for TestFlight beta testing.
If you upload a newer version, then you need do disable the old version of you app. Then only you can share new version.
If you want the old version back, then you need to disable new version and enable old version.
In short, only one version of your app will be active.