Signing configuration in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a signing configuration in the build.gradle.kts file.

Android Kotlin

signingConfigs {
    create("release") {
        storeFile = file([1])
    }
}

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

A"keystore.jks"

B"release.keystore"

C"mykeystore"

D"debug.keystore"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to put the keystore file name in quotes.

Using the wrong file name or extension.

The storeFile property expects a file path as a string. Here, "keystore.jks" is a common keystore file name.

2fill in blank

medium

Complete the code to set the keystore password in the signing configuration.

Android Kotlin

signingConfigs {
    create("release") {
        storePassword = [1]
    }
}

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

A"myPassword"

Bpassword123

C123password

D"password123"

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the password.

Using an incorrect password string.

The storePassword must be a string, so it needs to be in quotes.

3fill in blank

hard

Fix the error in the code by completing the alias property correctly.

Android Kotlin

signingConfigs {
    create("release") {
        keyAlias = [1]
    }
}

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

AreleaseKey

B"releaseKey"

C"release_key"

Drelease_key

Attempts:

3 left

💡 Hint

Common Mistakes

Not putting the alias in quotes.

Using an alias name with invalid characters.

The keyAlias must be a string, so it needs to be enclosed in quotes.

4fill in blank

hard

Fill both blanks to complete the signing configuration with key password and store password.

Android Kotlin

signingConfigs {
    create("release") {
        keyPassword = [1]
        storePassword = [2]
    }
}

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

A"keypass123"

B"storepass123"

Ckeypass123

Dstorepass123

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around passwords.

Mixing up keyPassword and storePassword values.

Both keyPassword and storePassword require string values, so they must be enclosed in quotes.

5fill in blank

hard

Fill all three blanks to define a complete release signing configuration with store file, key alias, and key password.

Android Kotlin

signingConfigs {
    create("release") {
        storeFile = file([1])
        keyAlias = [2]
        keyPassword = [3]
    }
}

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

A"release.keystore"

B"releaseKey"

C"keypass123"

D"debug.keystore"

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting strings.

Using wrong file names or alias names.

The storeFile needs a file path string, keyAlias and keyPassword need string values, all enclosed in quotes.

Practice

1.

What is the main purpose of a signing configuration in Android app development?

easy

A. To prove the app's identity and allow publishing

B. To increase app performance

C. To change the app's user interface

D. To add new features automatically

Solution

1. Step 1: Understand signing configuration role

   Signing configuration is used to prove the app's identity to Google Play and users.

2. Step 2: Identify its necessity for publishing

   Without signing, apps cannot be published or updated on app stores.

3. Final Answer:

   To prove the app's identity and allow publishing -> Option A

4. Quick Check:

   Signing config = app identity proof [OK]

Hint: Signing config proves app identity for publishing [OK]

Common Mistakes:

• Thinking signing improves app speed
• Confusing signing with UI changes
• Assuming signing adds features automatically

2.

Which of the following is the correct syntax to define a signing configuration in build.gradle?

signingConfigs {
    release {
        keyAlias 'myKey'
        keyPassword 'myPass'
        storeFile file('mykeystore.jks')
        storePassword 'storePass'
    }
}

easy

A. signingConfigs { release { keyAlias = 'myKey' keyPassword = 'myPass' storeFile = file('mykeystore.jks') storePassword = 'storePass' } }

B. signingConfigs { release { keyAlias 'myKey' keyPassword 'myPass' storeFile file('mykeystore.jks') storePassword 'storePass' } }

C. signingConfigs release { keyAlias = 'myKey' keyPassword = 'myPass' storeFile = file('mykeystore.jks') storePassword = 'storePass' }

D. signingConfigs { release { keyAlias: 'myKey' keyPassword: 'myPass' storeFile: file('mykeystore.jks') storePassword: 'storePass' } }

Solution

1. Step 1: Check Gradle Groovy DSL syntax for properties

   In Gradle Groovy DSL (build.gradle), properties are assigned without '=' but by space, e.g., keyAlias 'myKey'.

