Error handling for network calls in iOS Swift - Build, Publish & Deploy

Build & Publish - Error handling for network calls

Performance Impact

Proper error handling in network calls helps maintain smooth app performance by avoiding crashes and unresponsive UI. Handling errors gracefully prevents wasted CPU cycles on repeated failed requests and reduces battery drain caused by unnecessary retries. It also ensures the app remains responsive, targeting 60fps frame rate for smooth animations and interactions.

Optimization Tips

Use asynchronous APIs like URLSession with completion handlers or async/await to avoid blocking the main thread. Implement retry logic with exponential backoff to reduce network load. Cache responses when appropriate to minimize network calls. Handle errors specifically (e.g., timeout, no internet) to provide quick user feedback and avoid unnecessary UI updates that can drop frames.

App Size and Startup Time

Error handling code for network calls adds minimal size to the app bundle, typically just a few kilobytes. Using native Swift APIs keeps dependencies small. Proper error handling can improve perceived startup time by preventing the app from hanging on failed network calls during launch.

iOS vs Android Differences

On iOS, use URLSession with Swift's async/await or completion handlers for network calls and error handling. iOS requires apps to handle network errors gracefully to pass App Store review. Android uses OkHttp or Retrofit with Kotlin coroutines or callbacks. Both platforms recommend handling errors like no connectivity or server errors to improve user experience and app stability.

Store Review Guidelines

• Apple App Store requires apps to handle network errors gracefully without crashing (Apple Human Interface Guidelines).
• Provide meaningful error messages or fallback UI to users when network calls fail.
• Do not block the main thread during network calls to avoid app freezes.
• Ensure your app complies with privacy rules when handling network data.

Self-Check Question

Your app takes 5 seconds to load this screen. What's likely wrong?

Answer: The app might be performing synchronous network calls on the main thread or not handling network errors properly, causing delays or hangs. Optimizing with asynchronous calls and proper error handling will improve load time and responsiveness.

Key Result

Proper error handling for network calls in iOS apps ensures smooth UI performance, minimal battery drain, and compliance with App Store guidelines by using asynchronous APIs and providing graceful user feedback on failures.

Practice

1. What is the main purpose of the error parameter in a network call's completion handler in Swift?

easy

A. To update the UI directly from the background thread

B. To store the data returned from the server

C. To specify the URL of the network request

D. To check if the network request failed and handle the failure

Solution

1. Step 1: Understand the role of the error parameter

   The error parameter indicates if something went wrong during the network request. Developers check this parameter to detect failures and respond appropriately, like showing an alert.

2. Final Answer:

   To check if the network request failed and handle the failure -> Option D

3. Quick Check:

   Error parameter = check failure [OK]

Hint: Error parameter signals failure in network calls [OK]

Common Mistakes:

• Confusing error with data parameter
• Trying to update UI directly from background thread
• Ignoring error and assuming success

2. Which of the following is the correct syntax to check for an error in a Swift network call completion handler?

easy

A. if error == nil { print("Error occurred") }

B. if error != nil { print("Error occurred") }

C. if error = nil { print("Error occurred") }

D. if error != false { print("Error occurred") }

Solution

1. Step 1: Recall error checking syntax in Swift

   To check if an error exists, use if error != nil. Using != nil means an error was found, so handle it.

2. Final Answer:

   if error != nil { print("Error occurred") } -> Option B

3. Quick Check:

   Check error with != nil [OK]

Hint: Use 'if error != nil' to detect errors [OK]

Common Mistakes:

• Using assignment '=' instead of comparison '=='
• Checking error == nil to detect error (wrong logic)
• Comparing error to false instead of nil

3. Consider this Swift code snippet for a network call:

URLSession.shared.dataTask(with: url) { data, response, error in
  if let error = error {
    print("Error: \(error.localizedDescription)")
  } else {
    print("Success")
  }
}.resume()

What will be printed if the network request fails due to no internet connection?

medium

A. Error: The Internet connection appears to be offline.

B. No output

C. Success

D. Crash due to unwrapped nil

Solution

1. Step 1: Trace the code on network failure

   The code uses optional binding if let error = error which succeeds when error is not nil, printing the localized description like "The Internet connection appears to be offline." for no internet.

2. Final Answer:

   Error: The Internet connection appears to be offline. -> Option A

3. Quick Check:

   Error prints localizedDescription [OK]

Hint: Error prints message; success prints 'Success' [OK]

Common Mistakes:

• Assuming success prints even on error
• Expecting crash from optional binding
• Ignoring error and printing nothing

4. This Swift code attempts to handle a network error but has a logic error:

URLSession.shared.dataTask(with: url) { data, response, error in
  if error == nil {
    print("No error")
  } else {
    print(error!.localizedDescription)
  }
}.resume()

What is the likely cause of the logic error?

medium

A. Not calling resume() on the data task

B. Force unwrapping error when it is nil

C. Using error == nil instead of error != nil

D. Printing error.localizedDescription without checking error

Solution

1. Step 1: Analyze the logic and best practice

   The code checks if error == nil for success first, then handles error in else (safe unwrap). While functional, best practice is to check if error != nil first to explicitly handle failures before success.

2. Final Answer:

   Using error == nil instead of error != nil -> Option C

3. Quick Check:

   Error check logic reversed [OK]

Hint: Check error != nil to handle errors safely [OK]

Common Mistakes:

• Reversing error check logic
• Force unwrapping error without check
• Not calling resume() on data task

5. You want to update a label's text after a network call completes. Which is the correct way to handle errors and update the UI safely in Swift?

URLSession.shared.dataTask(with: url) { data, response, error in
  // Handle error and update label
}

hard

A. Check if error != nil, then update label text inside DispatchQueue.main.async block

B. Update label text directly inside the completion handler without dispatching

C. Ignore error and update label text on background thread

D. Use try-catch inside the completion handler to update label

Solution

1. Step 1: Handle threading and errors for UI updates

   Completion handlers run on background threads, so dispatch UI updates to main. First check if error != nil to handle failure (e.g., update label with error message), using DispatchQueue.main.async.

2. Final Answer:

   Check if error != nil, then update label text inside DispatchQueue.main.async block -> Option A

3. Quick Check:

   UI updates on main thread after error check [OK]

Hint: Always update UI on main thread after error check [OK]

Common Mistakes:

• Updating UI on background thread causing crashes
• Ignoring error and updating UI blindly
• Using try-catch incorrectly for async callbacks