Build variants (debug, release) in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding build variant purpose

What is the main purpose of having separate debug and release build variants in Android development?

A To allow developers to test the app with debugging tools and enable optimizations for the final release.

B To create two completely different apps with unrelated codebases.

C To prevent the app from running on certain devices.

D To automatically translate the app into multiple languages.

💡 Hint

Think about why developers need different versions during development and for users.

Debug builds include debugging tools and are easier to test, while release builds are optimized and signed for distribution.

❓ ui_behavior

intermediate

Behavior difference in debug vs release

If you add a log statement inside your Android app, in which build variant will the log messages typically appear?

A Only in the debug build variant.

B Only in the release build variant.

C In both debug and release build variants.

D Log statements never appear in any build variant.

💡 Hint

Consider what happens to logs in release builds for performance and security.

Debug builds show logs to help developers, but release builds usually remove or disable logs to improve performance and security.

❓ lifecycle

advanced

Build variant effect on app signing

Which statement correctly describes how app signing differs between debug and release build variants in Android?

A Neither debug nor release builds require signing.

B Both debug and release builds use the same keystore automatically generated by Android Studio.

C Release builds do not require signing, but debug builds do.

D Debug builds use a debug keystore automatically generated by Android Studio; release builds require a developer-provided keystore.

💡 Hint

Think about how apps are prepared for publishing versus testing.

Debug builds use a default debug keystore for convenience, while release builds must be signed with a secure keystore provided by the developer.

📝 Syntax

advanced

Gradle build variant configuration

Given this snippet in build.gradle.kts, which option correctly adds a custom field only to the debug build?

Android Kotlin

android {
  buildTypes {
    getByName("debug") {
      // Add custom field here
    }
  }
}

A buildConfigField(String, API_URL, 'https://debug.api.com')

B buildConfigField("String", "API_URL", "https://debug.api.com")

C buildConfigField("String", "API_URL", "\"https://debug.api.com\"")

D buildConfigField('String', 'API_URL', 'https://debug.api.com')

💡 Hint

Remember the syntax requires types and values as strings with escaped quotes.

The correct syntax uses escaped double quotes (\") inside the double-quoted value string.

🔧 Debug

expert

Release build crashes due to missing debug-only code

You have code that calls a debug-only method inside your app. It works in debug builds but crashes in release builds. What is the most likely cause?

A Release builds do not support method calls at all.

B The debug-only method is removed or not included in the release build, causing a crash.

C The debug build disables ProGuard, so the method is missing in debug builds.

D The release build uses a different programming language.

💡 Hint

Think about code shrinking and conditional compilation in release builds.

Release builds often remove debug-only code via ProGuard or build config flags, so calling such methods causes crashes.