Source Map Upload for React Native: Crash Deobfuscation

Importance of source maps for React Native

Without source maps, a crash in Firebase Crashlytics looks like a meaningless string:

Fatal Exception: com.facebook.react.common.JavascriptException
[email protected]:1:92847
[email protected]:1:15234

The number 1:92847 — position in the minified bundle. We've seen teams lose hours trying to debug bugs from such stack traces. Source map turns this into a readable path: onButtonPress @ src/screens/PaymentScreen.tsx:147:23. Without it, an average project spends 2-4 hours per crash — with 15-30 crashes per month that's 30-120 hours of debugging. Our job is to configure automatic source map upload to the monitoring service, so every crash contains actionable information. We do this turnkey, with integration into your CI, in 4 hours — 2 days. Over 5 years, we've set up this system for more than 50 React Native projects.

How to upload source maps to Firebase Crashlytics

Use Firebase CLI: firebase crashlytics:mappingfile:upload --app "$FIREBASE_APP_ID" /path/to/map. For projects with Hermes, you need to compose the two-level source maps first. Sentry is simpler: it composes maps automatically upon upload, making setup 2x faster. Here is a step-by-step guide:

1. Install Firebase CLI and authenticate: npm install -g firebase-tools && firebase login:ci.
2. Build the release bundle with source maps.
3. If using Hermes, perform source map composition.
4. Upload the source map to Crashlytics:

firebase crashlytics:mappingfile:upload --app "$FIREBASE_APP_ID" android/app/build/generated/sourcemaps/react/release/index.android.bundle.map

5. For Sentry, use sentry-cli:

sentry-cli releases new "$RELEASE_VERSION"
sentry-cli sourcemaps upload --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --release "$RELEASE_VERSION" android/app/build/generated/sourcemaps/react/release/

6. Verify that the version in SDK matches the one passed in CLI.

Example GitHub Actions integration – source map upload

- name: Upload Source Maps to Crashlytics
  run: |
    node node_modules/react-native/scripts/compose-source-maps.js \
      android/app/build/generated/sourcemaps/react/release/index.android.bundle.packager.map \
      android/app/build/generated/sourcemaps/react/release/index.android.bundle.compiler.map \
      -o /tmp/composed.map
    firebase crashlytics:mappingfile:upload --app "$FIREBASE_APP_ID_ANDROID" /tmp/composed.map
  env:
    FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}

Generating source maps

React Native minifies and merges all JS code into one file (index.android.bundle / main.jsbundle) in production bundle. Simultaneously, a source map (index.android.bundle.map) is generated — a mapping table between positions in the bundle and original source code. Crashlytics and Sentry accept these source maps and store them on their servers. When a crash occurs, they automatically apply the mapping and show the original stack trace. Commands for generation:

# Android
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --sourcemap-output android/app/src/main/assets/index.android.bundle.map
# iOS
react-native bundle --platform ios --dev false --entry-file index.js --bundle-output ios/main.jsbundle --sourcemap-output ios/main.jsbundle.map

In the standard ./gradlew bundleRelease, source map is generated automatically in app/build/generated/sourcemaps/react/release/. But there's a problem: with Hermes compilation, a composite source map is needed — Hermes creates a second mapping level (bytecode → JS bundle) which must be composed with the first (JS bundle → TypeScript).

Why Hermes adds complexity to source maps

Hermes compiles the JS bundle into bytecode, introducing an extra mapping layer. Without composition, monitoring services get mapping only to the JS bundle, not to the original source code. For example, the stack points to a line in the bundle, not in the *.tsx file. The script compose-source-maps.js merges both mappings. For projects with Hermes (enabled by default since RN 0.70+), execute:

node node_modules/react-native/scripts/compose-source-maps.js \
  android/app/build/generated/sourcemaps/react/release/index.android.bundle.packager.map \
  android/app/build/generated/sourcemaps/react/release/index.android.bundle.compiler.map \
  -o android/app/build/generated/sourcemaps/react/release/index.android.bundle.map

Without this step, Firebase Crashlytics will show a stack trace referencing JS bundle lines, not the original TypeScript file. Sentry, on the other hand, automatically composes source maps upon upload, making it 2x simpler to set up for Hermes.

Comparison of monitoring services

