Turns out the Signing Certificate property had the same chicken-and-egg bug as the images. If you pull commit 2d8bed9 you should be able to provide a certificate through the UI.
You can generate a pfx file suitable for use during development and testing using something like:
- You only need a certificate if you want to install a packaged version of your app (i.e. wrapped up as a single appx file). That’s particularly useful for devices that are in the default ‘Sideload apps’ mode; it may be less relevant for devices in Developer Mode where you can use an unsigned version (provided you don’t package it).
- It’s important that your certificate Subject name matches the Company Distinguished Name, otherwise signing will fail.
- The current implementation doesn’t support password protected certificates.