-
Notifications
You must be signed in to change notification settings - Fork 452
Manually Test Sentry integration
On Sentry, find the "DSN" of the project to target. It looks like this URL: https://XXX@XXX.ingest.sentry.io/XXX. This is the value you will set in the environment variable (replace _your_dsn_ placeholder).
export SENTRY_URL=_your_dsn_
pnpm desktop build
# For Mac:
SENTRY_SAMPLE_RATE=1 ./apps/ledger-live-desktop/dist/mac-universal/Ledger\ Live.app/Contents/MacOS/Ledger\ Live
You can then proceed to confirm that Sentry report works from the 3 different targets of Ledger Live Desktop: renderer process, main process and internal process. To do so, at any part of the app, you can literally type one of these:
CRASH_MAIN
CRASH_INTERNAL
CRASH_TEST
and it will report mocked errors to Sentry so we can test it end to end.


Set in your .env these variables
FORCE_SENTRY=true
SENTRY_ENVIRONMENT=development
SENTRY_DSN=_your_dsn_You can then proceed to testing in dev mode. To trigger a crash, you can go to Settings > Debug > Mock & Test > Debug crash and then click one crash case to test. Typically "JS Crash" works well and you will be able to easily confirm on Sentry side.
- Ledger Live Desktop
- Ledger Live Mobile
-
Ledger Live Common
- Introduction
- Currency Models
- Currency Bridge
- Account
- Account Bridge
- apps
- appsCheckAllAppVersions
- ledger-live bot
- Canonical Ways to Investigate Bugs
- Coin Integration Introduction
- Countervalues
- Packages Duplicates
- Derivation
- Developing with CLI
- Developing
- Gist Firmware Update
- Gist Transaction
- Hardware Wallet Logic
- Socket
- Assorted tips
- Integration Tests
- Process
- Monorepository Migration Guide
- Issues, Workaround and Tricks
- Common CI Troubleshooting
- Create staging builds using the CI
- Deprecated