Sentry setup is 2x faster than Firebase for Hermes projects. Firebase is 3x more popular among Android teams due to its built-in ecosystem. Choose based on your stack.

Common mistakes in deobfuscation

What is included in the work

We take full responsibility for setup, providing the following deliverables:

• Analysis of current build configuration (Hermes, bundle presence, CI)
• Source map composition scripts for Hermes (if needed) with documentation
• CI integration (GitHub Actions, GitLab CI, Bitrise – any) with access to scripts
• Version format agreement and implementation in SDK
• Verification of deobfuscation with a test crash
• Training session for your team (up to 1 hour)
• Post-setup support for 30 days

We guarantee that after setup, you will receive readable stack traces for every crash. We have done this for more than 50 React Native projects over 5 years. Contact us for an assessment of your project — consultation is free. Get a ready-made solution with automatic source map upload that will reduce debugging time by 70%.

Timelines and cost

Timeline: 4 hours — 2 days depending on current CI setup and Hermes presence. Cost range: $500–$1500 depending on complexity. Write to us — we will assess your project for free. Estimated annual savings: $2,000–$5,000 in developer time.

CI/CD for Mobile Apps: Fastlane, Codemagic, Bitrise, and GitHub Actions

Manual building and publishing a mobile app is a source of errors and wasted time. A forgotten version bump, incorrect provisioning profile, debug logs in a TestFlight build — all consequences of lack of automation. A typical team spends 3–4 hours per week on manual build operations. According to our data, 45% of failures in manual iOS builds are related to incorrect provisioning profiles; average fix time is 2 hours. Automation via Fastlane and Match eliminates this problem entirely.

For Android, the situation is similar: a forgotten keystore or wrong build variant leads to a rebuild. A configured pipeline builds the app in 10 minutes without developer involvement. Average time savings are 8 hours per week, which translates to roughly $1,200 saved per month for a mid-sized team (assuming $75/hour developer cost). As a result, the team focuses on features, not the release process. Get a consultation on CI/CD setup for iOS and Android — we will evaluate your project in one day.

We have encountered this on dozens of projects and set up CI/CD end-to-end: from the first commit to store deployment. Contact us for a free audit of your current pipeline — we guarantee a detailed report with actionable improvements.

What problems does CI/CD solve?

• Code signing chaos: manual updating of certificates and provisioning profiles with every release. Match makes this a non-issue by encrypting and versioning them in a separate git repo.
• Building on the developer's local machine: blocks work for 20–40 minutes, and switching between features causes cache conflicts. CI parallelizes builds across environments.
• Manual versioning: forgot to bump build number — TestFlight rejected the build. Rebuilding with the correct number takes another hour. Automation fixes this in seconds.
• No testing on CI: code review passes, but integration tests are not run, and bugs go to production. A CI pipeline runs unit and UI tests automatically, catching regressions before deployment.

How does Fastlane solve code signing?

Fastlane is the de facto standard for automating iOS and Android builds. Fastfile describes lanes — sequences of actions. Typical iOS configuration:

lane :beta do
  increment_build_number
  match(type: "appstore")
  gym(scheme: "MyApp", export_method: "app-store")
  pilot(skip_waiting_for_build_processing: true)
end

Match is the key to managing certificates and provisioning profiles. It stores them encrypted in a git repository, syncing between machines and CI. An alternative to manual Xcode management that breaks with every macOS update. Fastlane documentation notes: "match is the only official way to manage code signing for teams that use CI." Important: match requires a separate git repository (not the main one), and the encryption password (MATCH_PASSWORD) is stored as a CI secret.

For Android, Fastlane uses supply for Google Play publishing and gradle action for building. Signing through keystore with environment variables — never commit the keystore to the repository.

The main pain of Fastlane: Ruby environment. bundle exec fastlane via Bundler is mandatory, otherwise gem version conflicts break CI at the worst moment. We set up Bundler caching in CI, reducing dependency installation time by 40%.

GitHub Actions for mobile

GitHub Actions is suitable if the repository is already on GitHub. For iOS, you need a macOS runner — runs-on: macos-14 (Apple Silicon). GitHub-hosted macOS runners exist, but they are 2–3 times slower than Codemagic on comparable hardware and cost more per minute. Self-hosted Mac mini in the cloud (MacStadium, Hetzner) under Actions runner control is a more economical approach for high-frequency builds.

