Android build and signing in React Native - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of the signing key

Why do Android apps require a signing key before publishing?

Select the best explanation.

A To increase the app's download speed from the Play Store

B To encrypt the app's code so users cannot see it

C To verify the app's identity and ensure updates come from the same developer

D To reduce the app's size by compressing resources

💡 Hint

Think about how the Play Store knows the app is from the original developer.

Android requires apps to be signed with a key to verify the developer's identity and to allow secure updates. This prevents others from tampering with the app.

❓ ui_behavior

intermediate

Effect of incorrect signing on app installation

What happens if you try to install an Android app update signed with a different key than the original?

Choose the correct behavior.

A The system merges both apps into one

B The system rejects the update and shows a signature mismatch error

C The update installs normally, replacing the old app

D The update installs but disables all permissions

💡 Hint

Think about security checks during app updates.

Android checks that the update is signed with the same key as the installed app. If not, it rejects the update to prevent unauthorized changes.

❓ lifecycle

advanced

Keystore file lifecycle in React Native Android builds

In a React Native Android project, where should the keystore file be placed and how is it referenced during the build?

Choose the correct description.

A Place the keystore in android/app and reference it in android/gradle.properties with signing configs

B Place the keystore in the root project folder and reference it in package.json

C Place the keystore in android/build and reference it in MainActivity.java

D Place the keystore anywhere and the build system automatically finds it

💡 Hint

Think about how Gradle uses signing configs.

The keystore file is usually placed in android/app folder. The build.gradle file uses signingConfigs that reference the keystore path and credentials, often stored in gradle.properties.

❓ navigation

advanced

Choosing the correct build command for release APK

Which command correctly builds a signed release APK for a React Native Android app?

Assume the keystore and signing configs are properly set.

A cd android && ./gradlew assembleRelease

B react-native run-android --variant=release

C npm run android-release

D gradle buildRelease

💡 Hint

Think about the official Gradle command for building release APKs.

The correct command to build a signed release APK is to run the Gradle wrapper with the assembleRelease task inside the android folder.

🔧 Debug

expert

Diagnosing a build failure due to missing signing config

You run './gradlew assembleRelease' but get this error:

"SigningConfig 'release' not found"

What is the most likely cause?

A The React Native version is incompatible with signing

B The keystore file is corrupted and unreadable

C The AndroidManifest.xml is missing the signingConfig attribute

D The build.gradle file does not define a signingConfig named 'release'

💡 Hint

Check the build.gradle signingConfigs section.

This error means the build script expects a signingConfig named 'release' but it is not defined in build.gradle. The keystore file or manifest is unrelated to this error.

Practice

1. What is the main purpose of signing an Android app in React Native?

easy

A. To make the app run faster on Android devices

B. To reduce the app's file size before publishing

C. To verify the app's author and ensure it hasn't been tampered with

D. To enable debugging features in the app

Solution

1. Step 1: Understand app signing purpose

   Signing an app proves who created it and ensures it is secure and unchanged.

2. Step 2: Compare options

   Only To verify the app's author and ensure it hasn't been tampered with describes verifying author and app integrity, which is the purpose of signing.

3. Final Answer:

   To verify the app's author and ensure it hasn't been tampered with -> Option C

4. Quick Check:

   App signing = Verify author and integrity [OK]

Hint: Signing proves app identity and security [OK]

Common Mistakes:

• Thinking signing makes app faster
• Confusing signing with debugging
• Believing signing reduces app size

2. Which command is used to generate a new keystore for signing an Android app?

easy

A. adb install my-app.apk

B. gradlew assembleRelease

C. react-native run-android

D. keytool -genkeypair -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000

Solution

1. Step 1: Identify keystore generation command

   The keytool command with -genkeypair creates a new keystore file for signing.

2. Step 2: Check other commands

   gradlew assembleRelease builds the app, react-native run-android runs debug build, and adb install installs APK; none generate keystore.

3. Final Answer:

   keytool -genkeypair -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000 -> Option D

4. Quick Check:

   Keystore generation = keytool command [OK]

Hint: Use keytool with -genkeypair to create keystore [OK]

Common Mistakes:

• Using gradlew to generate keystore
• Confusing build commands with keytool
• Trying to generate keystore with adb

3. Given the Gradle signing config snippet below, what will happen if the keystore password is incorrect?

signingConfigs {
  release {
    storeFile file('my-release-key.keystore')
    storePassword 'wrongpassword'
    keyAlias 'my-key-alias'
    keyPassword 'correctpassword'
  }
}

medium

A. The build will fail with a password error during signing

B. The app will build but signing will be skipped

C. The app will build and sign successfully

D. The build will succeed but app crashes on launch

Solution

1. Step 1: Understand password role in signing

   The storePassword must match the keystore password to access the key for signing.

2. Step 2: Effect of wrong password

   If the password is wrong, Gradle cannot access the keystore, causing the build to fail with an error.

3. Final Answer:

   The build will fail with a password error during signing -> Option A

4. Quick Check:

   Wrong keystore password = build failure [OK]

Hint: Wrong keystore password causes build failure [OK]

Common Mistakes:

• Assuming build skips signing on password error
• Thinking app runs despite signing failure
• Believing wrong password causes silent errors

4. You tried to build a signed APK but got this error: Execution failed for task ':app:signRelease'. What is the most likely cause?

medium

A. The keystore file path is incorrect or missing

B. The app's JavaScript code has syntax errors

C. You forgot to run npm install

D. The Android device is not connected

Solution

1. Step 1: Understand signRelease task

   This task signs the APK using the keystore; failure usually means signing config issues.

2. Step 2: Identify common signing errors

   Incorrect or missing keystore file path causes signing to fail; other options relate to unrelated issues.

3. Final Answer:

   The keystore file path is incorrect or missing -> Option A

4. Quick Check:

   signRelease error = keystore path problem [OK]

Hint: Check keystore file path if signing task fails [OK]

Common Mistakes:

• Blaming JavaScript errors for signing failure
• Thinking npm install fixes signing errors
• Assuming device connection affects build signing

5. You want to update your published app but lost your original keystore file. What is the best solution to continue updating your app on Google Play?

hard

A. Generate a new keystore and upload the app as a new app with a different package name

B. Create a new keystore and contact Google Play support to reset your key

C. Build the app without signing and upload it to Google Play

D. Use the debug keystore to sign the update

Solution

1. Step 1: Understand keystore importance for updates

   Google Play requires the same signing key to update an app; losing it blocks updates.

2. Step 2: Best recovery method

   Creating a new keystore and requesting Google Play support to reset your key is the official way to regain update ability.

3. Step 3: Why other options fail

   Uploading as new app changes package name, unsigned builds are rejected, and debug keystore is not allowed for release.

4. Final Answer:

   Create a new keystore and contact Google Play support to reset your key -> Option B

5. Quick Check:

   Lost keystore = new key + Google support [OK]

Hint: Lost keystore? Contact Google Play to reset key [OK]

Common Mistakes:

• Uploading unsigned or debug signed APK
• Publishing as new app instead of updating
• Ignoring Google Play key reset process