Room with Coroutines in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when you call a suspend DAO function from the main thread?

Consider a Room DAO suspend function called directly from the main thread without using any coroutine builder. What will happen?

A The app crashes with an IllegalStateException.

B The function returns immediately without executing.

C The function blocks the main thread until completion.

D The function runs asynchronously without blocking the main thread.

💡 Hint

Room enforces thread rules for database access.

Room requires database operations to be off the main thread. Calling a suspend DAO function directly on the main thread without coroutine context causes an IllegalStateException.

🧠 Conceptual

intermediate

Why use Flow in Room DAO with Coroutines?

What is the main advantage of returning a Flow from a Room DAO query function compared to a suspend function?

A Suspend functions automatically cache data, Flow does not.

B Flow provides continuous updates when the database changes, while suspend functions return data only once.

C Flow runs on the main thread by default, making UI updates easier.

D Flow requires no coroutine context to collect data.

💡 Hint

Think about live data updates.

Flow emits new data whenever the database table changes, allowing UI to reactively update. Suspend functions return a single snapshot of data.

❓ lifecycle

advanced

What happens if you collect a Flow from Room DAO without lifecycle awareness?

If you collect a Flow returned by a Room DAO in a coroutine launched in a ViewModel without tying it to lifecycle, what is a likely consequence?

A The Flow collection pauses and resumes automatically with lifecycle.

B The Flow collection automatically stops when the UI is destroyed.

C The Flow collection throws an exception when UI is destroyed.

D The Flow collection continues even after the UI is destroyed, causing memory leaks.

💡 Hint

Consider what happens when UI components are destroyed.

Without lifecycle-aware collection, the coroutine collecting the Flow keeps running, potentially leaking memory and wasting resources.

📝 Syntax

advanced

Which DAO function signature correctly uses suspend with Room?

Choose the correct Kotlin DAO function signature for inserting a User entity using coroutines.

A suspend fun insertUser(user: User): Long

B fun insertUser(user: User): Deferred<Long>

C fun insertUser(user: User): Long

D suspend fun insertUser(user: User): Unit

💡 Hint

Room supports suspend functions returning inserted row id.

The correct signature is a suspend function returning Long for the inserted row id. Deferred return type is not supported by Room DAO directly.

🔧 Debug

expert

Why does this coroutine collecting a Room Flow never emit data?

