We have a number of apps written in C#, some headed some non-headed (background). They are able to communicate with each other via Windows.ApplicationModel.AppService.AppServiceConnection, which works rather good on ARM on e.g. a Raspberry Pi 3 B (which works well enough with Windows 10 IoT Core, no hardware rendering tho which is a bummer). We are not using Native Tool chain when building our apps for ARM. As building them with Native Tool chain takes forever, so we would like to avoid it if possible.
For non-headed (background) apps built for ARM64 running on Windows 10 IoT Core Windows.ApplicationModel.AppService.AppServiceConnection seems to not work while debugging, when we try to connect to a app service we are greeted with AppServiceConnectionStatus.AppUnavailable. Which means:
// The package for the app service to which a connection was attempted is temporarily
// unavailable. Try to connect again later.
Even when we try to connect later the app fails to do so. A foreground app succeeds to connect, after a while, after a number of tries.
In practice this makes it almost impossible for us to debug (and therefore develop) our apps for ARM64.
To summeries debugging on ARM64 works but Windows.ApplicationModel.AppService.AppServiceConnection does not work as expected when debugging.
