Updated App on Samsung TV (version 2.013) - App freezes

Server Version#: 1.19.2.2702
Player Version#: 2.013

I just updated the Plex app on my Samsung TV. After launching, I had to re-link the app to my server. Once linked successfully, the app starts to load and then freezes. No libraries load and I am unable to move the “cursor” within the app. Is anyone having this issue?

Yes a friend of mine is having same issue he is having issue with 2.012 and 2.013

Hi @tripster23

See:

1 Like

I’m having the exact same issue here., however im running 2.012 client. It just started in the last 24 hours, and an update from the previous realse to the current release 1.19.2.2702 made no difference.

Thanks everyone. I rolled back my PMS version to 1.19.1.2645 and it 's working again on the Plex Samsung App.

I have the exact same issue and screen as first post.
Just started today after a forced SmartHub update on the samsung tv. No changes made on server since the last time it worked (earlier today)

After SmartHub update, all apps were removed, and I had to install plex fresh, and link it to TV. After logging in to my account with pin code, I am stuck with a frozen screen like the one in the first post, and I have to switch my TV off and back on again to get out of it.

Downgrade your server to 1.191, change your updates channel to public from beta and it will work again.

See this thread for more details:Version 1.19.1.2645 Server broke Samsung access

2 Likes

I too have a Samsung 2015 3D TV. This issue where I could login and see nothing started this morning. I had been on 1.191.1.2702 for a couple of days now.

I hope they fix this sooner rather than later. It’s not like I can buy a newer Samsung 3D TV. :frowning:

Yep having the same issue here, deleted the app multiple times on the samsung tv and also updated my plex . It will play for a short time, but as soon as I return to the main selection screen I get the same as above…

Thanks man, much appreciated. Fixed my issue as well! Roll-back was not as squeaky bum time as i thought it would be! :slight_smile:

The new update, version 2.2737, should have fixed this, according to the release notes.

It works now!

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