Fictura
Error tracking

Native crashes

Native crashes, ANRs, out-of-memory kills and app hangs, read from what Android and iOS recorded, with readable native stacks.

JavaScript errors are only part of what users hit. A native crash, an ANR, an out-of-memory kill or a watchdog termination ends the app with no JavaScript running. @fictura/sdk 0.22 reads what the operating system recorded about the last run on the next launch and reports each one as an issue, next to your JS errors.

What is reported

PlatformSourceIssues
Android 11+the system's exit records (ApplicationExitInfo)native crashes (signal, abort message and the crashing thread, Android 12+), ANRs (the main thread first), JVM crashes, out-of-memory kills in the foreground, initialization failures, kills for excessive resource use
iOS 14+MetricKit diagnosticscrashes (exception type and code, signal, termination reason, memory region, the call stack tree), watchdog terminations, app hangs with their duration

The SDK installs no signal or exception handler, so it runs safely next to Sentry. It needs the SDK's native module in the build: a development or store build after npx expo prebuild (not Expo Go). Turn it off with enableNativeCrashReporting: false.

Release health

Each report names the session that died: on Android the app hands its session id to the system, which returns it with the exit record; otherwise the process id is matched against recent runs. That session counts as crashed in release health, not only as abnormal. A JS crash that already reported itself is not counted twice.

Readable native stacks

Upload symbols after each store build, with the same upload token as source maps:

# iOS: the symbol table of each binary in the build's dSYMs (macOS with Xcode installed)
npx fictura-sdk upload-dsym ios/build --api-base https://<your Fictura API>

# Android: the R8 / ProGuard mapping of the build
npx fictura-sdk upload-mapping android/app/build/outputs/mapping/release/mapping.txt \
  --app-id <applicationId> --version-code <versionCode> --api-base https://<your Fictura API>
  • iOS. Only the binary's symbol table is uploaded, never the debug information. Frames read ContentView.body.getter + 16 instead of MyApp + 0x4010; file and line numbers are not shown.
  • Android. ANR and crash traces are deobfuscated: classes, methods, inlined calls and line numbers.
  • Late uploads. Crashes from the last 7 days are symbolicated when the symbols arrive, up to 500 per upload. They stay in the issue they were first grouped into.
  • Missing symbols. A crash whose build has none shows a Missing native symbols badge, and Issues → Source maps lists the builds waiting for symbols with the command that uploads them.

Performance

With the native module in the build, the app-start span begins when the system started the process, screen-load spans carry slow and frozen frame counts, and Growth.reportFullyDisplayed() records time to full display for a screen (a paywall with its prices loaded). See the SDK README, "Native performance".

On this page