Skip to content

Commit 3c12ca0

Browse files
authored
Uploading of debug symbols no longer required (#5408)
1 parent 926f30a commit 3c12ca0

File tree

1 file changed

+4
-6
lines changed
  • src/platforms/javascript/guides/electron

1 file changed

+4
-6
lines changed

src/platforms/javascript/guides/electron/index.mdx

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -117,13 +117,11 @@ This script exposes IPC to the isolated renderer via Electrons `contextBridge` A
117117

118118
Check out the [example apps](https://github.com/getsentry/sentry-electron/tree/master/examples) for how to do this.
119119

120-
## Uploading Debug Information
120+
## Debug Information
121121

122-
To get symbolicated stack traces for native crashes, you have to upload debug symbols to Sentry. Sentry Wizard creates a convenient `sentry-symbols.js` script that will upload the Electron symbols for you. After installing the SDK and every time you upgrade the Electron version, run this script:
123-
124-
```shell
125-
node sentry-symbols.js
126-
```
122+
To get symbolicated stack traces for native crashes, you should enable fetching
123+
debug symbols from the Electron symbol server. Go to **Project Settings > Debug
124+
Files** and add Electron to the list of built-in repositories.
127125

128126
If your app uses a custom Electron fork, contains modules with native extensions or spawns subprocesses, you have to upload those symbols manually using Sentry CLI. For more information, see [_Native Usage_](/platforms/electron/).
129127

0 commit comments

Comments
 (0)