Plex App for Mac: Custom Filter Error/Library view stuck in error state

When selecting Custom filter in the dropdown in Library View, I get this error message: There was an unexpected error. Please visit our forums if you continue to experience problems.

The main problem though is that now my library is stuck in this error state, because the Library view is stuck on the custom filter which again gives the error.

Is there a way for me to reset the state of the Library View to default instead of the last used state (custom filter). I can then just stay away from the custom filter until that gets fixed. I tried restarting and re-installing but no luck, every time I try viewing my library I get the error.

Thanks, H

Server Version#:1.18.0.1846-f62172e99
Player Version#: 1.3.1.916-1cb2c34d

2 Likes

let’s get some Log Files while in debug mode sir.

  • Reboot the Mac
  • Get PMS up and running and give it 6min to initialize (makes clean logs)
  • Use the web app and Settings - Troubleshooting - Download Logs
  • Zip and upload what it gives you, but just the logs that were changed.
1 Like

Here are my logs.

Plex Logs.zip (101.2 KB)

Aww you seem to have captured VERBOSE logging, even though I didn’t have that checked in my picture above. Was that an oversight?

1 Like

Well I followed your instructions, Debug level is enabled and verbose is not selected. I went through the whole process again but the logs look the same to me, verbose logging seems to be on even though not selected!?

36

Here are the new logs:
Plex Logs.zip (92.3 KB)

Edit:
I did find this log under /Library/Application Support/Plex/Plex Media Server/Logs/Plex Media Server.log and it seems to be non verbose.
Plex Media Server.log.zip (4.2 KB)

Thanks for trying. That persistent VERBOSE is annoying, yeah.
It’s possible you need to Disable - Save - Enable - Save.

The picture I showed has a circle around the section that’s active.
It’s called General, and it’s right next to Remote Access.

You attached a screen shot of the debug section lol.

I also mentioned exactly the steps to download the logs afterward.
I realize it’s confusing there are other ways to achieve something similar.
I’ll have a look at what you attached. It might be enough.

Pretty clean logs. One or two odd errors that may be solved by upgrading PMS to a newer version, but at least there’s zero SQLITE3 database issues.

Oct 08, 2019 16:28:25.775 [0x70000d2e5000] DEBUG - Connection Tester: Successfully tested media server HALHUB to be at https://192-168-0-111.fe98841248004000984cffc480bc6c50.plex.direct:32400 in 15 ms

Oct 08, 2019 16:28:25.782 [0x700016866000] DEBUG - Connection Tester: Successfully tested media server Offline to be at https://192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct:32400 in 22 ms.

Oct 08, 2019 16:28:25.783 [0x700016866000] DEBUG - HTTP requesting GET https://192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct:32400/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Oct 08, 2019 16:28:25.783 [0x70000db15000] DEBUG - EventSource: Resolved 192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct to 192.168.0.106
Oct 08, 2019 16:28:25.791 [0x70000db98000] DEBUG - EventSource: Connected in 7 ms.
Oct 08, 2019 16:28:25.791 [0x70000db98000] DEBUG - EventSource: Wrote data, reading reply.
Oct 08, 2019 16:28:25.793 [0x70000db15000] DEBUG - EventSource: Read HTTP reply header.
Oct 08, 2019 16:28:25.793 [0x70000db15000] DEBUG - EventSource: Successfully connected to 192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct.
Oct 08, 2019 16:28:25.802 [0x700016866000] DEBUG - HTTP 200 response from GET https://192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct:32400/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Oct 08, 2019 16:28:25.803 [0x700016866000] ERROR - Unknown metadata type: 
Oct 08, 2019 16:28:25.803 [0x700016866000] DEBUG - Connection Tester: The server Offline is a valid media provider.
Oct 08, 2019 16:28:25.803 [0x700016866000] DEBUG - HTTP requesting GET https://192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct:32400/security/token?type=delegation&scope=all&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Oct 08, 2019 16:28:25.820 [0x700016866000] DEBUG - HTTP 200 response from GET https://192-168-0-106.dab0ba1461b943a9a12b4d7950e95a01.plex.direct:32400/security/token?type=delegation&scope=all&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Oct 08, 2019 16:28:26.554 [0x70000d2e5000] DEBUG - HTTP 200 response from GET https://192-168-0-111.fe98841248004000984cffc480bc6c50.plex.direct:32400/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Oct 08, 2019 16:28:26.554 [0x70000d2e5000] ERROR - Unknown metadata type: 

So it looks like I see Unknown metadata type
I guess we’ll have to google some of that.

1 Like

So how can we reset this library view? hmm :slight_smile:

1 Like

LOL Well that was dumb of me.

Anyway I found a fix here: "unexpected error" after enabling custom filters
Restoring plex settings to defaults resets the library view to defaults and my library re-appears. Custom Filter is still broken though, both on Mac & Windows apps.

Thanks so much for the help :wink:

2 Likes

The bug at the root of this will be fixed in v1.4, due in a week-ish.

4 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.