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.

Practice

1. What is the main purpose of the debug build variant in Android development?

easy

A. To publish the app on the Play Store

B. To test the app with debugging tools enabled

C. To reduce the app size for faster downloads

D. To disable all logging and debugging features

Solution

1. Step 1: Understand build variant roles

   The debug variant is designed for developers to test and debug the app during development.

2. Step 2: Compare with release variant

   The release variant is optimized and signed for publishing, unlike debug.

3. Final Answer:

   To test the app with debugging tools enabled -> Option B

4. Quick Check:

   Debug variant = testing with debugging [OK]

Hint: Debug variant is for testing, release is for publishing [OK]

Common Mistakes:

• Confusing debug with release variant
• Thinking debug is for publishing
• Assuming debug disables logging

2. Which of the following is the correct way to specify a release build variant in the build.gradle file?

easy

A. buildVariants { debug { minifyEnabled false } }

B. buildVariants { release { minifyEnabled true } }

C. buildTypes { release { minifyEnabled false } }

D. buildTypes { debug { minifyEnabled true } }

Solution

1. Step 1: Identify correct block name

   The correct block to define build variants is buildTypes, not buildVariants.

2. Step 2: Check release variant syntax

   Inside buildTypes, release can have minifyEnabled set to true or false. buildTypes { release { minifyEnabled false } } uses correct syntax with minifyEnabled false.

3. Final Answer:

   buildTypes { release { minifyEnabled false } } -> Option C

4. Quick Check:

   Use buildTypes block for release variant [OK]

Hint: Use buildTypes, not buildVariants, to define release [OK]

Common Mistakes:

• Using buildVariants instead of buildTypes
• Mixing debug and release settings
• Incorrect minifyEnabled value placement

3. Given this build.gradle snippet, what will be the application ID for the debug build variant?

android {
  defaultConfig {
    applicationId "com.example.app"
  }
  buildTypes {
    debug {
      applicationIdSuffix ".debug"
    }
    release {
      minifyEnabled true
    }
  }
}

medium

A. com.example.app

B. com.example.debug.app

C. com.example.apprelease

D. com.example.app.debug

Solution

1. Step 1: Identify default application ID

   The default application ID is com.example.app from defaultConfig.

2. Step 2: Check debug variant suffix

   The debug build type adds .debug as a suffix to the application ID.

3. Final Answer:

   com.example.app.debug -> Option D

4. Quick Check:

   Debug variant adds suffix .debug [OK]

Hint: Debug adds suffix; release usually does not [OK]

Common Mistakes:

• Ignoring applicationIdSuffix
• Confusing suffix placement
• Assuming release suffix applies to debug

4. You have this build.gradle snippet:

buildTypes {
  release {
    minifyEnabled true
    proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
  }
  debug {
    minifyEnabled true
  }
}

What is the problem with this configuration?

medium

A. minifyEnabled should be false for debug builds to avoid obfuscation

B. proguardFiles cannot be used in release builds

C. minifyEnabled must be true for debug builds

D. The buildTypes block is missing a closing brace

Solution

1. Step 1: Understand minifyEnabled purpose

   Minify (obfuscation) is usually enabled in release builds to shrink and protect code.

2. Step 2: Check debug build settings

   Enabling minify in debug builds is uncommon and can make debugging harder.

3. Final Answer:

   minifyEnabled should be false for debug builds to avoid obfuscation -> Option A

4. Quick Check:

   Debug builds usually disable minify [OK]

Hint: Disable minify in debug to ease debugging [OK]

Common Mistakes:

• Enabling minify in debug builds
• Thinking proguardFiles are invalid in release
• Missing braces in buildTypes block

5. You want to create a new build variant called staging that behaves like release but with a different application ID and no code shrinking. Which build.gradle snippet correctly achieves this?

hard

A. buildTypes {
staging {
initWith release
applicationIdSuffix ".staging"
minifyEnabled false
}
}

B. buildTypes {
staging {
initWith debug
applicationIdSuffix ".staging"
minifyEnabled true
}
}

C. buildTypes {
staging {
applicationIdSuffix ".staging"
minifyEnabled true
}
}

D. buildTypes {
staging {
initWith release
applicationIdSuffix ".release"
minifyEnabled true
}
}

Solution

1. Step 1: Use initWith to copy release settings

   The initWith release copies all release build settings to staging.

2. Step 2: Override applicationIdSuffix and minifyEnabled

   Set applicationIdSuffix ".staging" to differentiate the app ID and minifyEnabled false to disable code shrinking.

3. Final Answer:

   buildTypes { staging { initWith release applicationIdSuffix ".staging" minifyEnabled false } } -> Option A

4. Quick Check:

   initWith release + override suffix and minify [OK]

Hint: Use initWith release, then override needed settings [OK]

Common Mistakes:

• Using initWith debug instead of release
• Forgetting to disable minify for staging
• Using wrong applicationIdSuffix