Skip to content

mechanism.handled value altered unexpectedly #1327

@hetu1234

Description

@hetu1234

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Electron SDK Version

7.10.0

Electron Version

33.3.1

What platform are you using?

Windows

Link to Sentry event

https://jupiter-ct.sentry.io/issues/7357130581/?project=1428302&query=release%3A%22desktop%4026.2.1010%2B16773%22&referrer=release-issue-stream

Steps to Reproduce

mechanism.handled incorrectly set to true for unhandled promise rejection after upgrading from 6.6.0 to 7.10.0

Description:

After upgrading sentry-electron from version 6.6.0 to 7.10.0, the mechanism.handled field for an unhandled promise rejection is reported as true, whereas it was correctly reported as false in version 6.6.0.

Steps to Reproduce:

Upgrade sentry-electron from 6.6.0 to 7.10.0.

Mock an error using the following code in the main process:

javascript
ipcMain.on('TestSentry::PromiseErrorInMainProcess', () => {
setTimeout(() => {
new Promise((_resolve, _reject) => {
throw new Error('Unhandled promise rejection in renderer process');
});
}, 500);
});
Trigger the event and observe the reported event in Sentry.

Expected Result:

mechanism.handled should be false, indicating the rejection was not handled (as seen in version 6.6.0).

Actual Result:

mechanism.handled is true.

Example Issue (v6.6.0):
https://jupiter-ct.sentry.io/issues/7357130581/?project=1428302&query=release%3A%22desktop%4026.2.1010%2B16778%22&referrer=release-issue-stream

Expected Result

I want it keep the same with before
https://jupiter-ct.sentry.io/issues/7357130581/?project=1428302&query=release%3A%22desktop%4026.2.1010%2B16778%22&referrer=release-issue-stream

Actual Result

It change the handled, and the mechanism.type is also changed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for issues without a type.

    Projects

    Status

    Waiting for: Community

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions