Functions and lambdas in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Identify the output of a lambda expression

What is the output of this Kotlin code snippet using a lambda function?

Android Kotlin

val numbers = listOf(1, 2, 3, 4)
val doubled = numbers.map { it * 2 }
println(doubled)

A Compilation error

B [1, 2, 3, 4]

C [1, 4, 9, 16]

D [2, 4, 6, 8]

💡 Hint

Remember that map applies the lambda to each element and returns a new list.

The map function applies the lambda 'it * 2' to each element, doubling each number.

❓ ui_behavior

intermediate

Lambda usage in button click listener

Given this Kotlin Android code, what happens when the button is clicked?

Android Kotlin

button.setOnClickListener { 
  textView.text = "Clicked!"
}

A The app crashes because the lambda is missing a parameter.

B The textView text changes to "Clicked!" when the button is clicked.

C Nothing happens because the listener is not set properly.

D The button text changes to "Clicked!" instead of textView.

💡 Hint

setOnClickListener takes a lambda with no parameters to handle clicks.

The lambda updates the textView's text property when the button is clicked.

❓ lifecycle

advanced

Effect of lambda capturing variables in Android lifecycle

Consider this Kotlin code inside an Activity: var count = 0 button.setOnClickListener { count++ textView.text = count.toString() } What happens to the count variable if the device is rotated (causing Activity recreation)?

A count keeps its value because lambdas preserve variable state across recreations.

B count increments twice on each click after rotation due to lambda duplication.

C count resets to 0 because the Activity is recreated and variables are reinitialized.

D The app crashes because count is accessed inside a lambda.

💡 Hint

Think about what happens to Activity variables on configuration changes.

When the Activity is recreated, all instance variables including count reset to initial values.

❓ navigation

advanced

Passing lambda as a callback between fragments

In Kotlin Android, you want to pass a lambda from Fragment A to Fragment B to handle a button click in Fragment B. Which approach correctly passes and uses the lambda?

A Define a lambda property in Fragment B and set it from Fragment A before navigation; call it inside Fragment B's button listener.

B Pass the lambda as a Bundle argument during navigation and retrieve it in Fragment B.

C Use a global variable to store the lambda accessible by both fragments.

D Lambdas cannot be passed between fragments; use interfaces instead.

💡 Hint

Lambdas are not Parcelable, so passing via Bundle is not possible.

You can define a lambda property in Fragment B and assign it from Fragment A before navigating. Then Fragment B calls it on button click.

🔧 Debug

expert

Diagnose the cause of a NullPointerException with lambda usage

This Kotlin code crashes with a NullPointerException when the button is clicked: var listener: (() -> Unit)? = null button.setOnClickListener { listener?.invoke() } // Somewhere else, listener is never assigned. What is the cause of the crash?

A The safe call operator ?. prevents invocation if listener is null, so no crash occurs.

B listener is null, so invoking it causes a NullPointerException.

C button is null, causing the crash when setOnClickListener is called.

D The lambda assigned to listener throws an exception internally.

💡 Hint

Check how the safe call operator ?. works in Kotlin.

The safe call operator ?. prevents invocation if listener is null, so no NullPointerException occurs here. The crash must be caused elsewhere.