sentry-react-native: RNSentry.extraUpdated is not a function

OS:

  • Windows
  • MacOS
  • Linux

Platform:

  • iOS
  • Android

SDK:

  • @sentry/react-native
  • react-native-sentry

react-native version: 0.60.5

Init Code:

Sentry.init({
  dsn: 'https://...@sentry.io/...'
});

I have following issue:

After updating to the latest release and following the migration guide, our app is crashing on launch.

RNSentry.extraUpdated is not a function

<unknown>
    backend.js:27:57
<unknown>
    scope.js:51:20
<unknown>
    scope.js:50:38
<unknown>
    JSTimers.js:250:17
_callTimer
    JSTimers.js:146:6
Object.callTimers
    JSTimers.js:399:6
scope.addScopeListener(scope => RNSentry.extraUpdated(scope._extra));

maybe should be setExtra()?

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 9
  • Comments: 18 (2 by maintainers)

Most upvoted comments

Downgrading to "@sentry/react-native": "1.0.5" fixed my issue

@HazAT With all due respect, I followed the documentation precisely with unlinking react-native-sentry, and then proceeding to install @sentry/react-native and face this issue.

Can you give us some more context to go on? Steps to troubleshoot?

Make sure you correctly relink your native deps, this function changed in iOS/Android.

This can only happen if your native and JS code are out of sync. This function has been removed in the major bump, if you codepush update your app without releasing the native part as will this will break.

Not sure if this will help anyone else but this happened to my team because we did a code push after bumping that sentry package

Where has this extraUpdated function been ever written? We’re unable to find it on https://github.com/getsentry/sentry-javascript/search?q=extraUpdated or https://github.com/getsentry/sentry-react-native/search?q=extraUpdated (one result which has been always commented out).

This is absolutely crashing our app. Still happening on @sentry/react-native 1.33 and React Native 61.5. Happening on a production app on several real iOS devices. Sorry for not providing more info. The above comments describe well the issue.