Sentry.Init: 'Cannot read property 'bind' of undefined' when running jest

Environment

How do you use Sentry? Sentry SaaS (sentry.io)

Which SDK and version? "@sentry/react-native": "^2.5.0",

Steps to Reproduce

1. Run tests with jest

Expected Result

Tests should run fine

Actual Result

Get this error:

  ● Test suite failed to run

    TypeError: Cannot read property 'bind' of undefined

      16 |     const appBuild = RNDeviceInfo.getBuildNumber();
      17 |
    > 18 |     Sentry.init({
         |            ^
      19 |       dsn:
      20 |         '...',
      21 |       ignoreErrors,

      at getNativeFetchImplementation (node_modules/@sentry/browser/src/transports/fetch.ts:73:20)
      at new FetchTransport (node_modules/@sentry/browser/src/transports/fetch.ts:84:72)
      at ReactNativeBackend._setupTransport (node_modules/@sentry/react-native/src/js/backend.ts:87:12)
      at ReactNativeBackend.BaseBackend (node_modules/@sentry/core/src/basebackend.ts:72:28)
      at new ReactNativeBackend (node_modules/@sentry/react-native/src/js/backend.ts:18:5)
      at ReactNativeClient.BaseClient (node_modules/@sentry/core/src/baseclient.ts:88:21)
      at new ReactNativeClient (node_modules/@sentry/react-native/src/js/client.ts:22:5)
      at initAndBind (node_modules/@sentry/core/src/sdk.ts:21:18)
      at Object.init (node_modules/@sentry/react-native/src/js/sdk.ts:82:3)
      at new ErrorHandler (src/client-blocks/helpers/ErrorHandler.ts:18:12)

This error started happening after I upgraded from 2.4.2 to 2.5.0. I setup sentry like this:

Sentry.init({
      dsn: '...',
      ignoreErrors,
      enableNative:
        typeof process?.env?.JEST_WORKER_ID !== 'undefined' ? false : true,
      release: `${bundleId}@${appVersion}+${appBuild}`,
    });

[svenlombaert]

@svenlombaert When running jest tests, you would now have to pass NoopTransport to Sentry.init under transport. You should be able to import it from @sentry/react. Although this will cause errors to not be sent (as the transport is a No-Op) I assume that should be fine unless you’re also testing your Sentry integration?

This seems to work and is exactly what I need, thanks! Had to import NoopTransport from @sentry/core though. What’s the default value of the transport param actually?

[jennmueng]

@svenlombaert When running jest tests, you would now have to pass NoopTransport to Sentry.init under transport. You should be able to import it from @sentry/react. Although this will cause errors to not be sent (as the transport is a No-Op) I assume that should be fine unless you’re also testing your Sentry integration?