Agreed, fix core issues before adding new features. It doesn’t help to add a shiny new widget when you are unable to do something as basic as watching a show that is currently being recorded - My DirectTV could do it 15 years ago, why can’t Plex?
Having the same issue on multiple clients for weeks now; Android phones and Nividia Shield.
Plex server version 1.23.0.4497. Restarting the server is a temporary work-around.
Would be great to get this resolved. Thank you
Same issue with my Nvidia Shield Pro. Been that way for a while. Hoping they get it sorted. 
Same problem on Nvidia Shield with all of the latest versions of software.
Pleas fix!
Hope to see resolution to this soon. My Plex on my Nvidia Shield hasn’t been working for a few days. I can still get it to play from my iPhone and do chromecast but that’s a temporary work around
Captured the Error again this morning when I navigated into watching a show that was recorded on the DVR “Showing toast: Unable to navigate, item not found.”
UnableToNavigate.txt (98.5 KB)
I have the issue for a while as well. Mainly use Fire TV products to watch with. I get the error when I try to delete items. It also seems to forget the resume point and start from the beginning when I ask it to resume on DVR items. I have been browsing to the network share and deleting items manually.
Almost 2 months now and still this problem had not been fixed. Plex devs, please fix core issues like this instead of adding more and more functionality.
Fix is needed desperately, we probably all paid good money for a product that is becoming unusalble. I think Emby is worth a look, or even Jellyfin for free. But I love my plex…
Seeing this issue on Android TV when autoplay tries to start the next episode. It appears to get stuck, black screen, then when clicking stop it returns to season view and reports the “unable to navigate, item not found” error
Adding my experience of this issue to the growing list - for many weeks now when watching any TV series on my personal PLEX server, whenever the next episode tries to play, I get the error “Unable to navigate: Item not found”.
I have several friends using my PLEX server and can confirm that this issue only affects those of us, myself included, when using the Amazon FireStick client - when we use Xbox, PlayStation, Windows, Android (direct or cast), the issue is not experienced.
Pretty much the same issue that has been described countless times above. Using Shield Pro latest model and Chromecast ultra. It’s irritating to say the least. The UI seems to update every few seconds with this issue.
Hoping it is fixed soon.
Cheers!
Well, I don’t know if a change has been made, but this evening after an episode ended, I left PLEX playing and went to the kitchen knowing it would fail again and I’d just come back and go back.
IT PLAYED THE NEXT EPISODE
This is the first time it’s worked in months.
Not sure if it was an update or a fluke but I will let it play out in future and keep monitoring.
Having the same issue here. Client 8.18.2.25850 on Android TV
Having the same issue on Fire TV Stick 4K using Plex. After playing the next episode, audio & video are not in sync and the whole app is sluggish. The only fix is rebooting my Fire TV. Please look into fixing this soon.
1 Like
I’m having the same issue on both of my Shield TV boxes. It is very aggravating.
it’s hard to remember a time where i used plex and there wasn’t some sort of ongoing bug that the plex developers just ignore for months/years even though it affects the majority of people, maybe never?
4 Likes
I just updated plex server and its still happening. 
Happens to me too, on 2 x Nvidia Shield TV Pro and 2 x Mi Box 3 (4K). Even just having a tv season open this popup will appear by itself even though I’m not doing anything. Every single time I stop an episode it automatically appears.
Yes I use stablebit drive pool and this issue has been happening anytime files are automatically moved within the storage pool. It’s definitely a NEW glitch because my server has been running this way for 7 year and no issues till about a month or so ago. So it definitely has to do with files in use.