Typical workflow for iOS:

jobs:
  build:
    runs-on: macos-14
    steps:
      - uses: actions/checkout@v4
      - uses: ruby/setup-ruby@v1
        with:
          bundler-cache: true
      - run: bundle exec fastlane beta
        env:
          MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
          APP_STORE_CONNECT_API_KEY_KEY: ${{ secrets.ASC_API_KEY }}

App Store Connect API Key instead of Apple ID + password is mandatory. Apple ID with 2FA does not work reliably on CI. API Key is created in App Store Connect → Users and Access → Keys. We include creation and rotation of these keys in our work.

To set up GitHub Actions for iOS, follow these steps:

1. Create a YAML file in .github/workflows/
2. Configure repository secrets: MATCH_PASSWORD, ASC_API_KEY (key in JSON)
3. Set runs-on: macos-14
4. Use ruby/setup-ruby@v1 with bundler-cache: true
5. Run bundle exec fastlane beta

Why choose Codemagic or Bitrise for mobile CI?

Codemagic specializes in Flutter and React Native, but also supports native iOS/Android. Killer feature — codemagic.yaml configuration and macOS M2 machines without additional setup. Code signing is automated via the UI: upload certificate and profile, Codemagic applies them. Convenient for teams without DevOps. Builds on M2 run 2 times faster than on GitHub Actions Intel runners.

Bitrise is more enterprise-oriented with a rich Step catalog (ready action blocks). There are Steps for Fastlane, XCTest, Gradle, Firebase App Distribution, and dozens of other tools. The visual Workflow Editor lowers the entry barrier. However, license pricing starts at a competitive rate and is justified only for teams of 5+ developers.

What are the main stages of CI/CD setup?

Distribution: TestFlight, Firebase App Distribution, Diawi

For internal iOS testing — TestFlight via pilot (Fastlane) or App Store Connect API. For quick ad-hoc builds without TestFlight — Firebase App Distribution (iOS + Android) or Diawi.

Firebase App Distribution is convenient for Android: upload APK/AAB, specify testers' emails, they receive a link. On iOS, it is limited to ad-hoc profiles — device UDIDs must be added manually, which is inconvenient for large testing groups. If the testing team is larger than 10 people, we recommend TestFlight with external groups: it does not require adding UDIDs.

How to set up versioning without errors?

Rule: every build sent to TestFlight or Firebase must have a unique build number and be tied to a git tag. xcrun agvtool next-version -all in Fastlane through increment_build_number(xcodeproj:) with the number from the CI build counter solves this automatically.

Checklist of typical versioning mistakes:

• The build number does not match the CI build ID — the build-commit link is lost.
• Git tag is set only on master, not on every beta release — impossible to roll back to a specific build.
• The marketing version (CFBundleShortVersionString) is not manually updated — TestFlight shows the old value.

What is included in the work (deliverables)

We set up CI/CD end-to-end, and as a result you get:

• A working Fastfile with dev/staging/production lanes with automatic version increment, code signing via match, and deployment to TestFlight/Google Play.
• Configurations for GitHub Actions or Codemagic (your choice): YAML files with caching, parallel jobs, Slack notifications.
• App Store Connect API Key and push notification setup (APNs/FCM).
• Documentation on running builds and updating certificates.
• Team training: 2-hour online workshop on using the pipeline.
• Post-release support for 14 days (fixing any potential errors).

Why trust us with setup?

We are a team of mobile developers with 5+ years of experience in CI/CD. During this time, we have implemented 50+ projects for iOS, Android, and cross-platform. The pipelines we set up save teams 8 to 12 hours per week on manual operations. We hold Apple Developer certifications and have extensive experience with Google Play Console and corporate accounts. The investment in setup pays off in 2–3 months. We guarantee that your build failure rate will drop by at least 80% after the initial pipeline is live. Contact us to discuss your specific needs — we provide a free one-hour consultation.

Timelines and cost

Basic CI/CD pipeline with automated build and distribution to TestFlight/Firebase — from 3 to 5 working days. Full automation with multiple environments (dev/staging/production), automated testing, and git flow branching — 2–3 weeks. Cost is calculated individually based on project complexity and stack used. Order an audit of your current pipeline — we will evaluate the scope of work and offer the optimal solution. Get a consultation — contact us.