withContext for thread switching in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to switch to the IO dispatcher using withContext.

Android Kotlin

suspend fun fetchData() {
  withContext([1]) {
    // perform IO operation
  }
}

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

ADispatchers.Main

BDispatchers.Default

CDispatchers.Unconfined

DDispatchers.IO

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.Main causes UI blocking.

Using Dispatchers.Default is for CPU-intensive tasks, not IO.

The Dispatchers.IO is used for IO-bound tasks like reading from disk or network calls.

2fill in blank

medium

Complete the code to switch back to the Main dispatcher after an IO operation.

Android Kotlin

suspend fun updateUI() {
  withContext(Dispatchers.IO) {
    // fetch data
  }
  withContext([1]) {
    // update UI
  }
}

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

ADispatchers.IO

BDispatchers.Unconfined

CDispatchers.Main

DDispatchers.Default

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.IO for UI updates causes exceptions.

Using Dispatchers.Default does not guarantee main thread execution.

UI updates must happen on the Main dispatcher to avoid crashes.

3fill in blank

hard

Fix the error in the code by choosing the correct dispatcher for CPU-intensive work.

Android Kotlin

suspend fun calculate() {
  withContext([1]) {
    // heavy computation
  }
}

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

ADispatchers.IO

BDispatchers.Default

CDispatchers.Main

DDispatchers.Unconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.IO for CPU work can cause thread starvation.

Using Dispatchers.Main blocks the UI.

Dispatchers.Default is optimized for CPU-intensive tasks like calculations.

4fill in blank

hard

Fill both blanks to correctly switch context for network call and UI update.

Android Kotlin

suspend fun loadData() {
  withContext([1]) {
    // network call
  }
  withContext([2]) {
    // update UI
  }
}

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

ADispatchers.IO

BDispatchers.Main

CDispatchers.Default

DDispatchers.Unconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Reversing the dispatchers causes UI crashes or blocking.

Using Dispatchers.Default for network calls is inefficient.

Network calls run on Dispatchers.IO, UI updates on Dispatchers.Main.

5fill in blank

hard

Fill all three blanks to create a map of word lengths filtering words longer than 4 characters.

Android Kotlin

suspend fun processWords(words: List<String>): Map<String, Int> = withContext([1]) {
  words.associateWith { word -> word.length }
}.filter { (word, length) -> length [2] [3] }

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

ADispatchers.Default

B>

C4

DDispatchers.IO

Attempts:

3 left

💡 Hint

Common Mistakes

Using IO dispatcher for length calculation is inefficient.

Using wrong comparison operator or number in filter.

Use Dispatchers.Default for CPU work, filter lengths greater than 4.

Practice

1. What is the main purpose of using withContext in Kotlin coroutines for Android?

easy

A. To cancel a running coroutine

B. To create a new coroutine scope

C. To delay coroutine execution

D. To switch the code execution to a different thread or dispatcher

Solution

1. Step 1: Understand withContext role

   withContext is used to change the thread or dispatcher where the coroutine code runs.

2. Step 2: Identify the correct purpose

   It does not create new scopes, cancel coroutines, or delay execution; it switches context.

3. Final Answer:

   To switch the code execution to a different thread or dispatcher -> Option D

4. Quick Check:

   withContext switches threads [OK]

Hint: Remember: withContext changes thread, not scope or delay [OK]

Common Mistakes:

• Confusing withContext with coroutineScope or launch
• Thinking withContext cancels coroutines
• Assuming withContext delays execution

2. Which of the following is the correct syntax to switch to the IO dispatcher using withContext?

easy

A. withContext(Dispatchers.IO) { /* code */ }

B. withContext(IO.Dispatchers) { /* code */ }

C. withContext(Dispatchers.Main) { /* code */ }

D. withContext(Dispatchers.Background) { /* code */ }

Solution

1. Step 1: Recall dispatcher names

   The correct dispatcher for background IO tasks is Dispatchers.IO.

