Task and TaskGroup in iOS Swift - UI Render Trace

Component - Task and TaskGroup

This UI component demonstrates how Swift's Task and TaskGroup work together to run multiple asynchronous tasks concurrently. It shows a list of tasks running and their results updating on the screen as they complete.

Widget Tree

VStack
├── Text (Title)
├── List
│   ├── ForEach (Task Results)
│   │   └── Text (Result Item)
└── Button (Start Tasks)

The main vertical stack (VStack) holds a title text at the top, a list showing results of each asynchronous task, and a button at the bottom to start running the tasks concurrently.

Render Trace - 4 Steps

Step 1: VStack

Step 2: Text (Title)

Step 3: List

Step 4: Button

State Change - Re-render

Trigger:User taps 'Start Tasks' button

Before

taskResults array is empty, list shows no items

→

After

taskResults array fills with strings as each async task completes, list updates to show results

Re-renders:The List and its child Text views re-render to show updated task results

UI Quiz - 3 Questions

What happens when the 'Start Tasks' button is tapped?

A The button disappears and nothing else happens

B The app navigates to a new screen

C Multiple asynchronous tasks run concurrently and update the list as they finish

D The title text changes to 'Tasks Running'

Key Insight

Using Task and TaskGroup in Swift allows running multiple asynchronous operations at the same time. Updating a shared state array with results triggers the UI list to refresh automatically, showing progress in real time. This pattern helps keep the UI responsive and informative during background work.

Practice

1. What is the main purpose of a Task in Swift concurrency?

easy

A. To run a single background job asynchronously

B. To group multiple tasks and run them together

C. To update the UI on the main thread

D. To pause the app execution

Solution

1. Step 1: Understand what Task does

   A Task is designed to run one asynchronous job in the background.

2. Step 2: Differentiate from TaskGroup

   TaskGroup runs many jobs together, not a single job.

3. Final Answer:

   To run a single background job asynchronously -> Option A

4. Quick Check:

   Task = single background job [OK]

Hint: Task runs one job; TaskGroup runs many [OK]

Common Mistakes:

• Confusing Task with TaskGroup
• Thinking Task updates UI directly
• Assuming Task pauses app execution

2. Which of the following is the correct syntax to create a Task that prints "Hello" asynchronously?

easy

A. async Task { print("Hello") }

B. TaskGroup { print("Hello") }

C. Task.run { print("Hello") }

D. Task { print("Hello") }

Solution

1. Step 1: Recall correct Task syntax

   The correct way to create a Task is using Task { ... } with a closure.

2. Step 2: Check other options for errors

   TaskGroup is not used like this; async Task and Task.run are invalid syntax.

3. Final Answer:

   Task { print("Hello") } -> Option D

4. Quick Check:

   Correct Task syntax = Task { print("Hello") } [OK]

Hint: Use Task { } with closure for async code [OK]

Common Mistakes:

• Using TaskGroup instead of Task
• Adding 'async' keyword before Task
• Trying to call Task.run which doesn't exist

3. What will be printed by this Swift code using TaskGroup?

func fetchData() async {
  await withTaskGroup(of: String.self) { group in
    group.addTask { "A" }
    group.addTask { "B" }
    for await result in group {
      print(result)
    }
  }
}
fetchData()

medium

A. Either A then B or B then A (order not guaranteed)

B. B then A in order

C. A then B in order

D. No output because of syntax error

Solution

1. Step 1: Understand TaskGroup concurrency

   TaskGroup runs tasks concurrently and collects results as they finish, order is not guaranteed.

2. Step 2: Analyze the code output

   Since tasks return "A" and "B" concurrently, the print order can be either "A" then "B" or "B" then "A".

3. Final Answer:

   Either A then B or B then A (order not guaranteed) -> Option A

4. Quick Check:

   TaskGroup results order is unpredictable [OK]

Hint: TaskGroup runs tasks concurrently; output order varies [OK]

Common Mistakes:

• Assuming TaskGroup results are always ordered
• Thinking tasks run sequentially
• Believing syntax error prevents output

4. Identify the error in this Swift code using TaskGroup:

await withTaskGroup(of: Int.self) { group in
  group.addTask { 1 }
  group.addTask { 2 }
  for result in group {
    print(result)
  }
}

medium

A. Incorrect type in 'withTaskGroup' declaration

B. Using 'for' instead of 'for await' to iterate the group

C. Missing 'await' before 'for' loop

D. Cannot add tasks inside 'withTaskGroup'

Solution

1. Step 1: Check iteration over TaskGroup

   Iteration over a TaskGroup is asynchronous, so it requires for await.

2. Step 2: Identify the error in the code

   The code uses for result in group without await, causing a compile error.

3. Final Answer:

   Using 'for' instead of 'for await' to iterate the group -> Option B

4. Quick Check:

   Async iteration needs 'for await' [OK]

Hint: Use 'for await' to loop over TaskGroup results [OK]

Common Mistakes:

• Forgetting 'await' in asynchronous loops
• Confusing TaskGroup type declaration
• Thinking tasks can't be added inside withTaskGroup

5. You want to fetch user data from three different servers concurrently and combine the results. Which Swift concurrency pattern using TaskGroup is best to achieve this?

hard

A. Create three separate Task instances and wait for each sequentially

B. Run three synchronous functions one after another on the main thread

C. Use a TaskGroup to add three tasks fetching data, then collect all results asynchronously

D. Use a single Task that fetches data from all servers sequentially

Solution

1. Step 1: Understand concurrency needs

   Fetching from three servers concurrently requires running tasks in parallel to save time.

2. Step 2: Choose the best Swift concurrency pattern

   TaskGroup allows adding multiple tasks and collecting results asynchronously, perfect for this use case.

3. Final Answer:

   Use a TaskGroup to add three tasks fetching data, then collect all results asynchronously -> Option C

4. Quick Check:

   TaskGroup = concurrent multiple tasks [OK]

Hint: Use TaskGroup for multiple concurrent tasks and results [OK]

Common Mistakes:

• Running tasks sequentially losing concurrency benefits
• Using synchronous calls blocking main thread
• Using single Task for sequential fetches