Networking and API Calls in Swift

# CHAPTER 18

Networking and API Calls in Swift #

1. Introduction #

2. Learning Objectives #

• Understand the concept of REST APIs and JSON endpoints.

• Construct safe URL objects in Swift.

• Understand the necessity of Asynchronous programming (async/await).

• Use URLSession.shared.data(from:) to fetch internet data.

• Handle networking errors gracefully using do-catch.

3. What is an API? #

4. Asynchronous Programming (async/await) #

Functions that perform background tasks must be marked with the async keyword.

5. Constructing the Network Request #

import Foundation

class NetworkManager: ObservableObject {
    
    // 1. Mark the function as 'async' and 'throws' (because the internet might fail)
    func fetchRawData() async throws {
        
        // 2. Create a safe URL. (We use guard because a URL with weird spaces can be nil!)
        let urlString = "https://jsonplaceholder.typicode.com/users"
        guard let url = URL(string: urlString) else {
            print("Error: Invalid URL")
            return
        }
        
        print("Starting download...")
        
        // 3. The Network Call! 
        // We 'try' because it might fail. We 'await' because it takes time!
        // URLSession returns a Tuple: The raw (data) and the HTTP (response).
        let (data, response) = try await URLSession.shared.data(from: url)
        
        // 4. Check the HTTP Status Code (200 means OK!)
        guard let httpResponse = response as? HTTPURLResponse, httpResponse.statusCode == 200 else {
            print("Error: Bad Server Response")
            return
        }
        
        // 5. Print the raw binary data size
        print("Successfully downloaded \(data.count) bytes of data!")
    }
}

6. Executing the Request from SwiftUI #

import SwiftUI

struct DownloadView: View {
    @StateObject private var manager = NetworkManager()
    
    var body: some View {
        VStack {
            Text("Network Tester")
                .font(.largeTitle)
            
            Button("Fetch Data") {
                // We MUST wrap async calls inside a Task!
                Task {
                    do {
                        // We try to await the brain's function!
                        try await manager.fetchRawData()
                        print("Complete!")
                    } catch {
                        print("Fatal Error: \(error.localizedDescription)")
                    }
                }
            }
            .buttonStyle(.borderedProminent)
        }
    }
}

7. Main Actor (Thread Safety) #

To fix this, you must force the ViewModel to jump back to the Main Thread before touching the UI. You do this by marking the ViewModel class with @MainActor.

// By adding @MainActor, any UI variables modified by this class are safely updated on the Main Thread!
@MainActor 
class NetworkManager: ObservableObject {
    @Published var isLoading = false
    // ...
}

8. Mini Project: Weather API Skeleton #

@MainActor
class WeatherViewModel: ObservableObject {
    @Published var weatherStatus = "Unknown"
    
    func checkWeather() async {
        guard let url = URL(string: "https://fake-weather-api.com/now") else { return }
        
        do {
            let (data, _) = try await URLSession.shared.data(from: url)
            // Imagine we convert the 'data' into a String here...
            weatherStatus = "Sunny (Downloaded!)" 
        } catch {
            weatherStatus = "Failed to connect to weather satellite."
        }
    }
}

9. Common Mistakes #

• Forgetting App Transport Security (ATS): Apple rigidly forces all network traffic to be encrypted (https://). If you try to fetch data from an old http:// website, Apple will silently block the request to protect the user's security. You must either use HTTPS, or specifically configure an ATS exception in the Info.plist file.

10. Best Practices #

• Never Hardcode URLs in Views: Your UI buttons should never contain string URLs. The View should only know Task { await viewModel.fetch() }. All URL strings, headers, and URLSession logic MUST live securely inside your isolated networking class or ViewModel.

11. Exercises #

1. 1. Write a guard let statement that safely converts the string "https://google.com" into a URL object.

1. 2. Inside a Button action, write a Task block.

12. Coding Challenges #

13. MCQ Quiz with Answers #

14. Interview Questions #

• Q: Explain the necessity of asynchronous programming in mobile architecture. What happens to the user experience if a massive URLSession data download is executed synchronously on the Main Thread?

• Q: Detail the structural components returned by URLSession.shared.data(from: url). Why is validating the HTTPURLResponse status code (e.g., verifying it is 200) a critical step before processing the raw data?

• Q: Describe the architectural purpose of the @MainActor attribute when orchestrating complex background networking tasks within an MVVM architecture.

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #