App signing in Flutter - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the keystore file path in the Flutter app signing configuration.

Flutter

android {
  signingConfigs {
    release {
      storeFile file('[1]')
    }
  }
}

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

Amy-release-key.keystore

Brelease-key.jks

Cdebug.keystore

Dapp-release.keystore

Attempts:

3 left

💡 Hint

Common Mistakes

Using the debug keystore file instead of the release keystore.

Using a wrong file extension like .jks if your keystore is .keystore.

The storeFile property should point to your keystore file, commonly named my-release-key.keystore.

2fill in blank

medium

Complete the code to set the key alias for signing the Flutter app.

Flutter

android {
  signingConfigs {
    release {
      keyAlias '[1]'
    }
  }
}

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

Arelease_key

Bflutter_key

Cmy_key_alias

Dandroiddebugkey

Attempts:

3 left

💡 Hint

Common Mistakes

Using the debug key alias instead of the release key alias.

Leaving the key alias empty.

The keyAlias is the name of the key inside the keystore. It is often set to my_key_alias for release builds.

3fill in blank

hard

Fix the error in the code by completing the password field for the keystore.

Flutter

android {
  signingConfigs {
    release {
      storePassword '[1]'
    }
  }
}

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

Aflutterpass

Bpassword123

Candroid

Dstorepass

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the store password with the key password.

Using a default or empty password.

The storePassword must match the password you set when creating the keystore. Here, storepass is the correct password.

4fill in blank

hard

Fill both blanks to complete the signing configuration for the release build.

Flutter

android {
  buildTypes {
    release {
      signingConfig signingConfigs.[1]
      minifyEnabled [2]
    }
  }
}

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

Arelease

Btrue

Cfalse

Ddebug

Attempts:

3 left

💡 Hint

Common Mistakes

Using the debug signing config for release builds.

Enabling minify when not intended.

The release build should use the release signing config and usually has minifyEnabled false to disable code shrinking during signing.

5fill in blank

hard

Fill all three blanks to complete the command for building a signed APK in Flutter.

Flutter

flutter build apk --[1] --[2]=release --[3]=app-release.apk

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

Atarget-platform

Bbuild-name

Cbuild-output

Dbuild-mode

Attempts:

3 left

💡 Hint

Common Mistakes

Using debug mode instead of release.

Confusing build-name with build-output.

The command uses --build-mode release to specify release build, --target-platform to specify the platform, and --build-output to name the APK file.