• Review the documentation: https://docs.sentry.io/platforms/javascript/electron/
• Search for existing issues: https://github.com/getsentry/sentry-electron/issues
• Use the latest release: https://github.com/getsentry/sentry-electron/releases
  ⚠️ I am unable to use the latest release because of TypeError: Object(...) is not a function #363 (comment)
• Provide a link to the affected event from your Sentry account
  ⚠️ The event does not get sent to Sentry

Versions + Platform

• SDK version - @sentry/[email protected]
• Electron version - [email protected]
• Platform - Linux

Description

We initialise Sentry like this as described in the docs:

const { Offline: OfflineIntegration } = require('@sentry/integrations');

const { logger } = require('@sentry/utils');
logger.enable();

Sentry.init({
      dsn: '...',
      integrations: [new OfflineIntegration()],
});

If I turn off wifi and start the application I see the following log when I force an error from the main process:

Sentry Logger [Error]: Error while sending event: Error: net::ERR_INTERNET_DISCONNECTED

Forcing an error from the main process or from the renderer does not seem to cause an error to be logged to Sentry, even when restarting the application.

EDIT:

Forcing an error from a renderer process gives a different error, but when the machine becomes online:

Sentry Logger [Error]: Error while sending event: Error: net::ERR_NAME_NOT_RESOLVED