User not able to join the meeting for recompiled Jitsi iOS SDK version 8.6.3

[anupkanjariya]

Description:

We have been using Jitsi recompiled SDK for a long and working fine without any issues until SDK version 8.5.0, but in version 8.6.3 we got the following error in the console while trying to join any meeting with black screen:

-[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID , client pairingID:
Using video encoder factory: RTCDefaultVideoEncoderFactory
Using video decoder factory: RTCDefaultVideoDecoderFactory
Error: Exception in HostFunction: <unknown>
Unable to find module for RedBox
Unhandled JS Exception: Error: Exception in HostFunction: <unknown>
FATAL ERROR: RCTFatalException: Unhandled JS Exception: Error: Exception in HostFunction: <unknown>
Unhandled JS Exception: Error: Exception in HostFunction: <unknown>, stack:
<unknown>@(null):(null)
value@47:2137
<unknown>@39:1641
value@111:862
n@686:403
<unknown>@686:538
<unknown>@674:2658
h@2:1585
<unknown>@672:1085
h@2:1585
<unknown>@671:43
h@2:1585
<unknown>@539:2191
<unknown>@539:2800
h@2:1585
<unknown>@538:29
h@2:1585
<unknown>@19:45
h@2:1585
<unknown>@7:129
h@2:1585
<unknown>@6:29
h@2:1585
d@2:958
global code@2675:3
WCSession is not paired
-[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID , client pairingID:
WCSession is not paired
-[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID , client pairingID:
WCSession is not paired
-[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID , client pairingID:
WCSession is not paired
-[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID , client pairingID:
WCSession is not paired
Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
Unable to find module for RedBox
Unhandled JS Exception: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
FATAL ERROR: RCTFatalException: Unhandled JS Exception: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
Unhandled JS Exception: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., stack:
<unknown>@35:289
value@47:3202
<unknown>@47:673
value@47:2503
value@47:645

Steps to reproduce:

1. Download the source code of iOS SDK from here
2. Follow the steps provided in doc and export xcframework for iOS.
3. Trying to use JitsiMeetSDK.xcframework in our application and try to join any meeting

Expected behavior:

The user should be able to join the meeting without any issue in the case of recompiled SDK 8.6.3.

Actual behavior:

While trying to join the meeting got the following black screen

Client information:

• Jitsi SDK Version: 8.6.3
• Operating System: iPhone 15 pro (version 17.0)
• Node version: v20.10.0
• npm version: 10.2.3

Additional information:

if we are using the SDK using Cocoapods, it's working fine without any issues but due to some changes we required as per our requirement we need to compile it ourselves (This issue appears without changing anything in the codebase of the SDK).

[saghul]

We compile the release SDK with Node 16.

[anupkanjariya]

Hello, I have tried with node v16.20.2 and npm 8.19.4 to export the recompile SDK but getting the same error as mentioned above. Anyway, it's working fine with Jitsi SDK 8.5.0, this issue only appears while using SDK version 8.6.3.

[saghul]

Sorry, I have no idea what this could be.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[anupkanjariya]

Hello @saghul , Can you please help me how you are exporting JitsiMeetSDK.xcframework from latest version of code? I have tried multiple times with different node versions but facing the same issue from 8.6.0 and above and it's working fine until 8.5.0. I am following the same steps mentioned in document. If you can help with this same way you are exporting for CocoaPods it would be very helpful.

[saghul]

We are building it just as the document says.

What error do you get?

[anupkanjariya]

As mentioned above the compiling and exporting of the SDK is done successfully but while I am using the SDK in our application the meeting page is not being loaded and in console got following logs:

Invariant Violation: "App" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.
Unhandled JS Exception: Invariant Violation: "App" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.
FATAL ERROR: RCTFatalException: Unhandled JS Exception: Invariant Violation: "App" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.
Unhandled JS Exception: Invariant Violation: "App" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., stack:
<unknown>@33:290
runApplication@146:1613
value@42:3860
<unknown>@42:675
value@42:2510
value@42:646
Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Updating selectors after delegate addition failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
10.19.0 - [FirebaseAnalytics][I-ACS023012] Analytics collection enabled
10.19.0 - [FirebaseAnalytics][I-ACS023220] Analytics screen reporting is enabled. Call Analytics.logEvent(AnalyticsEventScreenView, parameters: [...]) to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
Invariant Violation: Failed to call into JavaScript module method RCTEventEmitter.receiveTouches(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 10): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, HMRClient, AppRegistry.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
Unhandled JS Exception: Invariant Violation: Failed to call into JavaScript module method RCTEventEmitter.receiveTouches(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 10): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, HMRClient, AppRegistry.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
FATAL ERROR: RCTFatalException: Unhandled JS Exception: Invariant Violation: Failed to call into JavaScript module method RCTEventEmitter.receiveTouches(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 10): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, HMRClient, AppRegistry.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
Unhandled JS Exception: Invariant Violation: Failed to call into JavaScript module method RCTEventEmitter.receiveTouches(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 10): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, HMRClient, AppRegistry.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., stack:
<unknown>@33:290

[saghul]

Sorry, I have no idea. We can build master with no problem, now using Node 20, I have never seen such an error. Did you make any changes to the project?

[anupkanjariya]

Nope, There is no single line of code change, Just download the code from here and install dependencies for iOS and be able to run the sample project without any issues. Now export framework and it's successfully archived but when using the same framework in the project, the meeting screen not loading and showing these errors.

[saghul]

Sorry, I'm out of ideas :-/

[developerashish01]

Facing same issue. any solution?