2. Step 2: Verify correct block structure

   The signingConfigs block must wrap the release block with properties assigned without '='.

3. Final Answer:

   signingConfigs { release { keyAlias 'myKey' keyPassword 'myPass' storeFile file('mykeystore.jks') storePassword 'storePass' } } -> Option B

4. Quick Check:

   Groovy DSL uses space for property assignment [OK]

Hint: Use space (no '=') for property assignment in Groovy Gradle blocks [OK]

Common Mistakes:

• Using '=' in Groovy DSL instead of space
• Using ':' instead of '=' or space
• Not wrapping properties inside release block

3.

Given this build.gradle snippet, what signing configuration will be used when building the release version?

android {
  signingConfigs {
    debug {
      keyAlias = 'debugKey'
    }
    release {
      keyAlias = 'releaseKey'
    }
  }
  buildTypes {
    release {
      signingConfig signingConfigs.release
    }
    debug {
      signingConfig signingConfigs.debug
    }
  }
}

medium

A. releaseKey

B. Both debugKey and releaseKey

C. No signing configuration used

D. debugKey

Solution

1. Step 1: Identify signingConfig for release buildType

   The release buildType uses signingConfigs.release as its signingConfig.

2. Step 2: Check keyAlias in release signingConfig

   The release signingConfig has keyAlias set to 'releaseKey'.

3. Final Answer:

   releaseKey -> Option A

4. Quick Check:

   release build uses release signingConfig [OK]

Hint: Release build uses signingConfigs.release [OK]

Common Mistakes:

• Confusing debug and release signingConfigs
• Assuming no signingConfig is set
• Thinking both keys are used simultaneously

4.

What is the error in this signing configuration snippet?

signingConfigs {
  release {
    keyAlias = 'myKey'
    keyPassword = 'pass'
    storeFile = 'mykeystore.jks'
    storePassword = 'storePass'
  }
}

medium

A. storePassword is missing

B. keyAlias must be a number

C. storeFile should use file() function

D. keyPassword cannot be set

Solution

1. Step 1: Check storeFile assignment

   storeFile must be assigned a File object using file('filename'), not a plain string.

2. Step 2: Confirm other properties are correct

   keyAlias, keyPassword, and storePassword are correctly assigned strings.

3. Final Answer:

   storeFile should use file() function -> Option C

4. Quick Check:

   storeFile = file('path') required [OK]

Hint: Use file() for storeFile path in signingConfigs [OK]

Common Mistakes:

• Assigning storeFile directly as string
• Confusing keyAlias type
• Omitting storePassword

5.

You want to create a signing configuration that uses different keystores for debug and release builds. How should you configure build.gradle to achieve this?

android {
  signingConfigs {
    debug {
      keyAlias = 'debugKey'
      keyPassword = 'debugPass'
      storeFile = file('debug.keystore')
      storePassword = 'debugStorePass'
    }
    release {
      keyAlias = 'releaseKey'
      keyPassword = 'releasePass'
      storeFile = file('release.keystore')
      storePassword = 'releaseStorePass'
    }
  }
  buildTypes {
    debug {
      signingConfig signingConfigs.debug
    }
    release {
      signingConfig signingConfigs.release
    }
  }
}

What will happen if you build the debug version?

hard

A. Build will fail due to missing signingConfig

B. The app will be signed with the release keystore

C. The app will not be signed

D. The app will be signed with the debug keystore

Solution

1. Step 1: Check signingConfig assigned to debug buildType

   The debug buildType uses signingConfigs.debug as its signingConfig.

2. Step 2: Identify keystore used for debug build

   SigningConfigs.debug uses 'debug.keystore' with its own keys and passwords.

3. Final Answer:

   The app will be signed with the debug keystore -> Option D

4. Quick Check:

   Debug build uses debug signingConfig [OK]

Hint: Debug build uses debug keystore signingConfig [OK]

Common Mistakes:

• Assuming debug uses release keystore
• Thinking build fails without explicit signingConfig
• Believing app is unsigned by default