Why Error handling (try, catch, throw) in iOS Swift? - Purpose & Use Cases

The Big Idea

What if your app could catch mistakes before they cause crashes and keep users happy?

The Scenario

Imagine you are building an app that downloads photos from the internet. Without error handling, if the internet is slow or the photo link is broken, your app might just crash or freeze without telling the user what went wrong.

The Problem

Manually checking every step for problems is slow and easy to forget. If you miss a check, your app can crash unexpectedly. It's like walking blindfolded on a rocky path -- you might trip and fall without warning.

The Solution

Using try, catch, throw lets your app safely test risky actions and gracefully handle problems. It's like having a safety net that catches errors and lets you decide how to respond, keeping your app smooth and user-friendly.

Before vs After

✗ Before

let data = downloadPhoto(url)
// What if download fails? No clear way to handle it

✓ After

do {
  let data = try downloadPhoto(url)
} catch {
  print("Oops, something went wrong!")
}

What It Enables

This lets your app stay strong and responsive, even when unexpected problems happen behind the scenes.

Real Life Example

Think about a banking app: if a transfer fails, error handling lets the app show a clear message instead of freezing or losing your money.

Key Takeaways

Error handling prevents app crashes by managing unexpected problems.

Try, catch, and throw let you test risky code and respond safely.

This makes apps more reliable and user-friendly.

Practice

1. What does the try keyword do in Swift error handling?

easy

A. It catches an error thrown by a function.

B. It calls a function that might throw an error and requires handling.

C. It defines a new error type.

D. It throws an error manually.

Solution

1. Step 1: Understand the role of try

   The try keyword is used before calling a function that can throw an error, signaling that error handling is needed.

2. Step 2: Differentiate from other keywords

   catch handles errors, throw raises errors, and defining errors uses enum or struct.

3. Final Answer:

   It calls a function that might throw an error and requires handling. -> Option B

4. Quick Check:

   try calls throwing functions [OK]

Hint: Remember: try calls, catch handles, throw creates errors [OK]

Common Mistakes:

• Confusing try with catch or throw keywords
• Thinking try itself catches errors
• Using try without a throwing function

2. Which of the following is the correct syntax to catch an error in Swift?

easy

A. do { try someFunction() } catch { print("Error") }

B. try { someFunction() } catch { print("Error") }

C. catch { try someFunction() }

D. do catch { try someFunction() }

Solution

1. Step 1: Recall the correct do-catch syntax

   In Swift, error handling uses do { try ... } catch { ... } blocks to catch errors.

2. Step 2: Identify the correct option

   do { try someFunction() } catch { print("Error") } correctly wraps the try call inside a do block followed by a catch block.

3. Final Answer:

   do { try someFunction() } catch { print("Error") } -> Option A

4. Quick Check:

   do-catch syntax = do { try someFunction() } catch { print("Error") } [OK]

Hint: Remember: do { try } catch { } is the pattern [OK]

Common Mistakes:

• Placing try outside do block
• Using catch without do
• Incorrect order of try and catch

3. What will be printed when running this Swift code?

enum FileError: Error { case notFound }
func readFile() throws {
  throw FileError.notFound
}
do {
  try readFile()
  print("File read successfully")
} catch {
  print("Failed to read file")
}

medium

A. Compile error

B. File read successfully

C. No output

D. Failed to read file

Solution

1. Step 1: Analyze the throwing function

   The function readFile() always throws FileError.notFound, so it never completes normally.

2. Step 2: Understand the do-catch behavior

   The try readFile() call throws an error, so control jumps to the catch block, printing "Failed to read file".

3. Final Answer:

   Failed to read file -> Option D

4. Quick Check:

   Thrown error triggers catch block [OK]

Hint: Thrown error skips try block print, runs catch print [OK]

Common Mistakes:

• Assuming code after try runs if error thrown
• Thinking no output if error thrown
• Confusing error throwing with returning

4. Identify the error in this Swift code snippet:

func riskyFunction() throws {
  throw NSError(domain: "Error", code: 1)
}
try riskyFunction()

medium

A. Missing do-catch block to handle the thrown error.

B. The function cannot throw NSError type errors.

C. The throw statement syntax is incorrect.

D. try keyword is not allowed with throwing functions.

Solution

1. Step 1: Check error handling usage

   The code calls a throwing function with try but does not handle errors with do-catch or propagate with try? or try!.

2. Step 2: Confirm syntax correctness

   The throw statement and function declaration are correct; the problem is missing error handling around the call.

3. Final Answer:

   Missing do-catch block to handle the thrown error. -> Option A

4. Quick Check:

   Throwing calls need error handling [OK]

Hint: Always handle errors from throwing functions with do-catch or try? [OK]

Common Mistakes:

• Calling throwing functions without error handling
• Confusing throw syntax with try syntax
• Assuming try alone handles errors

5. You want to write a function loadData() that throws a custom error DataError.invalidFormat if data is bad. Which code correctly defines the error and throws it inside the function?

hard

A. class DataError: Error { case invalidFormat }
func loadData() throws {
throw DataError.invalidFormat
}

B. struct DataError { case invalidFormat }
func loadData() throws {
throw DataError.invalidFormat
}

C. enum DataError: Error { case invalidFormat }
func loadData() throws {
throw DataError.invalidFormat
}

D. enum DataError { case invalidFormat }
func loadData() throws {
throw DataError.invalidFormat
}

Solution

1. Step 1: Define a custom error type conforming to Error

   In Swift, custom errors are usually enums conforming to the Error protocol, like enum DataError: Error.

2. Step 2: Throw the custom error inside the function

   The function loadData() declares throws and throws DataError.invalidFormat correctly.

3. Final Answer:

   enum DataError: Error { case invalidFormat } func loadData() throws { throw DataError.invalidFormat } -> Option C

4. Quick Check:

   Custom errors use enum + Error protocol [OK]

Hint: Use enum conforming to Error for custom errors [OK]

Common Mistakes:

• Not conforming error type to Error protocol
• Using struct or class without Error conformance
• Forgetting throws keyword in function