Publishing does not work on Xbox One

[ovesennet]

Hi!
I'm implementing ssdp publishing with RSSDP in a UWP / Windows 10 app for both desktop and Xbox.
I can publish successfully running on Windows 10, but on Xbox it does not work. I get no exceptions.
Any idea on why it does not work on the xbox device?

[Yortw]

Hi,

I'm afraid I don't. Given the Universal Windows Runtime I would have expected it to work on xbox if it worked on Win10, but I do not have an Xbox of any sort on which to test.

Things to check/try;

• Create the publisher with a specific local IP, in case the xbox has two and is using the wrong one.
• Does the xbox have any kind of firewall? Does it need to be modified?
• Create the publisher with a logging component and see if it records any 'silent' errors.
• Try a different local port (not 1900) in case xbox is using 1900 for it's own SSDP implementation and not sharing the data.

[ovesennet]

Hi!
No, I'm sure it is using the correct IP. I tried different ports, but no luck.
Actually, the Xbox is publishing it's own services, so I can find it that way, but I cannot be sure it is running MY service, I have to poll for an endpoint then.

[Yortw]

If you plug in a logging component, does the log show anything interesting?
Unfortunately I don't have any way to test and am running out of ideas already.

[Yortw]

Apologies for leaving this issue unattended for so long. Its likely you've moved on. However, in case you haven't given up, or for anyone else who stumbles across this issue;

If anyone is still interested it would be interesting to see if anything has changed with the new v5 package, which uses different targets, depdencies etc.

Thinking about this with a fresh mind, it's also possible that because "the Xbox is publishing it's own services," it might be receiving the search packets on port 1900 and blocking the RSSDP publisher from receiving them, though I would have expected an exception saying the socket couldn't be opened/bound if that were the case.