Jest tests fail when importing appcenter or appcenter-push

[anthonyhumphreys]

Description

Compatibility with Jest

Cannot test a connected container that includes import AppCenter from 'appcenter';

Jest throws an error which prevents further test execution.

Repro Steps

Please list the steps used to reproduce your issue.

1. import AppCenter from 'appcenter'; in a react-native container component.
2. Write a snapshot test to test that component
3. Execute said test

Details

1. Which SDK version are you using?
   • 1.5.0
2. Which OS version did you experience the issue on?
   • N/A
3. What device version did you see this error on? Were you using an emulator or a physical device?
   • N/A
4. What third party libraries are you using?
   • Jest
5. Run the following command and paste the output below: react-native info

Place output here

6. If you're developing for React Native iOS, run the following command and paste the output below: pod --version

Environment:
OS: Windows 10
Node: 8.10.0
Yarn: Not Found
npm: 5.6.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version 3.0.0.0 AI-171.4443003

Packages: (wanted => installed)
react: ^16.3.2 => 16.3.2
react-native: 0.49.3 => 0.49.3

7. Please enable verbose logging for your app using [MSAppCenter setLogLevel: MSLogLevelVerbose]; before your call to [AppCenterReactNative register]; (or any other SDK registration). For Android, use AppCenter.setLogLevel(android.util.Log.VERBOSE); before your SoLoader.init call. Include the logs here:

N/A

From AppCenter-Push

      at invariant (node_modules/react-native/node_modules/fbjs/lib/invariant.js:44:15)
      at new NativeEventEmitter (node_modules/react-native/Libraries/EventEmitter/NativeEventEmitter.js:31:1)
      at Object.<anonymous> (node_modules/appcenter-push/Push.js:5:26)
      at Object.<anonymous> (logic/actions/settingsActions.js:39:128)

[jmedellinMS]

Hi @antwan2093 ,
Thank you for reporting this. This looks like a bug and our team has an item in backlog for tracking this. We will update the thread once the fix is released. Sorry for the inconvenience.

[dhei]

This should be fixed in v1.6.0.