Tim Fish

It's worth noting that while we can instrument `global.Promise`, we cannot instrument the internal `[[Promise]]` that's used for `async function`.

Why are you manually constructing the `exception` and `message`? When you supply a minidump Sentry pulls these from the minidump.

To differentiate between different sources of errors I think it's recommended to use [tags](https://docs.sentry.io/platforms/rust/enriching-events/tags/). ```rust configure_scope(|scope| { scope.set_tag("source", "lib-bad"); }); ```

I released a modiule that can find/delete imcompatible binaries: https://github.com/timfish/incompatible-binaries You can use this with Electron Builder using the `afterPack` [hook](https://www.electron.build/includes/hooks.html): ```ts const { deleteIncompatibleBinaries } = require('incompatible-binaries'); const ARCHES...

> The issue we are seeing is that when using electron-builder tries to build for both x64 and arm64 it will ONLY pick up the optional dependency for the architecture...

How would this work with `dependencies` and `devDependecies`? If I'm building on arm64, targeting x64 and have development dependencies with native modules, I'll likely need a mix. I think it...

This hasn't made it into a release yet but once it has, you'll be able to add attachments in `beforeSend` in the renderers as per the browser docs: https://docs.sentry.io/platforms/javascript/enriching-events/attachments/#add-or-modify-attachments-before-sending

We have an `electron-react-boilerplate` example that is built and tested for our integration tests although this does not test a packaged build: https://github.com/getsentry/sentry-electron/tree/master/examples/electron-react-boilerplate

As far as I can see, the package script just runs the build and then runs Electron builder to package the app. It looks like the following error comes from...

If you use a version of `@sentry/integrations` that matches the the one in use in toucan-js ([ie. v7.76.0](https://github.com/robertcepa/toucan-js/blob/68c83695deed6f98728e3382087071f3736374f5/packages/toucan-js/package.json#L32)), you should not see this issue as the APIs will match. Once...