Mobile App Development

Google Play Store Deployment Guide for React Native (Expo) App

Complete guide to publishing a React Native Expo app on Google Play Store — EAS AAB build, store listing, data safety form, content rating, privacy policy, and common rejection fixes.

By Published: Reading time: 8 min read Level: BEGINNER
Google Play Store deployment process for a React Native Expo mobile app

Publishing a jewellery e-commerce app on Google Play requires more than just uploading a binary — the store listing, content rating, data safety form, and release notes all have to be right before the review team approves it. This guide covers every step of the process end-to-end for a React Native (Expo) app.

Stack: React Native · Expo SDK 51+ · EAS Build · Google Play Console


Pre-Deployment Checklist

Before triggering any build, verify these items in your codebase:

Item What to check
console.log statements Remove all debug logs from production code
Navigation screens registered Every tab/screen must be in the navigator
Disabled features Comment out or feature-flag anything not ready
expo-notifications plugin Must be present in app.json plugins array
buildNumber / versionCode Both must start at "1" / 1 for a first upload
Feature graphic ready 1024×500 px PNG or JPG
Privacy Policy URL Must be a live, publicly accessible URL
Delete Account URL Required by both Google Play and Apple

Step 1 — Build the Production AAB

Install EAS CLI and log in

yarn global add eas-cli
eas login

Configure EAS (first time only)

eas build:configure

Build the Android App Bundle

eas build --platform android --profile production

AAB vs APK: Google Play requires an Android App Bundle (.aab) for new apps since August 2021. Never upload a raw APK to the Production track.

Your eas.json production profile must have:

{
  "build": {
    "production": {
      "autoIncrement": true,
      "android": {
        "buildType": "app-bundle"
      }
    }
  }
}

autoIncrement: true means EAS automatically increments versionCode for every new build — you never need to manually bump it.


Step 2 — Google Play Console Setup

2.1 Create the App

  1. Go to play.google.com/console
  2. Click "Create app"
  3. Fill in:
    • App name: your app's display name (max 30 chars)
    • Default language: English (India) or appropriate locale
    • App or game: App
    • Free or paid: Free
  4. Accept the Developer Program Policies → Create app

Step 3 — Store Listing

App Name (max 30 chars)

Keep it concise — this is what users see on the Home Screen after install.

Short Description (max 80 chars)

Summarise the core value proposition in one sentence. Example:

Shop exquisite gold & silver jewellery. Easy ordering, tracking & more.

Full Description (max 4000 chars)

Structure your description with:

  1. Opening hook — what problem you solve
  2. Key features — use bullet points with emoji for scannability
  3. Trust signals — certifications, security, support
  4. Call to action — "Download now and..."

For a jewellery e-commerce app, highlight:

  • Product catalogue depth (categories, metals, occasions)
  • Payment security (Razorpay, UPI, EMI)
  • Order tracking and after-sales support
  • Gold/silver rate calculator if available
  • Store locator if you have physical locations

Required Graphics

Asset Size Notes
App Icon 512×512 PNG No rounded corners — Play Console applies the mask
Feature Graphic 1024×500 PNG or JPG Shown at top of store listing
Phone screenshots Min 2, max 8 Take from emulator or physical device
Tablet screenshots Optional Recommended if your app supports tablets

Step 4 — App Content

4.1 Privacy Policy

Your privacy policy page must be publicly accessible (no login required) and must mention:

  • Camera access (if used for KYC or product photos)
  • Photo library access
  • Push notifications
  • Payment data handling (even if processed by a third-party gateway)
  • User account creation and deletion

Generators like privacypolicygenerator.info can create a starting template. Host it on your website or GitHub Pages.

4.2 Content Rating (IARC Questionnaire)

Navigate to Policy → App content → Content rating and answer:

Category Answer
Violence No
Sexual content No
Controlled substances No
Location shared with third parties No
Digital goods / in-app purchases Depends on app — answer honestly
Gift cards / rewards No (unless implemented)

Expected rating for a standard jewellery e-commerce app: Everyone (E)

4.3 Data Safety Form

This section is displayed prominently on your Play Store listing. Fill it accurately.

Data collected and purpose:

Data Type Collected Shared with 3rd Parties Purpose
Name Yes No Account creation
Phone number Yes No OTP login
Email address Yes No Account
Delivery address Yes No Order fulfilment
Photos / documents Yes (if KYC) No App functionality
Device ID (push token) Yes No Notifications
Purchase history Yes No Order tracking

Additional answers:

  • Encrypted in transit: Yes (all API calls use HTTPS)
  • Account creation method: Other → "Phone number with OTP verification"
  • Delete account support: Yes — provide the URL to your delete account page
  • Partial data deletion: No (deleting account removes all data)

4.4 Target Audience

  • Age group: 18 and older
  • Not directed at children: Confirm this

Step 5 — Upload AAB to Production Track

  1. Go to Release → Production
  2. Click "Create new release"
  3. Upload your .aab file from the EAS build dashboard
  4. Release name: 1.0.0 (1) — follows the pattern version (versionCode)
  5. Release notes (shown to users in "What's new"):
🎉 Welcome to [Your App Name]!

Browse and shop premium gold & silver jewellery from the comfort of your home.

• Browse thousands of jewellery designs
• Secure checkout via Razorpay (UPI, Cards, Net Banking, EMI)
• Real-time order tracking
• In-app store locator
• Gold & silver rate calculator
• Push notifications for offers & orders

Step 6 — Final Review & Submit

Check every section has a green tick:

  • Store listing complete (name, description, icon, screenshots, feature graphic)
  • Content rating completed and rating issued
  • Data safety form filled and submitted
  • Privacy policy URL added (live URL, not a placeholder)
  • Delete account URL added
  • Target audience set (18+)
  • AAB uploaded to Production track
  • Release notes added in at least one language

Submit:

  1. Save each section individually
  2. Go to Publishing overview
  3. Resolve any warnings shown
  4. Click "Send for review"

⏱️ Review time: Typically 1–3 business days for new apps. Expedited review is not available for new accounts.


Step 7 — After Approval

Once your app is live:

  • Monitor Android Vitals in Play Console for ANRs and crashes
  • Set up Firebase Crashlytics alerts so crash spikes notify your team immediately
  • Reply to user reviews — Google uses review response rate as a ranking signal
  • Plan your v1.1 release — ship the features you held back (e.g. DigiGold, Wallet) as a follow-up update once your base listing is established

Common Rejection Reasons for E-Commerce Apps

❌ Privacy policy URL is broken or behind a login

Fix: Host the policy on a public URL. Test it in incognito mode before submitting.

❌ Data safety form doesn't match actual app behaviour

Fix: If your app collects phone numbers for OTP, declare it. Play Console cross-checks this against your APK's permission requests.

❌ App requests READ_MEDIA_IMAGES without justification

Fix: Use expo-image-picker (Android Photo Picker on Android 13+) which doesn't require this permission. If you still need it, provide a detailed justification under Photo and video permissions.

❌ Missing delete account option

Fix: Both Google Play and Apple require apps with user accounts to offer in-app account deletion. Add a "Delete Account" button in your Settings screen and a corresponding web URL in the Data Safety form.

❌ Screenshots show placeholder or test data

Fix: Use real (or realistic demo) data in your screenshots. Reviewers check for consistency between screenshots and actual app behaviour.


Resources