Bird
Raised Fist0
React Nativemobile~10 mins

App Store submission in React Native - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define the app name in app.json for App Store submission.

React Native
{
  "expo": {
    "name": "[1]",
    "slug": "my-app"
  }
}
Drag options to blanks, or click blank then click option'
AMyCoolApp
BMy App!
Capp_name
D123App
Attempts:
3 left
💡 Hint
Common Mistakes
Using special characters like exclamation marks.
Starting the name with numbers.
Using underscores instead of spaces.
2fill in blank
medium

Complete the code to set the iOS bundle identifier in app.json for App Store submission.

React Native
{
  "expo": {
    "ios": {
      "bundleIdentifier": "com.example.[1]"
    }
  }
}
Drag options to blanks, or click blank then click option'
Amy_app
BMy App
Cmyapp
D123app
Attempts:
3 left
💡 Hint
Common Mistakes
Including spaces in the bundle identifier.
Using uppercase letters.
Starting with numbers.
3fill in blank
hard

Fix the error in the app.json snippet to correctly specify the app version for App Store submission.

React Native
{
  "expo": {
    "version": "[1]"
  }
}
Drag options to blanks, or click blank then click option'
Aversion1
B1.0
Cv1.0.0
D1.0.0
Attempts:
3 left
💡 Hint
Common Mistakes
Using only two numbers like 1.0.
Adding 'v' or text before the version number.
4fill in blank
hard

Fill both blanks to set the correct app icon and splash screen image paths in app.json.

React Native
{
  "expo": {
    "icon": "[1]",
    "splash": {
      "image": "[2]"
    }
  }
}
Drag options to blanks, or click blank then click option'
A./assets/icon.png
B./assets/splash.png
C./assets/icon.jpg
D./assets/splash.jpg
Attempts:
3 left
💡 Hint
Common Mistakes
Using JPG files instead of PNG.
Incorrect file paths.
5fill in blank
hard

Fill all three blanks to configure the iOS build number, supportsTablet flag, and app category in app.json.

React Native
{
  "expo": {
    "ios": {
      "buildNumber": "[1]",
      "supportsTablet": [2],
      "bundleIdentifier": "com.example.myapp",
      "infoPlist": {
        "CFBundleCategory": "[3]"
      }
    }
  }
}
Drag options to blanks, or click blank then click option'
A42
Btrue
Cpublic.app-category.utilities
Dfalse
Attempts:
3 left
💡 Hint
Common Mistakes
Using numbers instead of strings for buildNumber.
Using strings instead of booleans for supportsTablet.
Incorrect category identifiers.

Practice

(1/5)
1. What is the main purpose of submitting a React Native app to the App Store?
easy
A. To make the app available for millions of iOS users
B. To test the app only on your local device
C. To convert the app into a web application
D. To automatically fix all app bugs

Solution

  1. Step 1: Understand App Store submission goal

    Submitting an app to the App Store allows it to be published and accessible to iOS users worldwide.
  2. Step 2: Eliminate incorrect options

    Testing locally, converting to web, or auto-fixing bugs are not purposes of submission.
  3. Final Answer:

    To make the app available for millions of iOS users -> Option A
  4. Quick Check:

    App Store submission = Publish app [OK]
Hint: App Store submission means publishing app for users [OK]
Common Mistakes:
  • Thinking submission is only for testing
  • Confusing app publishing with app conversion
  • Assuming submission fixes bugs automatically
2. Which tool is essential for submitting a React Native app to the Apple App Store?
easy
A. Android Studio
B. Expo Go
C. Visual Studio Code
D. Xcode

Solution

  1. Step 1: Identify Apple-specific submission tools

    Xcode is Apple's official tool for building and submitting iOS apps.
  2. Step 2: Remove unrelated tools

    Android Studio is for Android apps, VS Code is a code editor, Expo Go is for testing but not submission.
  3. Final Answer:

    Xcode -> Option D
  4. Quick Check:

    Apple app submission requires Xcode [OK]
Hint: Use Xcode for iOS app submission, not Android Studio [OK]
Common Mistakes:
  • Choosing Android Studio for iOS app submission
  • Confusing code editors with submission tools
  • Thinking Expo Go submits apps to App Store
3. Consider this React Native app submission step: You archive your app in Xcode and upload it to App Store Connect. What happens next?
medium
A. Apple reviews the app before it appears on the store
B. The app is immediately live on the App Store
C. The app is automatically rejected
D. The app is converted to Android format

Solution

  1. Step 1: Understand the submission workflow

    After uploading, Apple reviews the app to ensure it meets guidelines.
  2. Step 2: Clarify incorrect options

    The app is not live immediately, not automatically rejected, and not converted to Android.
  3. Final Answer:

    Apple reviews the app before it appears on the store -> Option A
  4. Quick Check:

    App Store review happens after upload [OK]
Hint: App Store review happens before app goes live [OK]
Common Mistakes:
  • Assuming instant app availability after upload
  • Thinking Apple rejects all apps automatically
  • Confusing iOS and Android app processes
4. You submitted your React Native app but it was rejected due to missing app screenshots. What should you do to fix this?
medium
A. Change the app name and resubmit
B. Add required screenshots in App Store Connect and resubmit
C. Delete the app from Xcode and start over
D. Ignore the rejection and submit again

Solution

  1. Step 1: Identify the rejection cause

    Missing screenshots means Apple needs images showing app usage.
  2. Step 2: Correct the submission details

    Add the required screenshots in App Store Connect, then resubmit for review.
  3. Final Answer:

    Add required screenshots in App Store Connect and resubmit -> Option B
  4. Quick Check:

    Fix rejection by adding missing info [OK]
Hint: Add all required assets before resubmitting [OK]
Common Mistakes:
  • Ignoring rejection reasons
  • Deleting app unnecessarily
  • Changing unrelated app details
5. You want to submit a React Native app with a new feature that requires user location. What must you include in your App Store submission to avoid rejection?
hard
A. Only mention location use in the app code comments
B. No description is needed if the feature is optional
C. A clear privacy description explaining why location is needed
D. Disable location permissions to avoid review issues

Solution

  1. Step 1: Understand Apple's privacy requirements

    Apple requires apps to provide a clear privacy description for sensitive data like location.
  2. Step 2: Identify correct submission practice

    Include a privacy usage description in App Store Connect to explain why location is needed.
  3. Step 3: Avoid incorrect practices

    Ignoring description, hiding info in code, or disabling permissions are not acceptable.
  4. Final Answer:

    A clear privacy description explaining why location is needed -> Option C
  5. Quick Check:

    Privacy description required for sensitive data [OK]
Hint: Always add privacy usage descriptions for sensitive features [OK]
Common Mistakes:
  • Skipping privacy descriptions
  • Thinking optional features don't need explanations
  • Hiding info only in code comments
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard