I read the posts here:
I’ve experienced the exact same issue, causing me to have to detach. Here’s a snack I just created:
In my snack, I showcase how ErrorBoundaries don’t work in this case. Additionally, after detaching and using react-native-video, my app never crashes anymore. Even if I lift the 3 rendered video restriction (mentioned below), the app still functions. Only a handful of videos will actually display at any given time, but the app won’t crash.
07:21PM - 12 Apr 18 UTC
09:39PM - 12 Jun 18 UTC
We have reports of "The AVPlayerItem instance has failed" followed by a native crash when running multiple videos (e.g. in a...
I’m getting issues where occasionally the videos will not play and I’m getting this error: “The decoder required for this media is busy.”. My guess is that there might be too many rendered
players (I only have like 6-10 rendered). As of Oct 2020 on managed 39.0, what are the best practices in managed Expo apps for videos?
Do we need to create some kind of system whereby only one Video component shows at one time?
@sjchmiela, you mentioned you were going to look into it here:
I’ll investigate what is happening.
-11839 error code means
AVErrorDecoderTemporarilyUnavailable — The appropriate decoder is currently not available. Source
so I guess the crashes may be connected to rendering too many Video elements. I’ll see what we can do about it.
Was the issue resolved?