I’m trying to call playerClient.destroy() when leaving the PlayerScreen component. But that results in the app crashing(I get kicked back to the device’s Home screen with no logs in the dev console). I was able to capture some of the logs from my USB stick.
I’m destroying the playerClient in the beforeRemove callback from react-navigation in my screen component.
If I comment the line, the app backs out fine and I can play other videos. But if I stay in the PlayerScreen(we have an “Up next" feature and try to load another stream, it seems that KeplerSurfaceView won’t work on the next video as it doesn’t render any video frames but I can hear audio.
This is a blocker for us.
I’m attaching the device logs.
Our team is checking on this.
Meanwhile, could you please help us with the below information which will help us investigate better.
Environment
Please fill out the fields related to your bug below:
SDK Version:Output of kepler --version
App State:[Foreground/Background]
OS Information
Please ssh into the device via kepler exec vda shelland copy the output from cat /etc/os-releaseinto the answer section below. Note, if you don’t have a simulator running or device attached kepler exec vda shell will respond with vda: no devices/emulators found
<!-- Answer here if applicable -->
Player SDK:[Bitmovin, Shaka, ...]
Player SDK Version:[e.g. 1.23]
Audio Codecs:[AAC, ...]
Video Codecs:[h.264, mp4]
Manifest Types:[m3u8, dash, etc ..]
Example Code Snippet
Include any relevant code or component setup in React Native that can help reproduce the bug.