I also have this issue on Plex Google TV app
yes we are aware. I have no ETA for a fix.
1 Like
I have the same issue on my MiBox (as well as shield).
The strange thing is when I open Plex on my iPhone it works but if I stream it to my Nvidia Shield or start it from my Nvidia Shield I receive the message unable to navigate.
1 Like
I have been seeing this too (Linux Plex):
PLex for Amazon firecube and Nvidea shield (local) has the issue.
Remote access (fire stick) & web page on the server machine does not have this issue. Nor does it appear to be an issue on the phone app (android - I only used it to see if it works and it appears to but its not something i use)
I cannot read the episode description or look at actors, it always throws the error and I have to hit the back button to fix it.
I tried:
upgrading server to 1.23.0
downgrading to an old version (1.21.1), and it has the issue too.
Wiping cache of devices & factory reset(s). & clean bundles /optimize database on server.@BigWheel , please find attached a log from my NVidia Shield player this morning where I am able to replicate the issue pretty easily, whether I watch a show for 1 minute or 1 hour.
What can’t it find when it is resuming ‘Home Activity’?
05-07 05:06:27.260 i: Fetching [method:GET] https://192.168.0.158:32400/hubs/promoted?contentDirectoryID=2&count=10&excludeContinueWatching=1&excludeElements=Actor%2CCollection%2CCountry%2CDirector%2CGenre%2CLabel%2CMood%2CPart%2CProducer%2CRole%2CSimilar%2CWriter%2CPhoto%2CVast%2CTopic&excludeFields=summary%2Ctagline%2Cfile&includeExternalMetadata=1&includeLibraryPlaylists=1&includeMeta=1&includeRecentChannels=1&includeStations=1&includeTypeFirst=1&libraryHubsOnly=1&pinnedContentDirectoryID=2%2C1&X-Plex-Token=...qnFr&X-Plex-Language=en-us
05-07 05:06:27.314 i: Resuming HomeActivity.
05-07 05:06:27.321 i: [UpdateChannelsJob] Starting channel creation job
05-07 05:06:27.440 i: Showing toast: Unable to navigate, item not found.
UnableToFind.txt (249.6 KB)
I have also been seeing this issue on my Nvidia Shield for weeks. Among other bugs that have been appearing over the last few updates. Why is the Plex client going downhill so fast?
2 Likes
Having this issue, too. On Android and Firetv.
ditto on chromecast player 8.16.2.2493
Yet another person impacted by this issue for months who has been watching this thread.
I shouldn’t be that surprised though, the shield client bombs CONSTANTLY.
Do they even test it? I always have issues yet my friends not using a shield seem to function flawlessly.
Frustrated enough to finally post.
1 Like
This just started happening on my Fire TV stick.
After looking further into it, here’s what I’ve found:
The issue happens while in the menu when you hover over an item that’s also being used by another process.
For instance, if you have a tv series that’s stored on your server, and a process on that server (or elsewhere) is accessing those files, then when you scroll passed them on the Fire TV Stick, this error shows.
When you stop the other process from accessing the same files, the problem goes away.
I hope this helps other people while plex are working on this bug
1 Like
Same issue here - I have two Shield TVs and both show this popup pretty constantly
2 Likes
I’ve got this issue on both Shields that I own. Some files won’t play at all and some if I keep trying will load. None of my roku or other devices show any issues.
Also seeing this on my two Formuler Z8 boxes. A minor annoyance but still an annoyance.
This is an extremely annoying problem on the Firestick that has been an issue for many months.
@BigWheel , Plex has this forum for users to help each other but I would hope that you also use it as a way of finding out what pains people. When you consider the monthly fee people pay, which costs as much as streaming choices like HBO Max or Discovery or other lesser used TV apps, Plex needs to up their game.
Attached is another sample log file from when it happened again.
Unable to navigate.txt (161.0 KB)
Having been in software myself for 30 years I can appreciate prioritizing bugs but when you have an error message on screen that is really not necessary it gives a bad impression. This should be prioritized over home screen re-writes that customers don’t actually want nor care for.
Attempting to understand the logs, something that I’ve noticed in mine is that it would appear to error on Resuming Home Activity and when playing a show I usually get there by pressing the back button on my remote to take my NVidia Shield back to the previous screen. If the Plex app is not reading ‘Back’ and ‘Stop + Back’ then that would be the 1st place for the devs to look
You can see a lot of action within milliseconds around my pressing the back button.
05-15 05:46:30.361 i: [ExoPlayer][EventLogger] state [eventTime=52.19, mediaPos=70.00, window=0, period=0, IDLE]
05-15 05:46:30.362 i: [MemoryOptimisationBehaviour] Expanding memory cache.
05-15 05:46:30.362 i: [VideoAwakeBehaviour] Keep screen awake has been requested disabled for VideoAwakeBehaviour.
05-15 05:46:30.362 i: [AudioFocusBehaviour] Behaviour being destroyed, giving up audio focus
05-15 05:46:30.363 i: [AudioFocusBehaviour] Given up focus.
05-15 05:46:30.365 i: [DisplayBehaviour] Cancelling stop playback runnable to prevent unexpected stop.
05-15 05:46:30.368 i: [DisplayBehaviour] Reverting back to the original display mode.
05-15 05:46:30.368 i: [DisplayBehaviour] Mode is already set to our best mode of 1920x1080 @ 59.9401Hz (9).
05-15 05:46:30.378 i: [FF][MediaPeriod] Releasing.
05-15 05:46:30.379 i: [FFmpeg] [INFO] Demuxer has been successfully interupted.
05-15 05:46:30.381 i: [FF] Releasing demuxer.
05-15 05:46:30.381 i: [FFmpeg] [INFO] Demuxer closing.
05-15 05:46:30.382 i: [FFmpeg] [INFO] Demuxer has been interupted…
05-15 05:46:30.382 i: [FFmpeg] [INFO] Demuxer has been closed, interrupting FFmpeg…
05-15 05:46:30.387 i: [FFmpeg] [INFO] Demuxer has been interupted…
05-15 05:46:30.388 i: [FFmpeg] [INFO] Demuxer has been closed, interrupting FFmpeg…
05-15 05:46:30.390 i: [ExoPlayer][EventLogger] videoDisabled [eventTime=52.22, mediaPos=70.00, window=0, period=0]
05-15 05:46:30.391 i: [ExoPlayer][EventLogger] audioDisabled [eventTime=52.22, mediaPos=70.00, window=0, period=0]
05-15 05:46:30.394 i: [FFmpeg] [INFO] Demuxer has been interupted…
05-15 05:46:30.395 i: [FFmpeg] [INFO] Demuxer has been closed, interrupting FFmpeg…
05-15 05:46:30.401 i: [FFmpeg] [INFO] [Cache] Cache has been closed, interrupting AVIO …
05-15 05:46:30.402 i: [FFmpeg] [INFO] [Cache] Close requested, terminating.
05-15 05:46:30.406 i: [PlayerService] onDestroy
05-15 05:46:30.410 i: [FFmpeg] [INFO] [Cache] Close requested, terminating.
05-15 05:46:30.411 i: [FFmpeg] [INFO] Demuxer pipeline terminated.
05-15 05:46:30.412 i: [FFmpeg] [INFO] Demuxer has been successfully closed.
05-15 05:46:30.420 i: Resuming HomeActivity.
05-15 05:46:30.480 i: Showing toast: Unable to navigate, item not found.
05-15 05:46:30.493 i: Showing toast: Unable to navigate, item not found.
05-15 05:46:41.512 i: Time out fetching https://<>:32400/hubs/continueWatching?
Great another basic feature broken, can’t even navigate now.
Add that to not being able to watch in progress recordings from the start and some recordings playing in slow motion, which have now been broken for months.
How long are we going to have to wait for this to be fixed I wonder.? Plex seems to be regressing at an alarming rate. When are they going to start doing some real testing rather than just chucking it out there and hoping for the best.
Yet they still have time to release new features, many dont want or nice to have but not essential. While more core features get broken with no fix in sight.
1 Like
I’m seeing this too on my Hisense Android TV (current Plex build). It’s only cosmetic for me–no loss of functionality.
I don’t think this is just a useless error message, when it happens the item does not show as played, the item(show) description disappears, you go to a random episode or the beginning of the season.
1 Like
those are two separate issues, both of which are being looked into
1 Like
