Swift 4 Upgrade Error: ‘init(colorLiteralRed:green:blue:alpha:)’ is unavailable

Wed, 24 Jan 2018 12:35:04 +0000

I upgraded a project to Swift 4 today and hit a compiler error:

‘init(colorLiteralRed:green:blue:alpha:)’ is unavailable: This initializer is only meant to be used by color literals.

The fix is pretty simple: Don’t use that initializer! (thank you, Captain Obvious!)

The correct initializer to use for specifying a red, green, blue, and alpha to get a UIColor instance in Swift 4 is:

UIColor(red:green:blue:alpha:)

So essentially, just replace colorLiteralRed:, and replace it with just red:, and the compiler error will go away. Here’s an example of how to call it:

let color = UIColor(red: 204/255, green: 204/255, blue: 204/255, alpha: 1.0)

Swift UIColor Extension – Create using RGB Values (Not %)

Fri, 26 Jun 2015 03:11:48 +0000

I’ll say it up front – I’m not a great designer. What tends to happen with me and projects is that I end up saving all-things color until the end of a project. You know… the old procrastinator’s motto: “If you don’t get it done today and tomorrow doesn’t come, then you ain’t gotta do it!”

So the other day came and I had to “do color”…

Thankfully, a buddy of mine has good skills in the area, and gave me a color palette to use. Score!

Working with colors

I decided it might be nice to go ahead and encapsulate my color scheme in code and set the various tints and font colors and navigation bar backgrounds to their appropriate values in code.

This seemed like a really nice way to keep all the color stuff in once place, so that if I ever needed to change things, I’d be able to do it in one spot, and the whole app would just magically take on the adjustments.

Inevitably, I’d need to create myself some UIColor instances.

Baffled

For those of us who spend a lot of time designing in the Storyboard, as opposed to creating views and layouts directly in code, coming up against the UIColor API when you haven’t in a while can be…well…baffling. Not because it’s “hard” but because it’s not as intuitive as it looks on first-sight. Here’s what I mean…

My color-adept friend had given me some hex color values. Looking at UIColor of course, there’s no initializer or class function to create a color with such a value. No worries, though – there are plenty of converters out there!

So I got my red, green, and blue values all in order and did the thing that seemed most obvious: I supplied UIColor‘s init method with those values, verbatim:

let primaryColor = UIColor(red: 39.0, green: 44.0, blue: 79.0, alpha: 1.0)

And then I realized that I hit the same “gotcha” that I had before. UIColor takes a percentage of red, green, and blue, not the value of red, green, and blue. I needed to divide the values by 255.0 each in order to obtain a value between 0 and 1 as the initializer requires. Sure, this is in the documentation:

The red component of the color object, specified as a value from 0.0 to 1.0.

Similar instructions appear for green, blue, and alpha.

It’s easy enough to fix, but man – that sure seems like an easy-to-fall-for mistake if you’re coming to this API after spending time away from it, or if you’re brand new to iOS development.

UIColor extension

Having to divide the RGB values by 255.0 every time was just annoying enough that I created a UIColor extension to help me be able to do the intuitive thing and just supply the RGB values verbatim, like I’d done to begin with. Here it is for your enjoyment:

1extension UIColor {
2    static func colorWithRedValue(#redValue: CGFloat, greenValue: CGFloat, blueValue: CGFloat, alpha: CGFloat) -> UIColor {
3        return UIColor(red: redValue/255.0, green: greenValue/255.0, blue: blueValue/255.0, alpha: alpha)
4    }
5}

Wrapping up