Fictura
Error tracking

Source maps

Turn minified release stacks into the files, lines and function names you wrote.

A release build of a React Native app runs a minified Hermes bundle, so its crashes read at anonymous (address at main.jsbundle:1:9024). Upload the build's source map and the same crash reads at renderPrice (app/paywall/Price.tsx:12:7): on the issue page, in alerts, and in the MCP get_error_issue tool your coding agent uses.

How a crash finds its map

Expo gives every exported bundle a debug id and writes it into the bundle's source map. The Fictura Metro wrapper makes the running app report that id with each error, and the upload command stores each map under the same id. No release names to keep in sync.

Set it up

  1. Wrap Metro (metro.config.js):

    const { getFicturaExpoConfig } = require("@fictura/sdk/metro");
    module.exports = getFicturaExpoConfig(__dirname);

    Already calling getDefaultConfig? Use withFictura(config). Using Sentry's getSentryExpoConfig? Pass ficturaDebugIdPlugin in its unstable_beforeAssetSerializationPlugins.

  2. Create an upload token: Setup → Keys & webhook → Data API keys → a key with Upload source maps (sourcemaps:upload). Store it in CI as FICTURA_UPLOAD_TOKEN. Never use the app's publishable key; it ships inside the app.

  3. Upload after each build:

    npx expo export --source-maps --output-dir dist
    eas update --skip-bundler --branch production --message "…"
    npx fictura-sdk upload-sourcemaps dist --api-base https://<your Fictura API> --release 2.0.68

    Native Xcode and Gradle builds lose the debug id when they compose the Hermes map. The SDK README ("Readable stacks") has the build phase for iOS (--bundle) and the inject-debug-id step for Android.

What you see

  • Resolved stacks. The issue page opens on the resolved stack, your own frames highlighted and library frames folded, with a switch back to the raw stack exactly as the device sent it.
  • Grouping on your code. A crash whose map is already uploaded is grouped on its resolved frames, so the same bug thrown from two places in one function stays one issue.
  • Late maps. Upload after the crashes arrived and the last 7 days of that build's events are resolved in the background. They stay in the issue they were first grouped into.
  • Missing map. An event from a build with no uploaded map shows a Missing source map badge, and Issues → Source maps lists those builds.
  • Retention. Maps nobody used for 90 days are deleted.

On this page