MainActor for UI work in Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to mark the function to run on the main thread.

Swift

@[1]
func updateUI() {
    print("UI updated")
}

Drag options to blanks, or click blank then click option'

AUIActor

BBackgroundActor

CMainActor

DAsyncActor

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong actor attribute that does not guarantee main thread execution.

The @MainActor attribute ensures the function runs on the main thread, which is required for UI updates.

2fill in blank

medium

Complete the code to ensure the async function runs on the main thread.

Swift

func fetchData() async {
    await [1] {
        print("Data fetched and UI updated")
    }
}

Drag options to blanks, or click blank then click option'

ATask.detached

BDispatchQueue.global().async

CDispatchQueue.main.async

DMainActor.run

Attempts:

3 left

💡 Hint

Common Mistakes

Using DispatchQueue.global() which runs on a background thread.

Using Task.detached which runs detached from any actor.

MainActor.run ensures the closure runs on the main thread asynchronously.

3fill in blank

hard

Fix the error in the code to update the UI safely on the main thread.

Swift

class ViewModel {
    func update() async {
        await [1] {
            print("UI updated")
        }
    }
}

Drag options to blanks, or click blank then click option'

AMainActor.run

BDispatchQueue.global().async

CTask.detached

DDispatchQueue.main.async

Attempts:

3 left

💡 Hint

Common Mistakes

Using DispatchQueue.global() which runs on a background thread.

Using Task.detached which runs detached from any actor.

Using MainActor.run inside async function ensures UI updates happen on the main thread safely.

4fill in blank

hard

Fill both blanks to create a MainActor isolated class with a UI update method.

Swift

@[1]
class UIHandler {
    func refresh() [2] {
        print("Refreshing UI")
    }
}

Drag options to blanks, or click blank then click option'

AMainActor

Basync

Cnonisolated

Dsync

Attempts:

3 left

💡 Hint

Common Mistakes

Marking the method as nonisolated which breaks main thread isolation.

Using sync keyword which is invalid in Swift.

Marking the class with @MainActor isolates it to the main thread, and the async method allows asynchronous UI updates.

5fill in blank

hard

Fill all three blanks to define a MainActor isolated class with an async UI update method and call it safely.

Swift

import Foundation

@[1]
class Controller {
    func updateUI() [2] {
        print("UI Updated")
    }
}

func performUpdate() async {
    let controller = Controller()
    await controller.[3]()
}

Drag options to blanks, or click blank then click option'

AMainActor

Basync

CupdateUI

Dsync

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to mark the method async.

Calling the async method without await.

Using sync keyword which is invalid.

The class is marked @MainActor to isolate it to the main thread, the method is async to allow awaiting, and the method is called with await.

Practice

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

easy

A. To create multiple threads for UI tasks

B. To speed up background data processing

C. To disable asynchronous programming

D. To ensure UI updates run on the main thread safely

Solution

1. Step 1: Understand the role of @MainActor

   @MainActor marks code to run on the main thread, which is required for UI updates to avoid crashes or glitches.

2. Step 2: Compare options with this role

   Only To ensure UI updates run on the main thread safely correctly states that @MainActor ensures UI updates run safely on the main thread. Other options describe unrelated or incorrect behaviors.

3. Final Answer:

   To ensure UI updates run on the main thread safely -> Option D

4. Quick Check:

   @MainActor = safe UI updates on main thread [OK]

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

Common Mistakes:

• Thinking @MainActor speeds up background tasks
• Confusing @MainActor with creating multiple threads
• Believing @MainActor disables async programming

2. Which of the following is the correct way to declare a function that updates UI and must run on the main thread using @MainActor?

easy

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

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

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

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

Solution

1. Step 1: Recall correct syntax for @MainActor on functions

   The attribute @MainActor must appear before the 'func' keyword. Swift uses postfix 'async' after parameters for asynchronous functions: @MainActor func updateUI() async { /* code */ }. For synchronous UI updates, @MainActor func updateUI() { /* code */ } is correct.

