I’ve been seeing the same issue and I would hazard a guess that all of these cases are being launched from the app sitting on the launcher bar, rather than the apps screen.
Certain Tizen devices try to be smart and prelaunch the apps on that bar, hidden in the background. It means a faster start up because they’re waiting to go. Unfortunately if the prelaunch occurs before the network is ready (as Volts pointed out) then the app can get stuck and when you “launch” it for the first time all you’re doing is pulling the broken app to the foreground. That’s why an exit and relaunch fixes it, because it’s now launching with a working internet connection.
Until the app can hold out for longer, disable prelaunch, or attempt recovery then the temporary solution might be to remove Plex from the bar and access it via Apps instead.
Thanks for this explanation. How to explain with same TV when used the OLD app, and launch from smart TV bar issue is not present.
I was using the OLD app for years and this issue not happened.
I suspect new changes in the app causing this issue.
@sLumpy Can you add internet check while loading the app and then load? If you look at other apps like Netflix and YouTube they display error message while loading the app if internet is not available.
The TV already checks if the app is on network or not. It prevents you from launching the app if so (at least it does for me, unless it has changed recently). In the cases where you somehow get into the app without and internet connection, it should fall back gracefully to offline usage. I suspect something is up there, but we’re still investigating.
@sLumpy please provide an update on this as it’s open for months now. What is PLEX position on this bug as if unable to fix please let me know as planning to seek a refund on my subscription.
@AliveKiller Now that’s going too far. This is only a preview. Just opt-out of the preview as I did and it is fixed. Let’s hope that PLEX could reproduce this somehow.
I’ve added a change in the next release that hopefully will address this. Once the next release is out, let me know if it fixes it or not. I can’t reproduce the problem so I can’t test if it’ll be fixed or not.
@sLumpy as I said before this is happening with Samsung Tizen 2016 TV models and specific to the models in this thread. Are you testing in these models?
If not I am happy to be at your assistant. I can even install a test build or open a FW to my TV IP and let you do your magic or follow specific steps.
It’s not an excuse to say I can’t reproduce therefore I can’t fix as you can’t simply replicate all variables.
It’s not an excuse to say I can’t reproduce therefore I can’t fix
It’s not an excuse, it’s a fact that all the Samsung devices differ regardless of TV models. We’ve had many bugs where they are reproducible only on certain devices even though it’s the same Tizen version, same series, or even the same model number. If I can’t reproduce it, then it makes it far more difficult to track down and debug. That doesn’t mean we won’t fix it, it means that it’s a bit of a shot in the dark when attempting to put in a fix.
I can even install a test build or open a FW to my TV IP
We can’t send out one-off builds via USB anymore because of Samsung’s T&C’s. We have a way to load test builds though, I can ping you once the changes have landed but I’d need your Plex username (which you can DM to me).
