@jsyarrow , [MENTION=3956]James Barnette[/MENTION]
That sorted out the signing side of things. Everything now cooks,builds,packages and deploys without a hitch for UWP32 and UWP64 for the pc.
Now that the packages are signed I am able to successfully install them on my XBO through the device portal.
When I start up the application through the device portal the splash screen loads up on my TV and hangs there for a while. I’m then kicked back to the dashboard on the XBO and receive the following message in the device portal.
I don’t get any debug information(that I know where to find at any rate). After reading through the known issues for UWP on XBO and the resources allocated to UWP on XBO, I’ve come to the conclusion that the app is likely exceeding the available resources and throwing a memory allocation failure and closing. I get the feeling that this is as far as I’m going to get in terms of testing on the XBO, I could be wrong of course and would be very happy to be proven so. What I imagine is that the engine would have to be optimized to run on such limited resources, likely in much the same way as it has been to run on android. That said I am probably going to try and package a scalable prototype that I’ve been working on (and have packaged and run on android) for further testing.