Crashlytics是否支持React Native生产环境？Release包错误定位及Source Map咨询

Hey there! Let's tackle your questions one by one and get your Crashlytics setup sorted for your React Native app:

First off, the clear answers:

• Yes, Crashlytics fully supports React Native apps in production environments — it’s built specifically to capture and report crashes from live, user-facing apps, so production use cases are well-covered.
• Fabric Crashlytics does support React Native Release APKs (and iOS Release IPAs too). While Google has officially migrated Fabric to Firebase Crashlytics, existing Fabric integrations will still work reliably with your React Native release builds. That said, for long-term support, you might want to consider migrating to Firebase Crashlytics eventually, but your current setup is totally valid for release builds.

The issue you’re seeing (no original filenames in crash reports) happens because React Native minifies and bundles your JS code in release mode. To get readable stack traces that point back to your actual files, you need to generate and upload a source map that maps the minified code to your original source. Here’s how to set this up for both Android and iOS:

Android Setup Steps #

1. Generate the Release Bundle and Source Map #

Run this command from your project root to create the bundled JS and corresponding source map:

react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/ --sourcemap-output android/app/build/generated/sourcemaps/react/release/index.android.bundle.map

Then build your Release APK as usual:

cd android && ./gradlew assembleRelease

2. Upload the Source Map to Fabric Crashlytics #

You can do this either via the Fabric CLI or configure Gradle to auto-upload during builds:

• Using Fabric CLI:

  crashlyticsUploadSymbolsRelease --android --sourceMap android/app/build/generated/sourcemaps/react/release/index.android.bundle.map --bundle android/app/src/main/assets/index.android.bundle
  

• Auto-upload via Gradle:
  Add this to your android/app/build.gradle inside the release build type block:

  buildTypes {
      release {
          // ... your existing release config
          crashlytics {
              enableNdk true
              mappingFileUploadEnabled true // Enables auto-upload of source maps
          }
      }
  }
  

  Make sure you already have the Fabric Gradle plugin added to your project's build files.

iOS Setup Steps #

1. Generate the Release Bundle and Source Map #

From your project root, run:

react-native bundle --platform ios --dev false --entry-file index.js --bundle-output ios/main.jsbundle --assets-dest ios --sourcemap-output ios/main.jsbundle.map

Then build your Release IPA via Xcode (Archive > Distribute App) or using the command line:

xcodebuild -workspace YourApp.xcworkspace -scheme YourApp -configuration Release -archivePath ./build/YourApp.xcarchive archive

2. Upload the Source Map to Fabric Crashlytics #

Again, two options here:

• Using Fabric CLI:

  crashlyticsUploadSymbolsRelease --ios --sourceMap ios/main.jsbundle.map --bundle ios/main.jsbundle
  

• Auto-upload via Xcode Build Phase:
  1. Open your Xcode project, select your app target, go to Build Phases
  2. Click the + button and select New Run Script Phase
  3. Paste this script into the phase:

  "${PODS_ROOT}/Fabric/run"
  # Upload source map for React Native
  node node_modules/react-native/scripts/crunchify.js ios/main.jsbundle ios/main.jsbundle.map
  

  Ensure you have the Fabric pod installed in your project and your Info.plist includes your Fabric API Key and Build Secret.

Key Notes #

• Always generate and upload the source map every time you build a new release — each release has a unique minified bundle, so the source map must match exactly.
• Check the Fabric dashboard's "Uploads" section to confirm your source maps were successfully uploaded (failed uploads are a common culprit for missing filenames).

内容的提问来源于stack exchange，提问作者ramesh m