I've got an application (not free) on the Appstore, it was one of my first app. I'd like to update it with a lot of new stuff, graphics etc. Most of these new feature such as collection views are available only from iOS 6, the app targets iOSes >=3.1. I prefer to not mess around with runtime checking.
Since is a paid application I'd like at least that all people with iOS6 could upgrade it for free, and I don't want to screw older versions.
What happens if I submit an upgrade that target only iOS=>6, would older iOSes be notified about the upgrade? could they do the upgrade? will be shown something such as "The upgrade will be available only for iOS>=6"? or it will be notified only with matching devices?
I've read that question (little bit old) and there is a Use Case not clear to me here
Thanks,
Andrea
Related
Is it possible to maintain 2 application versions of the same application at the same time?
When a device gets too old and won't receive any updates from apple, you will stay stuck on the last version supported by your device. When downloading apps from the app store that require a higher version of iOS, it will automatically download the last compatible version from the app store. this is default behavior as stated: https://apple.stackexchange.com/questions/160089/how-does-ios-appstore-handle-multiple-version-targeting-different-version-of-ios/336985#336985
While we will mostly update our latest version, can we still update the 'legacy' versions of the app for older devices? can we still add features to the old versions (eg iOS <11) while adding the same features in our new app?
You can maintain two apps simply by giving them two different bundle ids.
But you probably cannot update the "old" app without recompiling it against the current iOS or prevent a modern user from seeing and downloading the "old" app.
To give an example, if your old app was 32 bit only, a 64 bit user cannot download it. But if you update it, you have to make it 64 bit.
Im developing an SDK and its deployment target is set to 9.0. Im using some API's that are deprecated in iOS 10 and above and others that are deprecated at iOS 13 and above.
My question is what will happen to an app that is consuming my SDK and its deployment target is set to iOS 14? will my SDK be affected? will my methods get properly invoked? will it crash the hosting app? is the behaviour under these circumstances is unclear? or maybe all will run perfectly?
Any light on this would be appreciated, thanks.
First things first, deprecation is the first step in the process of ending the life of an API and Apple is warning the developers that these APIs will be removed in one of the future iOS releases. Nobody knows when except Apple. There is certainly a wisdom in that (e.g security concerns, better API design, etc).
Developing an SDK which uses deprecated APIs is generally considered a dead end. I am sure you have your own reasons, however, anyone who uses your SDK will be asking themselves whether there will be any value or will there be a maintenance overhead.
There are certain issues during the development stage that you should be aware of. If the app developer of an app who uses your SDK sets the deployment target to iOS14, most probably Xcode will flag this up as a warning. It depends on other things such as the development language that you are using, whether it is already compiled etc.
Assuming there is a good reason for you to move forward, there are several scenarios on what could happen.
In Production, the very short answer to your question is, the application will crash if the API is removed in the next OS upgrade by Apple (if the app developer doesn't take any action before it is released). However, long answer is a little bit more complicated than this.
The best case scenario is Apple doesn't remove the API for a very long time e.g UIWebView. I think it has been at least 5 years now since Apple deprecated the framework, and technical you can still build an app with the UIWebView. That means you do not have to do anything (in theory).
However, if the API is removed by the new OS update, there are several scenarios:
The device is eligible for an OS upgrade, THEN the app will most likely keep crashing when the API is called by the app/sdk.
If the device is NOT eligible for an OS upgrade (e.g stuck on iOS 10), the app will still live for a while on these devices until the owner buys a new device (whether the app developers takes action or not). That particular app version should also be available through iCloud purchases/downloads. So customers can re-download that version even if they delete it etc.
For an active app developer, the first scenario shouldn't happen. I would expect them to test the app on the next beta of the OS version and take action if there is an issue e.g ask you to provide an update, or replace your SDK with another one.
The API removal process can be a little bit more informed and Apple might force your hand, but be still gentle. Apple may make it explicit and warn developers that any new apps, or app updates which contain the API will not be accepted to App Store. This ties the app developers hands. They need to make a choice. This warning would be months in advanced and you would put this work into your backlog and plan for it.
The scenario in bullet point 2, on the other hand, may not be obvious at first, and Apple is doing a pretty good job of convincing the customers to buy the latest devices. There is a relative 2 year cycle, so you may not find many customer using older phones which are stuck on older OSs. This may be ignored depending on your significance level.
The app developers may or may not be able to keep the min target of the app. If they are so adamant then most likely their app will not be compatible with the latest devices or Apple may refuse their updates (as above). Then that means it is pretty much the end of life of the app, only used by a handful of customers.
There is also scenario where Apple may also remove the applications from App Store and iCloud download which are not maintained for a certain period of time (this has happened).
At first my first question was: Will I be able to upload the the appStore using an old SDK. Looking at the apple Documentation, and a stack overflow question, I arrived to the conclusion that I can upload my application using an old SDK as long as it's in a reasonable amount of time since the new SDK has been released. I could not find the minimum required SDK for approval though. At that point in my research, I think that I can use an old SDK to submit my application. Am I in the wrong? How long should I expect the current latest Xcode 7 SDK to be supported ?
(I do know we should move to the latest SDK as soon as we can.)
My company is working on several iOS projects, and we are having a big patch soon for one of them (maybe in December). We do not want to introduce new bugs. We understand we must change the SDK, but at this point in time, it would be too much time consuming. Some of us would like to enjoy the latest version of Xcode for some native projects, which brings me to my second question. Right now if we have a bug free application using Xcode X (7), can we expect the same bug free application using Xcode X+1 (8) with the same SDK. Is this safe or would we take a risk?
I have an application whose minimum version has been set to iOS 7.0. This application also uses NSUserDefaults dictionary. This application is using UIAlertView and UIActionSheet extensively (not sure how much Apple non-disclosure covers). Now, with iOS 8.0, these two views have been deprecated and have been replaced by controller UIAlertController. Now, there are two ways that I can see which can help me in updating the app for iOS 8.
Raise the minimum version to iOS 8.0 for the update. This way, the users running iOS 7.0 won't be able to see the update. However, it leads to the following situation :-
However, there is one problematic case, and that comes from upgrades
performed from within iTunes or on a device with a higher version
number that is then synced to iTunes. When the user syncs the older
device with iTunes, iTunes will actually delete the application from
the device because it cannot run the new version currently within
iTunes. I had a couple of users with original iPod touches report this
when I upgraded one of my applications to only support 4.0.
The above comment is present under the accepted answer at the following url :-
Raising minimum iOS Deployment Target Version for App Update
Since, the application is using NSUserDefaults dictionary, the relevant entries in the dictionary would get erased when the application is deleted.
The other option is for me to detect in the code which version is being used and code accordingly using if-else statements. This would enable me to keep the iOS 7.0 as the minimum version and might also help me in deploying the update for iOS 8.0. However, this seems like a lot of work which can potentially lead to bugs.
So, I was wondering which option is better between the above 2 ways ? (This application would only be using Objective-C for now due to some constraints).
The best thing to do from the user's perspective is probably to code using UIAlertView and UIActionSheet even though they're deprecated. Keep your iOS 7 target the same as it's been. Xcode shouldn't give you warnings since you're using the older version as your base target. You won't need to change anything about your code and it should still work well enough.
Once you're ready to switch (perhaps when iOS 9 comes out), I would switch your base target to iOS 8 and update your code to use UIAlertController everywhere. To me, it doesn't make sense to spend time trying to support two different versions if it's just an API deprecation that still allows your code to work how you've written it for years. Saves resources and energy to just update it later.
But it's really up to you and how much you want to support iOS 7. I think it doesn't make sense to drop support until the next version comes out. I always try to support the current and last versions so there are no annoyed customers, but it depends on your own needs.
If you have analytics integrated, check out percentage of iOS 8 adoption once it's been released for the public. If not, it's a great opportunity to add it to find out how up to date your customers are!
A week ago I have submitted an application which supports Blackberry Z10. Yesterday, I finished another version which supports Blackberry Q10 and Blackberry Q5. At the moment, my app on the market is version 3.0 and it only supports Z10.
If I upload a new bundle, the version of the app automatically increase to 4.0. This bundle also only supports Q10 and Q5 as the previous version already supported Z10. In this case, what will happen to Z10 users? Will they receive the update version (4.0), as it is a newer version, although I already set the specific devices to Q10 and Q5?
In the future, if I make some update, how can I manage it?
Cheers,
Disclaimer: I don't develop for BlackBerry 10, but I do for legacy BlackBerry OS versions, and I believe this works the same within the BlackBerry vendor portal (see comment by Peter Strange below confiming).
If I upload a new bundle, the version of the app automatically increase to 4.0.
First of all, this is what the web interface does by default. It auto-increments the major version number (the number to the left of the decimal point). However, the field for version number is editable, so if you don't like the default choice, you can change it. For example, if you would like the new version to be 3.1, or 3.0.1, instead of 4.0, then you can change it manually. Personally, I don't think you should increase major version numbers simply to add a new device, within the same line of OS's.
This bundle also only supports Q10 and Q5 as the previous version already supported Z10. In this case, what will happen to Z10 users?
Z10 users should see no change. If you previously have a version available for Z10, it should still continue to be available. Whenever you upload a new bundle, you should use the web interface to specify which devices that release bundle supports
(alternatively, you can make a zip container of bundles, and use release.xml/devices.txt to specify device support).
So, if the new release only specifies Q10/5 support, that bundle won't be served to Z10 users. Z10 users will still have access to version 3.0.
In the future, if I make some update, how can I manage it?
I would recommend that you only change major version numbers when the functionality of your app significantly changes. Version 3.0 to 4.0 should be a major change, visible to the users. I personally, then use minor version numbers for small changes, that are also visible to users. For example, version 3.0 to 3.1. Finally, the last digit of a version number I reserve for small changes, such as a bug fix that doesn't add new features, but prevents a problem. For example, version 3.0 to 3.0.1.
For a new release that only adds support for a new device, I would probably just change the last digit (e.g. 3.0 to 3.0.1). But, that's your decision.
If you have a new release that only adds support for new devices, then you should be able to only upload a new bundle that specifies support for those new devices, rather than uploading new code for all devices. This way, a Z10 user isn't bothered to install an update when the newest release actually contains nothing new for their device.