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).
Yep it is (I did recheck and even hard coded the example in the documentation just incase but that didn’t work either).
I am developing/debugging the Provider on my MacBook. When I point my Windows PMS (which is in a Windows VM) development box) to the provider it works, accesses Matches, MetaData, Images, etc so the Provider is definitely working (in fact I am at this very minute working on it so it def is working ok - though it’s taken me a while to do it!!!).
It is just when I point my local Mac PMS instance to the Provider it just doesn’t even attempt to access use the match/meta endpoints (there are no calls being received – as apposed to the call being received and failing). It obviously can access the Provider itself otherwise I wouldn’t be able to add it as a Provider and Agent. But I get no attempts to access the endpoints.
I will try again later - switching to my Mac PMS - just in case I’ve messed something up, but want to just finish off sorting out the images endpoint delivery.
Would there be a difference in the way the Mac vs Windows PMS handle the Custom Providers internally - not sure how much separation there is between code for different OS’s?
Dev Environment:
MacBook Air (Apple M2 - ARM)
MacOS Tahoe Version 26.4 Beta (25E5218f)
Rider IDE
.Net Core 10 / C#
NGROK (for providing external tunnel - this is how I calls are not even being made - rather than my Provider is failing)
Windows PMS:
Windows 11 (ARM) in a VMWare Machine running on the MacBook Air
Version 1.43.0.10492
MacOS PMS:
Running on the Dev Environment
Version 1.43.0.10492
There is no difference between Mac and Windows with the implementation so it might be something unrelated on the Mac causing a problem.
I’d have to take a look at the server logs if you could provide those.
Aplogise I have it working now.
Really don’t know what was going on but did a quick uninstall and a few other clean up is working.
As part of my testing I add the provider, agent, library, scan library via API’s (to help automate) then remove library, agent and provider and clean up. Not sure if this was the case and it messed up my Mac PMS but as I say a quick ‘switch on and off again’ worked!!!
Sorry for wasting you time on not properly checking.
Still loving this ability though, game changer for when the TVDB etc don’t work well.
