This might seem like a strange topic – after all, why would anyone want their program to crash? Well, the answer is two-fold.
First, if something has gone wrong that leaves your program in an unsafe state, continuing might mean corrupting user data.
Second, if you're debugging your app (i.e., it's still in development), having your app refuse to continue if a serious problem is found is a huge advantage and a very common way to spot problems.
Swift lets you force an app crash using the
assert() function. This takes two parameters: a condition to check, and a message to print if the assertion fails. Helpfully, any calls to
assert() are ignored when your app is compiled in release mode (i.e., for the App Store), which means these checks have no impact on your code's final performance.
Here are two examples of
assert() being used:
assert(1 == 1, "Maths failure!") assert(1 == 2, "Maths failure!")
The first one asserts that 1 is equal to 1, which is clearly true, so nothing will happen. The second one asserts that 1 is equal to 2, which is clearly false, so that assertion will fail: your app will halt, and the message "Maths failure!" will be printed out to help you identify the problem.
Because assertions are ignored in release builds, you don't need to worry about running expensive checks in your assertions. For example:
assert(myReallySlowMethod() == false, "The slow method returned false, which is a bad thing!")
In release builds, that code will never be run, so you won't see any performance impact.
Available from iOS 7.0
Did this solution work for you? Please pass it on!
Other people are reading…
About the Swift Knowledge Base
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Love Hacking with Swift?
Get all 40 projects in PDF and HTML: buy the Hacking with Swift book! It contains over 1300 pages of hands-on Swift coding, and will really help boost your iOS career