Repository navigation
[simplex, simplex-desktop]: report errors to Sentry - #1399
Merged
Merged
Conversation
The web UI (@sentry/react) and the desktop main process (@sentry/electron) report errors when CI bakes a DSN into the build. Events are scrubbed of recovery phrases, keys, long tokens and provider URL paths before sending. Operators opt out with SIMPLEX_ERROR_REPORTING=off: /health tells the UI to drop events, and the desktop skips Sentry and keeps it out of the renderer CSP. UI source maps are uploaded in CI and deleted from dist.
Renderer, GPU and utility process crashes and OOMs are sent as events. An unexpected solver stop is reported where the desktop already notifies the operator. A running-session marker in userData reports a main process that ended without a clean quit on the next launch, ignoring sessions that an OS shutdown or restart ended.
Gate SDK initialization because session envelopes bypass beforeSend. Scrub mixed-case and structured recovery phrases, absolute file paths, and cyclic data. Enable source maps in an entry module before loading the desktop main bundle.
ddboy19912
marked this pull request as ready for review
October 14, 2026 13:07
Contributor
Author
|
@seunlanlege I've already set up the projects on Sentry and updated the Secrets/Variables |
seunlanlege
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Sentry error reporting to the Simplex web UI and Desktop main process in release builds. CI bakes in the DSNs; local builds, unsigned validation builds, and Docker images send nothing.
SIMPLEX_ERROR_REPORTING=offdisables reporting. The web UI waits for solver/healthpermission before initializing any Sentry integration, including sessions. Failed probes leave reporting inactive. Desktop skips initialization and excludes Sentry from the renderer CSP.@hyperbridge/simplex/error-reportingmodule strips recovery phrases regardless of case, including serialized and structured word arrays; key material and long tokens; absolute Windows, UNC, and POSIX paths; and remote URL paths and queries. Request bodies, cookies, and headers other than User-Agent are removed. Stack frames and grouping identifiers remain intact.dist/bootstrap.js, which enables source maps before loadingmain.js; its map ships in the app.Operator documentation:
evm/simplex/configuration.mdx. Feature note:docs/ai/changelog/2026-10-14-simplex-sentry-error-reporting.md.Required repository configuration
SIMPLEX_UI_SENTRY_DSN,SIMPLEX_DESKTOP_SENTRY_DSN,SENTRY_AUTH_TOKENSENTRY_ORG,SIMPLEX_UI_SENTRY_PROJECTValidation