PMS 1.22.1.4228 version discrepancy and recurring PMS crashes with Plex for Android connections

Plex Media Server NAS & Devices
, ,
1

Server Version#: 1.22.1.4228-6000
Player Version#: 3.4.4 Plexamp for Android
Player Version#: 4.54.4 Plex Web for Windows
Player Version#: 8.14.1.23548.88dd4b13 Plex for Android (mobile)
Player Version#: 8.14.1.23548.88dd4b13 Plex for Android (Nvidia Shield)
Synology Info #: DS1019+ (x86_64), DSM 6.2.4-25556 Update 0

The DSM reports the installed Plex version as 1.22.1.4228-6000, however, I have downloaded and installed 1.22.1.4228-724c56e62. The DSM never reflects this version in the DSM or via ā€˜synopkg versionā€™.

Since installing the latest version that was released 3 days ago ( 2021-03-23 05:41:44-07:00), I have experienced repeated crashes of the PMS which require a manual restart via the DSM. I would also note that since installing the latest version, Plex seems to take longer to start than previously.

The crashes seem to be triggered by an Android (mobile and Nvidia Shield) connection to the Plex server. Plex Web and Plexamp do not seem to trigger a crash in independent tests.

2

I have the same Problems, please fix.

3

I have the same Problems too, please fix.Thanks

5

Thanks for the reply, @trumpy81. Sorry for the confusion regarding the version number, and thank you for the clarification on why the file numbering seems to have changed.

I will keep my eyes open for app updates and report back.

7

Hey, @trumpy81. The Plex client for Android update from this morning fixes the crash problem on the Nvidia Shield, but not on my Samsung Galaxy S20. Both running the same version of Plex for Android, both updated this morning, but the Plex mobile connection is causing an immediate crash of the PMS.

I had been playing media fine on my Nvidia Shield until I tried to test via my mobile.

Since the crash from the mobile client, Iā€™m now unable to play ANY media from the Nvidia Shield even though itā€™s not causing a crash. I get the good 'ol, ā€œAn error occurred while attempting to playback this video. Please check your connection and try again.ā€ if I try to play a video. Music playback fails with the error, ā€œAn error occurred while playing this item.ā€

The Nvidia/Android TV Plex client interface otherwise works OK, but no media playback whatsoever.

As previously, Plex for Web works fine and Plexamp is unaffected by any of this and continues to playback music just fine.

edit: Nvidia Shield playback was resolved by rebooting the Shield.

8

TO ALL:

PMS 1.22.1.4288 crashing is a known issue which was fixed earlier today.

Engineering is going to include the fix in PMS 1.22.2- which is on itā€™s way to PlexPass beta.

3 Likes
9

Thank you @ChuckPa and Plex devs! The latest beta has resolved all of the related crash issues involving Android clients.

1 Like
10

@ChuckPa The beta releases donā€™t help those of us using PMS on Shield. How long will it be before this fix is pushed to the Play store?

11

@BinaryJay

which build are you discussing?

The release announcement for today is:

12

@ChuckPa

Iā€™m running 1.22.1.4288 on Shield. Well, I was until today, it is completely dead as of now. You mentioned that there is a fix for this for 1.22.2 in the beta channel which is not available on this platform so my users and myself seem to be dead in the water until this hopefully fixed release is made available on the Play store which is where Shield gets its PMS updates.

13

The big problem folks were running into with 1.22.1.4288 was indeed Hubs related.
Engineering corrected and pushed it plus a few other fixes. (borrowing from the next release)

Does your shield work on build 1.22.0.4163 ?

14

Confirming by looking back at my changelogs, I did previously run 1.22.0.4163 for (14) days without any issues (no crashes of PMS or clients). It all went sideways with 1.22.1.4288.

Can you explain what you mean by ā€œHubs relatedā€?

15

were hubs removed in the beta version? I upgraded to the beta, and now the libraries canā€™t be managed with the new features. The features Iā€™m referring to are where we can manage the hubs for shared users, etc.

16

I donā€™t know anything about hub specifics. Iā€™ve been so busy helping folks and tracking issues that I didnā€™t know the version number until a few hours ago. I donā€™t know what has changed.

What I was able to determine, having read several sets of logs, is when the hubs would start to activate (for whatever reason), when one of the hubs started and tried to talk to the Home hub, the crash occurred.

Thatā€™s where my diagnosis stopped.

At that point, I could see the same behavior in mulitple sets of logs.
Just as I gave it to Engineering , is when they told me theyā€™d also seen and just resolved it.

They told me there would be a fix released (hot fix) and thatā€™s what we have.

17

Thanks for the explanation. I really liked the new hub idea. Itā€™s a great feature that Iā€™ve been wanting for quite some time. Hopefully weā€™ll see it back in a later release.

18

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.