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.