2. Step 2: Analyze each option

   @MainActor async func updateUI() { /* code */ } uses invalid prefix 'async func' syntax. @MainActor func updateUI() { /* code */ } is correct for synchronous UI function on main thread. func updateUI() async @MainActor { /* code */ } misplaces @MainActor after 'async'. func updateUI() @MainActor { /* code */ } places @MainActor incorrectly after function name.

3. Final Answer:

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

4. Quick Check:

   @MainActor before func keyword = correct syntax [OK]

Hint: @MainActor before func keyword for main thread UI functions [OK]

Common Mistakes:

• Using invalid prefix 'async func' syntax from other languages
• Placing @MainActor after function name or 'async'
• Misordering keywords in function declaration

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 when this code runs?

medium

A. 1

B. 0

C. Compilation error

D. Runtime crash

Solution

1. Step 1: Understand @MainActor effect on ViewModel

   The class is marked @MainActor, so all its properties and methods are main actor-isolated and require 'await' when accessed from non-isolated contexts like Tasks.

2. Step 2: Analyze the Task block

   The Task calls await vm.increment(), which correctly hops to the main actor and increments count to 1. The print(vm.count) is inside the Task closure, which is asynchronous and runs on the main actor context, so accessing vm.count is allowed and will print 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Accessing @MainActor properties inside async Task after await is allowed [OK]

Hint: Use 'await' for @MainActor-isolated properties in Tasks [OK]

Common Mistakes:

• Thinking print(vm.count) works and shows 1 after await increment
• Assuming count stays 0 without proper isolation handling
• Expecting runtime crash instead of compilation error

4. Identify the error in this Swift code using @MainActor:

class DataFetcher {
    @MainActor
    func fetchData() async {
        // fetch data
    }
}

let fetcher = DataFetcher()
Task {
    await fetcher.fetchData()
}

medium

A. Cannot use @MainActor on a method inside a non-actor class

B. Missing async keyword on fetchData()

C. No error, code is correct

D. Must mark class as @MainActor, not just method

Solution

1. Step 1: Check @MainActor usage on method

   Applying @MainActor to a method inside a normal class is allowed to ensure that method runs on main thread.

2. Step 2: Verify async and call correctness

   The method is async and called with await inside a Task, which is correct usage.

3. Final Answer:

   No error, code is correct -> Option C

4. Quick Check:

   @MainActor on method in class is valid [OK]

Hint: You can mark methods @MainActor even in normal classes [OK]

Common Mistakes:

• Thinking @MainActor only applies to classes
• Forgetting async keyword on async methods
• Assuming error without checking async/await usage

5. You have a SwiftUI app where a ViewModel class marked @MainActor updates a published property text. You want to fetch data asynchronously on a background thread and then update text safely on the main thread. Which approach correctly uses @MainActor to ensure safe UI updates?

hard

A. Mark the entire ViewModel as @MainActor and call async fetch on a background thread, then update text inside a @MainActor method

B. Do not use @MainActor; update text directly from any thread

C. Mark only the fetch method as @MainActor and update text without awaiting

D. Use DispatchQueue.global() to update text asynchronously

Solution

1. Step 1: Understand thread safety for UI updates

   UI updates must happen on the main thread. Marking ViewModel as @MainActor ensures all its properties and methods run on main thread.

2. Step 2: Use async fetch on background thread and update on main thread

   Fetching data can happen on background thread, but updating text must be done inside a @MainActor context, which is guaranteed if ViewModel is @MainActor.

3. Final Answer:

   Mark the entire ViewModel as @MainActor and call async fetch on a background thread, then update text inside a @MainActor method -> Option A

4. Quick Check:

   @MainActor ViewModel + async fetch + main thread update = safe UI [OK]

Hint: Mark ViewModel @MainActor to keep UI updates safe [OK]

Common Mistakes:

• Updating UI from background thread without @MainActor
• Not awaiting async fetch before updating UI
• Using global queue to update UI causing crashes