Replay or symbols are not working

Replay does not appear

Confirm that:

• the browser-only replay entry point is running;
• the project-scoped replay key has replay:write;
• input masking or application policy did not disable recording;
• chunks are not failing with 401, 403, 413, or 429;
• the selected project, environment, and time range are correct; and
• the customer ID and session ID match the surrounding browser telemetry.

Use browser network tools to inspect the replay chunk request without exposing the key or captured payload.

Replay has no backend evidence

Check that browser request tracing is enabled, the API origin is allowed for header propagation, and the backend extracts traceparent and trusted baggage. The replay can exist even when cross-tier correlation is broken.

JavaScript frames are not symbolicated

The SDK release and dist must exactly match the source-map upload. Confirm that the built artifact actually references the uploaded map and that CI did not rewrite paths after upload.

Android frames are obfuscated

Upload the exact mapping.txt produced by the failing build:

teml symbols upload-proguard mapping.txt --release "$RELEASE" --dist "$DIST"

iOS frames show addresses

Upload the dSYM from the archive that produced the installed application:

teml symbols upload-dsym App.dSYM/Contents/Resources/DWARF/App

The CLI accepts the Mach-O file containing DWARF symbols, not the .dSYM bundle directory. Rebuilding the same source can produce a different binary UUID; use the original archive artifact.

Verify with a release build

Development stacks often bypass minification or obfuscation. Trigger a safe test error from the same kind of release build used in production and confirm its release, distribution, and readable frames inside the Issue.

• Record session replay safely
• Capture errors and releases