I’m not sure if this is the right place for bug reports - please advise if I should post or copy this elsewhere.
I have been having problems with my photo library causing the client to stop working when I click into nested folders. It says “Something went wrong - An unexpected error occurred.” and then the client becomes completely unusable. I have to close and reopen it in order to use Plex again.
It does not seem to matter which folder I click into - clicking around at random, they all trigger the same problem. I checked in the browser by accessing my NAS instance directly, rather than using the desktop client, and this error seems to be the culprit: TypeError: y.At(...) is undefined) in the function deselectAllMetadataListItems
I’m guessing the issue here is this bug is unexpected so the error is not handled safely, which bubbles up and softlocks the client.
Reproduction steps: open Plex, click into my photo library, click Library tab, click a folder, click another folder inside that - error displays.
Local workaround: Strangely, these alternative steps seem to fix the bug for me: open Plex, click into my photo library, click Timeline instead of Library, and gently scroll all the way to the bottom. Afterwards, I can safely click Library and then whatever folders without the bug occurring. It seems that this “warms up” my photo library and prevents the bug. It’s also notable if I only scroll a little bit (in order of newest to oldest), I can access newer folders safely, but still see the bug if I try to open an older folder.
Not sure if my issue is the same or related, but I’m also seeing “Something went wrong - An unexpected error occurred.” occasionally when accessing photos. First time I noticed was a few months ago. Today I updated the server to 4.134.2 (Windows 11) then the error happened every time I accessed a photo (all other media are working fine). I cleaned the database and this improved things - now the error is only shown sporadically.
But I’ve also noticed on the iOS app (v8.38) on both my iPhone SE 2020 & iPad 6th Gen, if I view a photo, then click the down arrow at the top-left to minimize the display window, the app crashes.
I’m experiencing the same exact issues as the OP as detailed in “Reproduction steps.” Clicking any subfolder within a folder generates the error message. I’m using a MacBook with Plex Web Version 4.133.0 / Version 1.40.5.8761 and have also had the iOS app crash on iPhone and iPad when accessing photo subfolders.
Thank you so much for posting this. It solved my issue as I was just about to install other photo servers. I have over 80K photos and wonder if there is a limit.
Here to report that I’m also having the same issues. But I think there are two problems reported here:
The “Something went wrong” error when clicking into folders from the web client, and
iOS app crashing when trying to minimize/exit the photo display
Do we know if these are actually the same underlying issue? Or is the iOS app crash reported/tracked/acknowledged elsewhere? Just want to make sure that it doesn’t get lost.
I can confirm I’m having the same issue, as someone with arguably hundreds of thousands of photos organized in folders (usually 1 sub level deep) for performance reasons. this happens no matter the library or how deep the folder structuring goes.
I can also confirm that when viewing on browser OR PMS client (not the server) the issue persists, it completely locks plex up on the web or client, the only way to unlock it in terms of getting functionality back is to click the “wrench icon” and go back to home screen, this seems to unlock plex from whatever wierd state it gets put into.
Also iOS app freezes every time I access ANY photo library, but it doesnt crash till i enter the folder then use the “back” button to go out of the folder and then plex will hard crash on iOS. (thats reproducable 100% of the time for me)
Exact the same behavior for me. Plex Server 1.40.5.8854 on a Synology NAS. No matter if i use the plex.tv domain or my subdomain from synology to access my plex server. If i try to view some photos over the web always the error “there went something wrong” shows up when i go to the folder/album where the photos are stored. The folder/album structure before the folder that contains the photos is never a problem… If i then reload the page by pressing F5 and let the URL untouched i can view the photos. If i then browse to another album/folder the same error shows up again.
I have the same issue and the “solution” works for me as well.
One difference is that I have one folder that’s on the second level that contains no sub-folders. Clicking on that worked before this solution was implemented.
On Windows, Plex gives the “something happened” error if you try to go one subfolder lower in photos, as everyone seems to agree. But, if you click reload on the browser (I’m using Firefox) Plex will continue into that subfolder and you can review the photos. However, when you try to exit that folder you get the same error and, as was stated, you need to click the wrench to move on.
I am also having this problem in version 1.40.5.8921 when trying to view it on my iPhone 13 pro and iPad air (m2).
Another workaround for me is before exiting photo display, go to the first photo in the folder using the sidebar and this no longer crashes the app for me.
I’ll add my hat to the ring. Happens in my Windows client, saw it today on: Version 1.100.1.221-94aa83fb of Windows Client. Running Linux server Version 1.40.5.8854.
I added a bunch of new photos (~2K) to my ~80K photo/video library. When going into some of the new albums to peruse them so I could later set the poster, I’d get the error. (Something went wrong. An unexpected error occurred)
This is when I’m on library, and have “Photos” selected where you see the year first, then dive in from there. If I select library then “albums” where it shows the file folders it seems to work better.
It locks up the client - I can’t go to Home or any other libraries unless I quit client and restart. HOWEVER, if I select Settings (wrench) then I can go back to home, then go back albums and to the place that gave me the error and it usually works the second time without having to quit the client.
It’s more likely to happen to recently added stuff, but happens sometimes to older stuff too.
The timeline thing didn’t work for me - do you have to make sure ALL the photos fill in as you scroll down? - because that would take forever…
On my Roku, I don’t get the error. But right after accessing a photo album on my Roku, I can still get the error on my Windows client for the same album.
