MainActor for UI updates in iOS Swift - Mini App: Build & Ship

Build: MainActor UI Update Demo

This screen shows a label and a button. When the button is tapped, it simulates a background task that updates the label text safely on the main thread using @MainActor.

Target UI

-------------------------
| MainActor UI Update Demo |
|-----------------------|
|                       |
|  Label: Waiting...     |
|                       |
|  [ Update Label ]      |
|                       |
-------------------------

Display a label with initial text 'Waiting...'

Add a button labeled 'Update Label'

When button is tapped, simulate a 2-second background task

After task completes, update label text to 'Updated on MainActor!' safely on main thread using @MainActor

Starter Code

iOS Swift

import SwiftUI

struct MainActorDemoView: View {
    @State private var labelText = "Waiting..."

    var body: some View {
        VStack(spacing: 20) {
            Text(labelText)
                .font(.title)
            Button("Update Label") {
                // TODO: Call function to update label
            }
        }
        .padding()
    }

    // TODO: Add function to simulate background task and update label
}

struct MainActorDemoView_Previews: PreviewProvider {
    static var previews: some View {
        MainActorDemoView()
    }
}

Task 1

Task 2

Task 3

Solution

iOS Swift

import SwiftUI

struct MainActorDemoView: View {
    @State private var labelText = "Waiting..."

    var body: some View {
        VStack(spacing: 20) {
            Text(labelText)
                .font(.title)
            Button("Update Label") {
                updateLabel()
            }
        }
        .padding()
    }

    func updateLabel() {
        Task {
            try? await Task.sleep(nanoseconds: 2_000_000_000) // 2 seconds
            await MainActor.run {
                labelText = "Updated on MainActor!"
            }
        }
    }
}

struct MainActorDemoView_Previews: PreviewProvider {
    static var previews: some View {
        MainActorDemoView()
    }
}

We use Task to run an asynchronous background task that simulates a 2-second delay using Task.sleep. After the delay, we update the labelText state variable on the main thread by calling await MainActor.run. This ensures the UI update happens safely on the main thread, which is required for SwiftUI views.

The button calls updateLabel() when tapped, triggering the background wait and then the UI update.

Final Result

Completed Screen

-------------------------
| MainActor UI Update Demo |
|-----------------------|
|                       |
|  Label: Waiting...     |
|                       |
|  [ Update Label ]      |
|                       |
-------------------------

User taps 'Update Label' button

Label text stays 'Waiting...' for 2 seconds

After 2 seconds, label text changes to 'Updated on MainActor!'

Stretch Goal

Add a loading spinner that shows while the background task runs and hides after update

💡 Hint

Use a @State Boolean to track loading state and show ProgressView conditionally in the UI

Practice

1. What is the main purpose of using @MainActor in Swift UI code?

easy

A. To ensure UI updates happen on the main thread

B. To run background tasks faster

C. To prevent memory leaks

D. To encrypt user data

Solution

1. Step 1: Understand UI thread requirements

   UI updates must happen on the main thread to avoid crashes and keep the app smooth.

2. Step 2: Role of @MainActor

   @MainActor ensures the annotated code runs on the main thread, making UI updates safe.

3. Final Answer:

   To ensure UI updates happen on the main thread -> Option A

4. Quick Check:

   MainActor = UI updates on main thread [OK]

Hint: MainActor always means UI code runs on main thread [OK]

Common Mistakes:

• Thinking @MainActor speeds up background tasks
• Confusing @MainActor with memory management
• Assuming @MainActor encrypts data

2. Which of the following is the correct way to declare a function that updates UI using MainActor in Swift?

easy

A. func updateUI() { @MainActor /* code */ }

B. func updateUI() @MainActor { /* code */ }

C. func @MainActor updateUI() { /* code */ }

D. @MainActor func updateUI() { /* code */ }

Solution

1. Step 1: Recall correct syntax for @MainActor

   @MainActor is an attribute placed before the function declaration.

2. Step 2: Check each option

   @MainActor func updateUI() { /* code */ } correctly places @MainActor before the function name.

3. Final Answer:

   @MainActor func updateUI() { /* code */ } -> Option D

4. Quick Check:

   @MainActor before func = correct syntax [OK]

Hint: @MainActor goes before func keyword [OK]

Common Mistakes:

• Placing @MainActor after func name
• Putting @MainActor inside function body
• Using @MainActor as a suffix

3. Consider this Swift code snippet:

@MainActor
class ViewModel {
  var count = 0

  func increment() {
    count += 1
  }
}

let vm = ViewModel()
Task {
  await vm.increment()
  print(vm.count)
}

What will be printed?

medium

A. Compilation error

B. 0

C. 1

D. Runtime crash

Solution

1. Step 1: Understand @MainActor on class

   The class ViewModel is marked @MainActor, so its methods and properties are isolated to the main actor.

2. Step 2: Analyze the code

   await vm.increment() correctly increments count. Accessing vm.count inside the Task closure is safe because it's running on the main actor context.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   Accessing @MainActor properties within the actor context is allowed [OK]

Hint: @MainActor properties can be accessed safely within actor context without await [OK]

Common Mistakes:

• Thinking it prints 1 and forgetting await on print(vm.count)
• Expecting runtime crash instead of compile error
• Believing count stays 0 due to async context

4. You have this Swift function:

func updateLabel() {
  label.text = "Hello"
}

When called from a background thread, the app crashes. How can you fix it using MainActor?

medium

A. Add @MainActor before the function declaration

B. Call updateLabel() inside DispatchQueue.global()

C. Remove the function and update label directly

D. Wrap label update inside DispatchQueue.main.async without @MainActor

Solution

1. Step 1: Identify cause of crash

   UI updates must happen on main thread; background thread causes crash.

2. Step 2: Use @MainActor to fix

   Adding @MainActor before function ensures it runs on main thread, preventing crash.

3. Final Answer:

   Add @MainActor before the function declaration -> Option A

4. Quick Check:

   @MainActor fixes UI thread crash [OK]

Hint: Use @MainActor to run UI code on main thread automatically [OK]

Common Mistakes:

• Using global queue instead of main queue
• Updating UI directly from background thread
• Ignoring thread safety causing crashes

5. You want to update a SwiftUI view's text label from a background task safely. Which approach correctly uses @MainActor and async/await to update the UI?

hard

A. Use DispatchQueue.global().async to update the label

B. Declare the update function with @MainActor and call it with await inside the background task

C. Call the update function directly from the background thread without @MainActor

D. Update the label inside the background task without any special handling

Solution

1. Step 1: Understand UI update rules

   UI updates must happen on main thread to avoid crashes and glitches.

2. Step 2: Use @MainActor with async/await

   Marking the update function with @MainActor ensures it runs on main thread. Calling it with await from background task switches context safely.

3. Step 3: Evaluate other options

   Options A, B, and D update UI from background thread causing errors or crashes.

4. Final Answer:

   Declare the update function with @MainActor and call it with await inside the background task -> Option B

5. Quick Check:

   @MainActor + await = safe UI update [OK]

Hint: Use @MainActor function called with await for UI updates [OK]

Common Mistakes:

• Updating UI directly from background thread
• Ignoring await when calling @MainActor function
• Using global queue for UI updates