The telemetry identifies repeated, fatal exceptions originating from the com.facebook.react.ReactInstanceManager class during the application's attempt to bootstrap the React environment in response to background events. This error is consistently logged across multiple monitoring tools and is tied to the fundamental way third-party native modules attempt to interact with the React Native bridge.

The specific architectural signature of this crash is defined by a java.lang.UnsupportedOperationException stating that ReactInstanceManager.createReactContext is unsupported. This exception originates directly from the constructor of the ReactInstanceManager class within the React Native core framework. The triggering components identified in the telemetry include org.infobip.reactlibrary.mobilemessaging.MessageEventReceiver and the wix/react-native-notifications module.

To understand why this exception is thrown, it is essential to trace the execution path of a background event in a traditional React Native architecture. Historically, native modules handling push notifications or background background events relied heavily on Android BroadcastReceiver components to wake the application. When a push notification payload arrives from Firebase Cloud Messaging (FCM), the Android operating system triggers the onReceive method within a designated receiver. Because the JavaScript environment is required to process the notification payload and execute the corresponding business logic, these native receivers forcefully invoke methods to ensure the React context is active. Specifically, the telemetry shows the Infobip SDK calling ReactNativeBroadcastReceiver.getReactContext, which in turn relies on ReactNativeHost.getReactInstanceManager().createReactContext().