Unexpected error when loading library

Server Version#: 1.18.0.1913
Player Version#: 1.3.1.916-1cb2c34d

I was recently messing around with my Plex app and clicked on Custom Filter to check out the feature. However, upon clicking on it, the error “There was an unexpected error” shows. Whenever trying to access the library, “Unknown metadata type: folder” shows up in the logs. This is only affecting the Plex app and not the web app.

3 Likes

Which OS is this on? Windows or Mac?

Same here. Latest Server and Player installed on Windows 10.
I tried to switch to a predefined filter (I think it was Duplicates) in my main movie library and the error message appeared. Now it’s stuck there and I can’t open the movie library any more. I turned off the option to remember the last tab so I could at least switch back to recommended view.
Every time I click on library view the error message appears instantly.
Resetting the view changes has no effect on that issue.
The web app works fine, only the new player app has the problem.

Windows. I’ve tried deleting the app completely then reinstalling it but it doesn’t work. If I close my Plex server while trying to access the movie library, I can switch tabs from “Library” to “Recommended”, so I’m guessing if the Plex App could forget the last filters I applied it would go back to working normally.

1 Like

Just started seeing this on OSX after upgrading last evening, behavior same as noted above, switched to a custom filter and now that entire portion of my library (~1200 albums) is now unviewable.

A few weeks ago nothing could stream via Google Cast, now a majority of my music library is inaccessible through the app. Does Plex even employ a QA department anymore? This is getting ridiculous.

Version 1.18.0.1913-e5cc93306
Version 1.3.1.916-1cb2c34d

Same here with the same server and player versions on three different Windows 10 machines showing the error message straight away when attempting to access my music library (containing about 13,000 tracks). iOS app and Plex Web are fine, as are all my other (smaller) libraries.

The problem started for me when I upgraded the server to 1.18.0.1846.

Optimizing and repairing the database has made no difference.

Just adding a +1 to the conversation…happens on Windows 10 Desktop App Player

Version 1.18.0.1913-e5cc93306
Version 1.3.1.916-1cb2c34d

Ubuntu Server 18.04.3 LTS (GNU/Linux 4.15.0-65-generic x86_64)

this is the console error

1 Like

HERE IS THE FIX!!!
You have to do a cosmetic reset, by which the organization of your home page is reset and the current filters too. It has zero affect on metadata, or media.

Section

Confirmation

This suggested fix/workaround did not work for me

did not work for me as well

Here is what worked for me:

In the Plex App, access the settings and make sure “Show Advanced” is on. Under Plex --> General, turn off settings sync. Go to Plex --> Debug and click on restore defaults.

4 Likes

this solution did not work for me. still same error in console.

1 Like

Issue appears to be specifically for the Live TV/DVR section, the restore defaults fixed all but that section…

1 Like

This isn’t working for everybody, please stop marking this as a “solution”

It’s his thread and it solved it for him…

Always appreciate when a mod pops up on this forum to salt the wounds of users who are continuing to have problems with their product.

2 Likes

do other users in this thread not matter? serious question since you raised the point.

If it fixes the problem for everybody everywhere, that’s a “solution”

If it fixes the problem for some people some of the time, that’s a “hack” or more politely a “workaround”

Marking this as fixed would seem to absolve Plex devs from committing any resources to seeking a solution for the remainder of us who still can’t use the desktop player.

It’s just the way marking a solution works with this forum software. When the thread starter receives a solution they can mark that post as the solution. It has nothing to do necessarily with other users issues.

This is not the same as marking the bug as a resolved. As pointed out in other threads an internal release is currently being tested.

1 Like

Thank you for that clarification. I continue to maintain that forums/bulletin boards are a poor way to manage bug reports and properly communicate issues like these, and their solutions, to the customer base at large.

Invest in a ticketing/bug tracking system. Users helping users is fine for some things but when there are actual problems Plex needs a clear and effective way of communicating that, this isn’t it.