Custom Metadata Providers does not call match/meta on Mac PMS

peter.a.bayliss
Sun, 01 Mar 2026 21:03:03 +0000
Dev/API Corner

I have a custom metadata provider developed and running developed in c# and hosted on my development machine.

But when I try and use it from a MacOS PMS I can add the Provider and Agent but when I add it to a Library and it scans it doesn’t even attempt to call the match or metadata endpoints. On the Windows PMS it works fine.

It doesn’t matter where I host/develop the Provider on the Windows or Mac (I am moving to dev on Mac so moved all my development stuff there and started using the Mac PMS to test against) the Windows PMS always works the MacOS PMS doesn’t.

I am using the latest version 1.43.0.10492 on both Windows and Mac.

I have looked at the logs and in the WIndows machine can see lots of entries where it is making requests to the /match endpoint etc but on the Mac machine there is no calls being made. It looks like it kicks off as there is an entry but then it says:

[MetadataAgent/tv.plex.metadata.agents/Response::fetch] feature path is empty

As it is the same Provider on both I know the Provider is sending the correct Features during the setup of the Provider/Agent.

I assume this is a bug in the MacOS PMS?

I can look into more diag if required - for now I will just have to use my Windows laptop and PMS to test againstc and carry on (am still loving the Custom Metadata Providers and also the API once I’ve got my head around some of the inconsitances I think there are in naming of things and switching between using integers and strings for things though sure there is logic in there).

5 posts - 2 participants