Open kmelmon opened 4 years ago
Guess is that we're doing something wrong with how the CLI creates the certificate.
Fast forward 6 months... @asklar I know we're having different issues with certificates and VS versions. How relevant is this issue still?
@chrisglein this may still be relevant, I don't think we've looked at cross-machine deployment. There's also this other issue that may be related/the same: #4936
Currently, the CLI-generated app template has an issue with the certificate that's included with the app. If you build an appx package with this certificate, the app can be installed locally, but cannot be installed on another user's machine due to a certificate error.
Create a new app using the CLI. Then build an appx package via Project => Publish => Create App Packages... Click through to the "Select signing method" screen. VS then displays a message indicating something is wrong: "The selected certificate is password protected. The password is incorrect or missing".
I noticed we have this attribute in the .vcxproj:
Apparently VS is not happy with this attribute. I believe this was added to get around an issue in the CI loop, but this isn't working as expected.