search

microsoft / project-rome

Code samples and documentation of Microsoft's Project Rome SDK
https://aka.ms/projectrome
Creative Commons Attribution 4.0 International
448 stars 101 forks source link

Getting RemoteSystemUnavailable for PCs running Windows 10 version 1809 when available via proximity. #59

Open MahdiGhiasi opened 5 years ago

MahdiGhiasi commented 5 years ago

I'm getting RemoteSystemUnavailable error when trying to connect or launch urls to a PC running 1809, if that PC is available via proximity. (However, when it's not available via proximity and is using cloud, it's fine)

This issue has been reported by my app's users on Android->Windows and Windows Mobile->Windows scenarios.

And it seems that Windows 10 version 1809 is only affected, and 1803 is fine.

tadam-msft commented 5 years ago

I'm seeing this working on the latest builds of Windows, is this still happening for your app?

MahdiGhiasi commented 5 years ago

I'm still seeing this on latest updates of Windows 10 version 1809. Have you tested it on v1809 or v1903?

bpaliswiat commented 5 years ago

Can you check your Settings->System->Shared experiences and make sure your account doesn't require attention (this would show on the top of that settings page)

MahdiGhiasi commented 5 years ago

@bpaliswiat No, it says "All accounts are working correctly."

Please note this bug only appears when Rome API says that the remote device is available locally. (I think network discovery should be on so it can see the device is available in proximity)

I observed this on three different PCs and two different Microsoft accounts, and still can reproduce them from both Android and Windows Phone to my Windows 10 PC running the latest update. (Latest version of my app falls back to REST API when this issue happens, but I disabled it and created a custom build, it still happens)

Also another thing that might be worth noting is that, my Android app uses Rome Xamarin for Android SDK, which is unfortunately behind the native Android one. So maybe this is an issue that is fixed on newer SDK versions, but is not working on Xamarin one and Windows Phone, as they're both older?