App crashes on startup after installing instabug RN integration

Steps to Reproduce the Problem

1. Install the instabug RN SDK
2. Fire up the app in iOS or Android emulators

Expected Behavior

App doesn’t crash on startup

Actual Behavior

App crashes with the following error on startup:

transform[stderr]: The exported identifier "Survey" is not declared in Babel's scope tracker
transform[stderr]: as a JavaScript value binding, and "@babel/plugin-transform-typescript"
transform[stderr]: never encountered it as a TypeScript type declaration.
transform[stderr]: It will be treated as a JavaScript value.
transform[stderr]:
transform[stderr]: This problem is likely caused by another plugin injecting
transform[stderr]: "Survey" without registering it in the scope tracker. If you are the author
transform[stderr]:  of that plugin, please use "scope.registerDeclaration(declarationPath)".
 BUNDLE  ./index.js

error: node_modules/instabug-reactnative/src/index.ts: /Users/rkeiii/workspace/BookshareMobileReader/node_modules/instabug-reactnative/src/index.ts: Exporting local "Survey", which is not declared.
  16 |   Report,
  17 |   Trace,
> 18 |   Survey,
     |   ^^^^^^
  19 |   APM,
  20 |   BugReporting,
  21 |   CrashReporting,

Instabug integration code

The following is in my main App.tsx

import Instabug from 'instabug-reactnative';
...
  /**
   * Initialize Instabug crash handling service
   */
  useEffect(() => {
    Instabug.start('SECRET_TOKEN', [
      Instabug.invocationEvent.shake,
    ]);
  }, []);

SDK Version

11.5.0

React Native, iOS and Android Versions

React Native 0.7.0 iOS 15.5 Android 13

Device Model

Occurs on both emulators

[rkeiii]

Thank you for the suggested fix. We’ve actually moved onto another bug tracking platform but I will definitely try this if we end up switching back.

I’m leaving the ticket open since it appears to affect others.

[DavidMina96]

@tomwanzek Thanks a lot for your contribution with this issue fix (and for your wonderful feedback re our package too). Such feedback is what keeps us enhancing our package continually to be up to our customers’ expectations and beyond. 🙏

For anyone facing this error, I’m happy to share that a patch release v11.5.1 should now be out, which includes the fix for this issue. 🚀

I’ll be closing the issue accordingly, but please feel free to re-open it at any time if needs be.