Crash in 6.10.0.2787 on SATV When Navigating During playback

Plex Players Player Betas
1

After update to the latest beta on my Shield Android TV, the Plex app is crashing during playback whenever a navigation function (fast foward, rewind, select chapter, etc) is used.

2

For further info, rolling back to the public 6.9.0 release fixes the issue

3

Yep, same issue on the mobile release. It also crashes when you start a movie and don’t select resume from last position.

4

Thanks for reporting, we will have a new beta with a fix for seeking out soon.

5

Same crashes. Also crashed immediately after starting Plex immediately after a system restart (having previously experienced seek crashing).

Container/encoding doesn’t seem to matter for seek issues. Tested with MP4, MKV & MPEG2-TS containers, H.264 and MPEG2 video streams, stereo, AC-3 & EAC3 audio.

6

This is a very significant error in a very basic feature - is there any regression or sanity checking on the builds before they’re pushed out for public beta testing? This kind of error should never make it to a live update server, let alone a public one.

7

This isn’t a public release - this is a beta release. We beta users hopefully find these things before it makes it into a stable release.

8

A new beta was uploaded that fixes the navigation crashes.

9

@kegobeer-plex - a version made available to people outside Plex employees is a public release. Private would be behind a secure server at the very least. These releases are available via APK Mirror and other sources.

Years ago I left my corporate job as a test engineer, where one of my duties was managing and running public beta testing/groups like this one. Software didn’t get out before sanity checks by the engineers committing changes and the internal QA staff for regression.

Under no circumstances in any company, should a basic issue like crash on seek make it out of a QA lab and onto an external server for public beta testing, let alone have any chance whatsoever of making it into a general point release. Frankly, this type of error should never even make it to QA as it should be caught by the person submitting the code changes.