Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.

If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

And always feel free to hit us up on Twitter @MxdRealityDev.

Unable to connect to Sharing Service on same device as UWP application

edited April 2018 in Questions And Answers

I have a really bizarre scenario going on with UWP and SharingService. I have 4 computers, 2 of which have Unity 1.2p4 installed. On each machine with Unity installed, I can build a UWP (PC) app the connects to the Sharing service running on the local device either by using the machine name, IP or localhost.

But when I take that same app (deployed via store appx) to my other two devices that don't have Unity installed, they will not connect to the sharing service (running on the same machine) via localhost/machine name or IP.

If I connect to a sharing service on another machine, my UWP app connects just fine.
If I connect another device to the sharing service on the same device as UWP app, they also connect successfully.

So my UWP app will connect to the sharing service, but only when it's on a different device when installed from APPX.

So this doesn't appear to be a firewall issue. I've tested it with firewall on and off entirely to no avail. Thought it may be a wifi issues, but plugging in doesn't resolve it either. I've also got the right capabilities selected - internetclient, internetclientserver and privatenetworkclientserver

Has anyone else experienced this or could recommend some suggestions to try and troubleshoot?



  • I managed to find a work around, and that's to deploy using Remove Debugging. Seems there's a bug in the Appx deployment

Sign In or Register to comment.