Play Store submission in React Native - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Play Store App Signing

Which of the following best describes the purpose of app signing in the Play Store submission process?

A It removes unused code to optimize performance.

B It compresses the app to reduce download size.

C It automatically translates the app to multiple languages.

D It verifies the identity of the app developer and ensures app integrity.

💡 Hint

Think about security and trust when users download apps.

App signing uses a digital certificate to confirm the app comes from the developer and hasn't been tampered with.

❓ ui_behavior

intermediate

Play Store Listing Requirements

Which of these is NOT required when creating a Play Store listing for your React Native app?

A App screenshots showing the app interface.

B The source code of your app.

C A privacy policy URL if your app collects user data.

D A short and full description of the app.

💡 Hint

Think about what users and Google need to see, not what developers share.

Google Play requires screenshots, descriptions, and privacy policy but not the app's source code.

❓ lifecycle

advanced

Handling Version Codes in Play Store Submission

You have submitted versionCode 5 of your React Native app to the Play Store. What happens if you try to upload an APK or AAB with versionCode 4?

A The Play Store accepts it but users will not receive updates.

B The Play Store accepts it and replaces versionCode 5 with 4.

C The Play Store rejects the upload because versionCode must increase with each release.

D The Play Store automatically increments the versionCode to 6.

💡 Hint

Think about how updates should always move forward, not backward.

Play Store requires each new upload to have a higher versionCode than previous ones to avoid confusion.

❓ navigation

advanced

Play Store Release Tracks Usage

Which Play Store release track allows you to test your React Native app with a small group of users before a full public release?

A Closed testing track

B Production track

C Beta testing track

D Internal testing track

💡 Hint

Consider which track limits access to a specific group rather than everyone.

Closed testing lets you release your app to a limited group for feedback before wider release.

🔧 Debug

expert

Troubleshooting Play Store Submission Errors

You receive this error when uploading your React Native app bundle: "Upload failed: Your app bundle is missing the required native debug symbols." What is the most likely cause?

A You did not generate or include the native debug symbols (mapping files) during build.

B Your app bundle size exceeds the Play Store limit.

C You forgot to increment the versionName in build.gradle.

D Your app icon does not meet Play Store size requirements.

💡 Hint

Debug symbols help with crash reporting and must be included in the upload.

Native debug symbols are needed for Play Store to process crash reports; missing them causes upload failure.

Practice

1. What is the first step to submit a React Native app to the Google Play Store?

easy

A. Test the app only on iOS devices

B. Upload the debug APK to Google Play Console

C. Build a signed release version of your app

D. Publish the app without signing

Solution

1. Step 1: Understand Play Store submission requirements

   The Play Store requires a signed release version for app submission, not a debug build.

2. Step 2: Identify the correct first step

   Building a signed release APK or AAB is the first essential step before uploading.

3. Final Answer:

   Build a signed release version of your app -> Option C

4. Quick Check:

   Signed release build = first step [OK]

Hint: Always create a signed release build before upload [OK]

Common Mistakes:

• Uploading debug APK instead of release
• Skipping app signing
• Trying to publish without building

2. Which command correctly generates a signed Android app bundle for Play Store in React Native?

easy

A. npx react-native run-android --variant=release

B. cd android && ./gradlew bundleRelease

C. npm start --release

D. react-native build --signed

Solution

1. Step 1: Recall React Native Android build commands

   The correct command to build a signed app bundle is running Gradle wrapper with bundleRelease task inside android folder.

2. Step 2: Match commands to their purpose

   cd android && ./gradlew bundleRelease runs the Gradle task to create the release bundle; others are incorrect or incomplete.

3. Final Answer:

   cd android && ./gradlew bundleRelease -> Option B

4. Quick Check:

   Gradle bundleRelease builds signed app bundle [OK]

Hint: Use Gradle commands inside android folder for release builds [OK]

Common Mistakes:

• Using run-android which builds debug by default
• Trying npm start for release builds
• Using non-existent react-native build command

3. Given this snippet in android/app/build.gradle:

signingConfigs {
    release {
        storeFile file("my-release-key.keystore")
        storePassword "password"
        keyAlias "my-key-alias"
        keyPassword "password"
    }
}

buildTypes {
    release {
        signingConfig signingConfigs.release
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

What will happen if you run ./gradlew assembleRelease?

medium

A. A signed release APK will be generated using the specified keystore

B. The build will fail due to missing signingConfig

C. A debug APK will be generated instead

D. The app bundle will be generated, not APK

Solution

1. Step 1: Analyze signingConfigs and buildTypes

   The release build type uses the signingConfig named release, which is properly defined with keystore info.

2. Step 2: Understand assembleRelease behavior

   Running assembleRelease builds a signed APK using the release signingConfig, so a signed APK is generated.

3. Final Answer:

   A signed release APK will be generated using the specified keystore -> Option A

4. Quick Check:

   assembleRelease + signingConfig = signed APK [OK]

Hint: assembleRelease uses signingConfig to create signed APK [OK]

Common Mistakes:

• Confusing assembleRelease with debug build
• Assuming app bundle is generated by assembleRelease
• Missing signingConfig causes build failure

4. You tried uploading your React Native app bundle to Google Play Console but got an error: "App signing key not found." What is the most likely cause?

medium

A. You forgot to generate and configure the signing key before building

B. You uploaded a debug build instead of release

C. You used the wrong package name in AndroidManifest.xml

D. You did not enable internet permission in the app

Solution

1. Step 1: Understand the error message

   "App signing key not found" means the Play Console expects a signing key but it was missing or not configured.

2. Step 2: Identify common causes

   Most often, this happens if you did not generate or configure the signing key before building the release bundle.

3. Final Answer:

   You forgot to generate and configure the signing key before building -> Option A

4. Quick Check:

   Missing signing key causes upload error [OK]

Hint: Always generate and configure signing key before building release [OK]

Common Mistakes:

• Uploading debug build instead of release
• Ignoring package name mismatches
• Confusing permissions with signing errors

5. You want to submit your React Native app to the Play Store with these conditions: - Use Android App Bundle (.aab) - Enable ProGuard for code shrinking - Use a custom signing key Which steps must you perform in correct order?

hard

A. Enable ProGuard, upload unsigned bundle, then configure signingConfigs

B. Run ./gradlew assembleDebug, upload debug APK, then enable ProGuard

C. Upload unsigned APK, then configure signingConfigs and ProGuard later

D. Configure signingConfigs with your key, enable ProGuard in buildTypes, run ./gradlew bundleRelease, then upload the .aab

Solution

1. Step 1: Configure signingConfigs and ProGuard

   You must first set your custom signing key in signingConfigs and enable ProGuard in the release buildType.

2. Step 2: Build the Android App Bundle

   Run ./gradlew bundleRelease to create the signed, optimized .aab file.

3. Step 3: Upload the .aab to Google Play Console

   Finally, upload the generated .aab file to submit your app.

4. Final Answer:

   Configure signingConfigs with your key, enable ProGuard in buildTypes, run ./gradlew bundleRelease, then upload the .aab -> Option D

5. Quick Check:

   Sign key + ProGuard + bundleRelease + upload = correct flow [OK]

Hint: Set signing and ProGuard before building bundle for Play Store [OK]

Common Mistakes:

• Uploading debug or unsigned builds
• Building APK instead of app bundle
• Configuring signing after upload