apivideo / api.video-reactnative-player

React Native video player
https://api.video
MIT License
17 stars 2 forks source link

[Bug]: Not working in current version of React Native #26

Closed charlestbell closed 4 months ago

charlestbell commented 6 months ago

Version

1.0.2

Environment that reproduces the issue

https://github.com/charlestbell/api_dot_video_expo_50_bug

Windows 11 running on x86_64 VsCode Android Studio Android Emulator Pixel 3a with API 34 Extension level 7 Expo Version 51

Is it reproducible in the example application?

Yes

Reproduction steps

Device setup:

Code setup: https://github.com/charlestbell/api_dot_video_expo_50_bug

If it hangs at any point, with the terminal selected, tap r to refresh expo

Don't forget to instal dependencies with yarn!

If you prefer, you can download Expo Go from the Play store/App store and launch the project by scannign the QR code from the terminal.

Expected result

The video player appears inside of the app

Actual result

It throws this error on Android.

Screenshot_1717095968

And this on iOS File (7)

Additional context

If you comment out the player, like I do here, the app runs normally without error. Screenshot 2024-05-30 151047

The affecte file is in app/tabs/index.tsx

Relevant logs output

iOS:

 ERROR  TypeError: Cannot read property 'startLoadWithResult' of null, js engine: hermes

Android:

 ERROR  Invariant Violation: Failed to call into JavaScript module method RNCWebViewMessagingModule.onMessage(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 12): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, HMRClient, AppRegistry, RCTEventEmitter, WebViewMessageHandler1.
          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., js engine: hermes
olivier-lando commented 4 months ago

Hey, We've release a new version (1.1.0) that should fix this issue. Let us know if you encounter any issue. Regards

charlestbell commented 4 months ago

Thanks!