diff --git a/src/docs/product/cli/dif.mdx b/src/docs/product/cli/dif.mdx index b464acf65062a..8872e22f581c3 100644 --- a/src/docs/product/cli/dif.mdx +++ b/src/docs/product/cli/dif.mdx @@ -7,7 +7,7 @@ description: "Debug information files allow Sentry to extract stack traces and p Debug information files allow Sentry to extract stack traces and provide more information about crash reports for most compiled platforms. `sentry-cli` can be used to validate and upload debug information files. For more general -information, refer to [_Debug Information Files_](/workflow/debug-files/). +information, refer to [_Debug Information Files_](/platforms/native/data-management/debug-files/). ## Permissions @@ -94,7 +94,7 @@ Files that have already been upload are skipped automatically. We recommend uploading debug information files when publishing or releasing your application. Alternatively, files can be uploaded during the build process. See -[_Debug Information Files_](/workflow/debug-files/) +[_Debug Information Files_](/platforms/native/data-management/debug-files/) for more information. diff --git a/src/platform-includes/getting-started-primer/native.mdx b/src/platform-includes/getting-started-primer/native.mdx index 411ce0b4738bb..3cff1b17b4d85 100644 --- a/src/platform-includes/getting-started-primer/native.mdx +++ b/src/platform-includes/getting-started-primer/native.mdx @@ -4,4 +4,4 @@ Sentry also offers higher-level SDKs for platforms with built-in support for nat - [_Android_](/platforms/android/) - [_Apple (Cocoa)_](/platforms/apple/) -- [_Electron_](/platforms/electron/) +- [_Electron_](/platforms/javascript/guides/electron/) diff --git a/src/platforms/javascript/common/data-management/debug-files/index.mdx b/src/platforms/javascript/common/data-management/debug-files/index.mdx index 8ee84609a5e14..49c9a05e5dbcd 100644 --- a/src/platforms/javascript/common/data-management/debug-files/index.mdx +++ b/src/platforms/javascript/common/data-management/debug-files/index.mdx @@ -4,6 +4,7 @@ description: "Learn about how debug information files allow Sentry to extract st sidebar_order: 200 supported: - javascript.capacitor + - javascript.electron --- Debug information files allow Sentry to extract stack traces and provide more diff --git a/src/platforms/javascript/guides/electron/index.mdx b/src/platforms/javascript/guides/electron/index.mdx index 006d152ccb508..44c0c29255cdb 100644 --- a/src/platforms/javascript/guides/electron/index.mdx +++ b/src/platforms/javascript/guides/electron/index.mdx @@ -183,7 +183,7 @@ Files** and add Electron to the list of built-in repositories. If your app uses a custom Electron fork, contains modules with native extensions or spawns subprocesses, you should upload those symbols manually using the -Sentry CLI. For more information, see [_Native Usage_](/platforms/electron/). +Sentry CLI. For more information, see [_Native Usage_](/platforms/javascript/guides/electron/#native). @@ -193,7 +193,7 @@ It is currently not possible to send events from native code (such as a C++ exte ## Dealing with Minified Source Code -The Electron SDK supports [Source Maps](https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/). If you upload source maps in addition to your minified files that data becomes available in Sentry. For more information see [_Source Maps_](/platforms/electron/). +The Electron SDK supports [Source Maps](https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/). If you upload source maps in addition to your minified files that data becomes available in Sentry. For more information see [_Source Maps_](/platforms/javascript/guides/electron/#source-maps). ## Native @@ -220,13 +220,13 @@ are deploying to, depending on your needs. If your application contains custom native extensions or you wish to symbolicate crashes from a spawned child process, upload their debug information manually -during your build or release process. See [_Debug Information Files_](/workflow/debug-files/) for a detailed description of how to +during your build or release process. See [_Debug Information Files_](/platforms/javascript/guides/electron/data-management/debug-files/) for a detailed description of how to set up Sentry for native development. Additionally, see [_Uploading Debug Information_](/product/cli/dif/) for the upload process. ### Child Processes -The SDK relies on the [Electron CrashReporter](https://electronjs.org/docs/api/crash-reporter) to generate the crash dumps. To receive crash reports for child processes, you need to make sure the crash reporter is activated by either the SDK or manually (see [below](#electron-native-manual)). +The SDK relies on the [Electron CrashReporter](https://electronjs.org/docs/api/crash-reporter) to generate the crash dumps. To receive crash reports for child processes, you need to make sure the crash reporter is activated by either the SDK or manually (see [below](/platforms/javascript/guides/electron/#electron-native-manual)). An exception to this is _macOS_, where the crash reporter only needs to be started in the `main` process and watches all its child processes. The SDK already takes care of this difference, so there is no need to manually disable `enableNative`. @@ -238,7 +238,7 @@ ___MINIDUMP_URL___ It currently not possible create breadcrumbs or other event meta data from native code. This has to happen in JavaScript. Support for this is planned in future releases. -### Manual Crash Reporting {#electron-native-manual} +### Manual Crash Reporting You can also capture native crashes by starting the [Electron CrashReporter](https://electronjs.org/docs/api/crash-reporter) manually. Sentry is able to provide symbolicated stack traces and show system information, but no Electron-specific metadata, breadcrumbs or context information will be present. This is useful in cases where you cannot use the full Electron SDK: diff --git a/src/platforms/native/common/enriching-events/attachments/index.mdx b/src/platforms/native/common/enriching-events/attachments/index.mdx index f2e85753a3913..ea09019a06bd5 100644 --- a/src/platforms/native/common/enriching-events/attachments/index.mdx +++ b/src/platforms/native/common/enriching-events/attachments/index.mdx @@ -11,7 +11,7 @@ You can use a higher-level SDK for platforms with built-in support for native cr - [Electron](/platforms/javascript/guides/electron/) - [Minidump endpoint](/platforms/native/guides/minidumps/) -To receive symbolicated stack traces, you have to upload debug information to Sentry. Unless the option to store crash reports is enabled, Sentry will use the crash reports only to create the event, then will drop the files. For more information, see [Debug Information Files](/workflow/debug-files/). +To receive symbolicated stack traces, you have to upload debug information to Sentry. Unless the option to store crash reports is enabled, Sentry will use the crash reports only to create the event, then will drop the files. For more information, see [Debug Information Files](/platforms/native/data-management/debug-files/). ## Uploading Attachments diff --git a/src/platforms/native/guides/minidumps/index.mdx b/src/platforms/native/guides/minidumps/index.mdx index 7fec2e8d2c93e..8ae96794440a7 100644 --- a/src/platforms/native/guides/minidumps/index.mdx +++ b/src/platforms/native/guides/minidumps/index.mdx @@ -17,12 +17,12 @@ This page describes **standalone** usage of Minidumps with Sentry. We strongly e In order to receive symbolicated stack traces, you have to upload debug -information to Sentry. For more information, see [Debug Information Files](/workflow/debug-files/). +information to Sentry. For more information, see [Debug Information Files](/platforms/native/guides/minidumps/data-management/debug-files/). ## What is a Minidump? {#what-is-a-minidump} Minidumps are files containing the most important memory regions of a crashed -process. When the process crashes, the minidump is written to the user’s disk +process. When the process crashes, the minidump is written to the user's disk and can later be uploaded to Sentry. A minidump typically includes: - The runtime stack of each thread that was active during the time of the crash. diff --git a/src/platforms/native/guides/wasm/index.mdx b/src/platforms/native/guides/wasm/index.mdx index d91da53b8d079..335138e311540 100644 --- a/src/platforms/native/guides/wasm/index.mdx +++ b/src/platforms/native/guides/wasm/index.mdx @@ -43,7 +43,7 @@ wasm-split /path/to/file.wasm -d /path/to/file.debug.wasm --strip This command modifies the `file.wasm` in place to add the `build_id`, then removes all debug information. The debug information is put in a `file.debug.wasm` which -then needs to be uploaded to Sentry. For more information, see [Debug Information Files](/workflow/debug-files/). +then needs to be uploaded to Sentry. For more information, see [Debug Information Files](/platforms/native/guides/wasm/data-management/debug-files/). ## Crash Reporting diff --git a/yarn.lock b/yarn.lock index d76ab57ad72cc..ae925f70623df 100644 --- a/yarn.lock +++ b/yarn.lock @@ -4725,9 +4725,9 @@ caniuse-api@^3.0.0: lodash.uniq "^4.5.0" caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001283, caniuse-lite@^1.0.30001464, caniuse-lite@^1.0.30001503: - version "1.0.30001503" - resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001503.tgz#88b6ff1b2cf735f1f3361dc1a15b59f0561aa398" - integrity sha512-Sf9NiF+wZxPfzv8Z3iS0rXM1Do+iOy2Lxvib38glFX+08TCYYYGR5fRJXk4d77C4AYwhUjgYgMsMudbh2TqCKw== + version "1.0.30001574" + resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001574.tgz#fb4f1359c77f6af942510493672e1ec7ec80230c" + integrity sha512-BtYEK4r/iHt/txm81KBudCUcTy7t+s9emrIaHqjYurQ10x71zJ5VQ9x1dYPcz/b+pKSp4y/v1xSI67A+LzpNyg== capital-case@^1.0.4: version "1.0.4"