What’s the release date (Markus) mentioned, that fixes this problem?
I tried starting my LG PLEX app last night and was alerted that an update was available. Installed the update and now I’m reading about this problem on this forum. I have another LG that is not OLED and it’s OK without the update. Other clients are working fine, so my guess is the app on my OLED WebOS is the problem.
Having this problem on LG UH603v TV. As above have deleted app, unplugged telly for 2+ minutes, deleted TV from authorised devices and reinstalled with no luck. When opening the Plex logo comes up for approx 45 seconds then error screen:
“Error details: uncaught typeerror: cannot read properly ‘lastsourcepivots’ of undefined”
Hello,
Since the last update of my LG 65C8 TV (05.10.40), the Plex application has been working very poorly. The message with error 337 appears on the screen. The app works great with other devices. The TV also works very well on the network because I have access to my shared files from my PC.
I contacted LG and they told me that indeed since their update, Plex was unstable.
When do you expect a Plex update to be compatible with LG?
Cordially.
(Sorry for my english, I’m french)
Hi,
I am still getting the Uncaught type error on an LG WebOS TV UK6400PLF running software version 05.10.40
I’ve checked the PLEX app on the TV store and it is v2.1.3 dated 21/08/2019.
Does this mean that the update mentioned above has not been applied to this TV?
Is there any other way to get the update?
I tried removing and reinstalling the app, including the mains power cycle, but it didn’t work.
The other odd thing is that there are no webOS devices showing as authorized devices, but I haven’t removed them.
Same Problem on my LG 50UK6090PUA, appears to have stopped working about the same time I upgraded to 1.18.3.2156 server update? For sure it stopped working on 12-24-19.
Re-installed LG app, did not fix, then went back to server version 1.18.2.2080, still no fix, still getting “check network connection error -337” on out LG TV.
Have no problem casting to any of my 3 TVs using windows “cast to”.
I did not test my two Samsung TVs on version 1.18.3.2156 but both work fine on the re-installed 1.18.2.2080.
Installed the XPlay app (5 day trial) on my LG TV, it appears to be working fine. Have not researched XPlay yet, they want about $9 (USD) to authorize permanent use of app.
The LG is our main TV, attempting to catch up on missed series during the network holiday “down time”.
Any suggestions would be greatly appreciated!
I’ll see if the factory reset works, but the TV was linked once. It used to work fine, now I get the error and it seems to have disappeared from the Plex settings.
A bit stumped. This must be a bug somewhere as it was all working well, but has since stopped. All my Apple TV boxes and app installs work fine, so I know my server is fine.
To me the clue is further up the thread. Plex state that they fixed it in November, but the app in the TV is dated August, so this suggests that the fix hasn’t been rolled out everywhere.
Really need input from Plex support please if they are watching…
Just updated my LG C7 Plex app and am also getting the “Error details: uncaught typeerror: cannot read properly ‘lastsourcepivots’ of undefined” on startup. Don’t recall when it last worked.
@markus101 Could you please tell us when we can expect the update? In the app store of my LG 65SJ8109 (2017) I still see the version from August, as many people here have already written. At least please give us some feedback on the current situation. Thanks
Did the full factory reset on the TV and stared over.
Now all working again so there is something somewhere that upset the settings.
Thanks for the advice, but there is definitely a bug in there somewhere! I just hope it doesn’t reoccur…
All updates are posted to the release announcements thread.
The issue originally reported in this thread was released on December 2nd.
The package in the app store is not updated for every release, it is only updated when making changes around hosting (which was done in August).
After the original issue was fixed it looks like two more issues were posted here, one that appears to be a network issue and the pinnedSources issue. The network issue deserves a new thread if it’s still an issue, but the pinnedSources issue will be fixed in the next release.
Thanks for your answer, but there are two questions left. When can we expect the update?
I don’t quite understand the sense of pushing out new releases, but then not making them available in the App Store. I hope you can clarify this point a little bit more Thanks in advance!