Given this code snippet in a ViewModel: val usersFlow = userDao.getAllUsers() init { viewModelScope.launch { usersFlow.collect { users -> // update UI } } } The UI never updates even though the database has users. What is the most likely cause?

Android Kotlin

val usersFlow = userDao.getAllUsers()

init {
  viewModelScope.launch {
    usersFlow.collect { users ->
      // update UI
    }
  }
}

A The usersFlow variable is not marked as suspend.

B The coroutine is launched on Dispatchers.Main which cannot collect Flow.

C The getAllUsers() DAO function is not annotated with @Query returning Flow.

D The collect block is missing a delay causing it to skip emissions.

💡 Hint

Check DAO function annotations and return types.

If the DAO function does not return a Flow (missing @Query or wrong return type), the Flow will never emit data and collection will not trigger updates.

Practice

1. What is the main benefit of using Coroutines with Room in Android development?

easy

A. They replace the need for SQL queries.

B. They automatically create database tables.

C. They allow database operations to run without freezing the app UI.

D. They make the app use less memory.

Solution

1. Step 1: Understand Coroutines role

   Coroutines let tasks run in the background without blocking the main app thread.

2. Step 2: Connect Coroutines with Room

   Room uses suspend functions with Coroutines to perform database operations smoothly without freezing UI.

3. Final Answer:

   They allow database operations to run without freezing the app UI. -> Option C

4. Quick Check:

   Coroutines keep UI responsive = A [OK]

Hint: Coroutines keep UI smooth by running tasks in background [OK]

Common Mistakes:

• Thinking Coroutines create tables automatically
• Believing Coroutines replace SQL queries
• Assuming Coroutines reduce app memory usage directly

2. Which of the following is the correct way to declare a suspend function in a Room DAO interface?

easy

A. suspend fun getAllUsers(): List<User>

B. fun getAllUsers(): List<User>

C. async fun getAllUsers(): List<User>

D. fun suspend getAllUsers(): List<User>

Solution

1. Step 1: Recall suspend function syntax

   A suspend function is declared with the keyword suspend before fun.

2. Step 2: Check each option

   suspend fun getAllUsers(): List<User> correctly uses suspend fun. Plain fun getAllUsers(): List<User> lacks the suspend keyword. fun suspend getAllUsers(): List<User> has the keywords in wrong order. async fun getAllUsers(): List<User> uses async which is not valid here.

3. Final Answer:

   suspend fun getAllUsers(): List<User> -> Option A

4. Quick Check:

   suspend keyword before fun = B [OK]

Hint: Remember: suspend keyword always comes before fun [OK]

Common Mistakes:

• Placing suspend after fun
• Using async instead of suspend
• Omitting suspend keyword for coroutine functions

3. Given this DAO function:

 @Query("SELECT * FROM users")
 suspend fun getUsers(): List<User>

What happens when you call getUsers() from a coroutine?

medium

A. The function blocks the main thread until data is fetched.

B. The function suspends the coroutine until data is fetched, then returns the list.

C. The function returns immediately with an empty list.

D. The function throws a compile-time error.

Solution

1. Step 1: Understand suspend function behavior

   A suspend function pauses the coroutine without blocking the thread until the result is ready.

2. Step 2: Apply to Room DAO call

   Calling getUsers() suspends the coroutine until Room fetches data, then returns the list.

3. Final Answer:

   The function suspends the coroutine until data is fetched, then returns the list. -> Option B

4. Quick Check:

   suspend functions pause coroutine, not block thread = C [OK]

Hint: Suspend functions pause coroutine, not block main thread [OK]

Common Mistakes:

• Thinking suspend blocks main thread
• Expecting immediate empty list return
• Assuming compile-time error on suspend

4. You wrote this DAO method:

@Query("SELECT * FROM users")
fun getUsers(): List<User>

When calling getUsers() from a coroutine, what problem will occur?

medium

A. The app will crash with a runtime error about main thread database access.

B. The function will suspend correctly and return data.

C. The function will return null instead of data.

D. The function will compile but never return.

Solution

1. Step 1: Identify missing suspend keyword

   The DAO method is not marked suspend, so it runs on the calling thread.

2. Step 2: Understand Room's main thread policy

   Room forbids database queries on the main thread to avoid freezing UI, causing runtime crash if violated.

3. Final Answer:

   The app will crash with a runtime error about main thread database access. -> Option A

4. Quick Check:

   Non-suspend DAO on main thread causes crash = A [OK]

Hint: Always mark DAO queries suspend to avoid main thread crash [OK]

Common Mistakes:

• Forgetting suspend keyword in DAO
• Expecting null return on wrong thread
• Assuming silent failure without crash

5. You want to insert a list of users into the database using Room and Coroutines. Which DAO method signature correctly supports this operation without blocking the UI?

@Insert
??? fun insertUsers(users: List<User>)

hard

A. fun insertUsers(users: List<User>)

B. async fun insertUsers(users: List<User>)

C. fun insertUsers(users: List<User>): Deferred<Unit>

D. suspend fun insertUsers(users: List<User>)

Solution

1. Step 1: Identify correct coroutine support

   To run database operations without blocking UI, DAO methods must be suspend functions.

2. Step 2: Evaluate options

   suspend fun insertUsers(users: List<User>) uses suspend fun, which is correct. fun insertUsers(users: List<User>) blocks UI. fun insertUsers(users: List<User>): Deferred<Unit> returns Deferred which is not standard DAO signature. async fun insertUsers(users: List<User>) uses invalid async keyword.

3. Final Answer:

   suspend fun insertUsers(users: List<User>) -> Option D

4. Quick Check:

   Use suspend fun for non-blocking Room inserts = D [OK]

Hint: Use suspend fun for DAO inserts to keep UI smooth [OK]

Common Mistakes:

• Omitting suspend causing UI freeze
• Using async keyword incorrectly
• Returning Deferred instead of suspend function