2. Step 2: Match syntax

   The syntax is withContext(Dispatchers.IO) { ... }. Other options use wrong dispatcher names or order.

3. Final Answer:

   withContext(Dispatchers.IO) { /* code */ } -> Option A

4. Quick Check:

   Correct dispatcher syntax [OK]

Hint: Use Dispatchers.IO exactly as shown for background tasks [OK]

Common Mistakes:

• Swapping Dispatchers.IO and Dispatchers.Main
• Using incorrect dispatcher names like Background
• Wrong order of Dispatchers and IO

3. What will be the output of this Kotlin coroutine snippet?

println(Thread.currentThread().name)
withContext(Dispatchers.IO) {
  println(Thread.currentThread().name)
}
println(Thread.currentThread().name)

medium

A. IO thread name, IO thread name, IO thread name

B. Main thread name, Main thread name, Main thread name

C. Main thread name, IO thread name, Main thread name

D. IO thread name, Main thread name, IO thread name

Solution

1. Step 1: Identify thread before withContext

   The first println runs on the main thread, so it prints the main thread name.

2. Step 2: Identify thread inside withContext(Dispatchers.IO)

   The code inside withContext runs on the IO dispatcher thread, so it prints an IO thread name.

3. Step 3: Identify thread after withContext

   After withContext, execution returns to the original thread, main thread, so it prints main thread name again.

4. Final Answer:

   Main thread name, IO thread name, Main thread name -> Option C

5. Quick Check:

   withContext switches thread temporarily [OK]

Hint: withContext switches thread only inside its block [OK]

Common Mistakes:

• Assuming thread stays IO after withContext block
• Thinking all prints run on IO thread
• Confusing thread names printed

4. Identify the error in this coroutine code snippet:

launch {
  withContext(Dispatchers.IO) {
    updateUI()
  }
}

Assuming updateUI() modifies UI elements.

medium

A. Missing suspend keyword on updateUI()

B. Calling updateUI() inside Dispatchers.IO causes UI thread violation

C. withContext should use Dispatchers.Main instead of IO

D. launch should be replaced with async

Solution

1. Step 1: Understand thread rules for UI updates

   UI updates must happen on the main thread, not on IO or background threads.

2. Step 2: Analyze withContext usage

   withContext(Dispatchers.IO) switches to a background thread, so calling updateUI() there causes a thread violation.

3. Step 3: Identify the error

   The error is calling UI code on a non-main thread.

4. Final Answer:

   Calling updateUI() inside Dispatchers.IO causes UI thread violation -> Option B

5. Quick Check:

   UI code must run on main thread [OK]

Hint: UI updates only on Dispatchers.Main thread [OK]

Common Mistakes:

• Calling UI code on Dispatchers.IO
• Confusing launch and async for UI updates
• Ignoring thread rules for UI

5. You want to fetch data from the network and then update the UI with the result. Which is the correct way to use withContext for this task?

hard

A. Use withContext(Dispatchers.IO) for network call, then withContext(Dispatchers.Main) for UI update

B. Use withContext(Dispatchers.IO) for both network call and UI update

C. Use withContext(Dispatchers.Default) for both network call and UI update

D. Use withContext(Dispatchers.Main) for network call, then withContext(Dispatchers.IO) for UI update

Solution

1. Step 1: Identify correct dispatcher for network call

   Network calls should run on Dispatchers.IO to avoid blocking the main thread.

2. Step 2: Identify correct dispatcher for UI update

   UI updates must run on Dispatchers.Main to safely modify UI elements.

3. Step 3: Match correct order

   First switch to IO for network, then switch back to Main for UI update.

4. Final Answer:

   Use withContext(Dispatchers.IO) for network call, then withContext(Dispatchers.Main) for UI update -> Option A

5. Quick Check:

   Network on IO, UI on Main [OK]

Hint: Network on IO, UI on Main thread always [OK]

Common Mistakes:

• Reversing dispatcher order
• Using Default dispatcher for UI
• Running UI code on IO dispatcher