Skip to main content

Backing multiple iOS versions

A latest iOS version update can cover ~85% of iPhone users which is significant compared to a newly released Android running just ~0.1% of devices. (@StatistaCharts collected on September 2018 - iOS 11 vs Android Pie). If your application matters for the rest ~15% of “genuine” iOS users, then you have to spend extra time to support.

Why does it matters ?

Giving uniform user experience irrespective of iOS version and device factors - will give bonus market space for the sales. Essentially it will boost your revenue and popularity of the application.

Deployment Target vs Base SDK

Before heading to solution, we have to understand Xcode settings for Deployment Target and Base SDK.  A deployment target refers to the oldest version of iOS that is capable of running your project. To change your deployment target, open up your project file in Xcode and check the setting under Build Settings -> Deployment.
Base SDK refers to the newest version of iOS that is capable of running your app. To check which base SDK you are building your app against, simply open your project file in Xcode and check the setting under Build Settings -> Architecture Make sure you selected ‘Latest iOS’ from the dropdown list, So you don’t have to worry about updating your base SDK when Apple releases a new version of iOS.

How to shine the aged iOS version ?

1. Unsupported Frameworks :
Linking against a framework that doesn’t exist in your deployment target will just cause the dynamic linker to crash your app. To solve this, you mark unsupported frameworks as 'Optional' in your project settings.

2. Unsupported Classes
Look for Sometimes you want to use a class that exists in your base SDK, but not in your deployment target. For instance UIBlurEffect introduced in iOS 8.0. To support iOS 7.0, simply handle with the condition :
if NSClassFromString("UIBlurEffect") {
    let blur = UIBlurEffect(...)
    //use ‘blur’ for rest of the code
}
else {
   //Find alternative class that gives blur effect
 }
NSClassFromString returns ‘nil’ if the specified class doesn’t exists in the running iOS version or else it will return the class name.

 3. Unsupported Methods.
Similar to unsupported classes, you might face few methods that exists in your base SDK, but not in your deployment target. This time you can use 'respondsToSelector(_:)' API - which will return Boolean value 'true' if the specified method exists. For instance, Car class instance will call autoPilot if 'autoPilot' method exists - else it uses 'manualDrive'.
var car = Vehicle()
if car.responds(to:"autoPilot") {
  car.autoPilot()
}
else {
  car.manualDrive()
}


4. Explicit iOS Version Checks  - Availability attribute
We can check current running version of iOS as -
var systemVersion = UIDevice.current.systemVersion
With the help of system version we can bypass unsupported Classes, Structs, Enums, Enum Cases, Methods and Functions. But.. There is a better approach.
 '@available' attributes can be placed directly above any declaration in your code, other than a stored variable. For instance :
if #available(iOS 9.0, *) {
// use the feature only available in iOS 9
// for ex. UIStackView }
else {
// or use some work around
}

For further reference
medium.com
raywenderlich.com





Popular posts from this blog

Animating label text update - choosing a better way

Recently I published a countdown app .  At one point of development - I have to show a timer on a UILabel which ticks on each seconds. As usual I started  setting text to a label object - self .timerLabel.text = someString Easy piece of cake right !?   But wait ... it won't take much user attention when timer ticks on every seconds. So I decided to make use of a simple animation while label gets text update. I found there are dozens of ways to animate a label. In this short article, I listed 3 best way you can animate text on a label. ( Spoiler Alert 👀- I decided to go with 3rd option)  1. Fade In - Fade out animation : CATransition class has got transition type `fade`. With timing function of CATransition - I was able to see the below result. let animation: CATransition = CATransition () animation.timingFunction = CAMediaTimingFunction (name: CAMediaTimingFunctionName .easeInEaseOut) animation.type = CATransitionType .fade animation.subtype = C...

Prevent Navigationbar or Tabbar overlapping Subview - solved for Card view

Recently, I started with a Card view added as a subview of UIView in a view-controller. When a view controller created along subviews, it tends to use entire screen bounds and also slips behind Tab bar or Navigation bar. In my current situation, it's second case. Casually new iOS developers will write a patch by additional value for coordinate y and subtracting bar height from its size. A lot of them posted in SO threads too : How to prevent UINavigationBar from covering top of view? View got hidden below UINavigationBar iOS 7 Navigation Bar covers some part of view at Top So, how I got solved ? self.edgesForExtendedLayout = [] This  will avoid all subviews in a view controller get behind any bars. Read full apple  documentation on here. Full Source code below :  //Simple view controller where its view layed-out as a card. class WidgetCardViewController : UIViewController { var containerView = UIView () //MARK:- View Controller Life Cyc...

Printing Staircase Pattern : Swift coding challenge

In this post, we can try interesting pattern printing challenge in Swift. The problem statement goes like this " Print a staircase of given size 'n'. Make sure that its base and height are both equal to n, and the image is drawn only using `#` symbols and spaces. The last line is not preceded by any spaces." Expected Output : # ## ### #### ##### ###### Working solution: func makePatternOf ( _ size : Int ) { var str = "" // 1 for index in ( 0 ..< size ) { let stop = size -index-1; // 2 for _ in 0 ..< stop { str. append ( " " ) ; } // 3 for _ in 0 .. . index { str. append ( "#" ) ; } print ( str ) str = "" } } makePatternOf ( 6 ) Loop to visit every row of stair case. Loop for appe...

Implementing autocompletion OTP field in iOS

Long waiting is over. !!  iOS 12 brings Autofill for OTP text field which is close to Android provided a decade back. Previously in iOS we used to toggle between OTP text screen and message inbox.  Which was hard to remember and time consuming resulting a bad user experience. Personally, I have been asked from the client/customer couple of times to implement autocompletion for OTP field and took me a lot of time to convey that it is not possible in iOS. Why Autofill was not possible previously?  We all know that Apple gives at most care for user privacy. When we see iOS architecture, each individual app is like a separate island. There is no inter-app bridge between apps (exception for Keychain and URLSchemes APIs which gives very limited scope). Thus we cannot read message content from inbox. Where to start Autofilling? First of all, the target SMS need to have the OTP Code with prefix string "Code" or "Passcode"on its message content. Beware of OTP c...

UICollectionViewCell shows with wrong size on First time - Solved

We commonly use Collection view where its cell size calculated run time. The flow layout delegate is responsible to return individual cell sizes. BUT in most of the cases, delegate method `collectionView: layout sizeForItem:` expects cell size too early. Before generating actual cell size. extension YourViewController : UICollectionViewDelegateFlowLayout { func collectionView ( _ collectionView: UICollectionView, layout collectionViewLayout: UICollectionViewLayout, sizeForItemAt indexPath: IndexPath) -> CGSize { return CGSize (width: externalWidth, height: externalHeight) } } For instance, if a cell size depends on external view and its frame is not yet ready - results with wrong (or outdated) cell size. Typically happens for the first time view controller laid out all views. You can find similar queries in StackOverflow community : Collection view sizeForItemNotWorking UICollectionViewCell content wrong size on first load How to refresh UICollec...