Hi @Kevin
Addressing your follow-up questions from the comments:
- Previously an index.html file was produced which manages the .appinstaller and other links (such as to the msixbundle directly). This index.html file also links to the .cer file, which is no longer present (as Trusted Signing happens in the pipeline after the
AppPackages
folder is created during the build).
A: When signing msixbundle with Trusted Signing, there is no need to have an extra .cer file. Just make sure the Publisher value in the AppxManifest.xml matches with the Subject name in the certificate profile.
- When installing the msixbundle, I can see that the certificate is valid, but expires after only a few days. Does this mean that we are required to update our sideloading app on our website every 1-2 days, to avoid a certificate expiry? I had hoped that once our msixbundle had been signed, it would remain valid?
A: As long as you call the timestamping, the msixbundle will remain valid, and you can install it.
Please refer to this link to set up the signing command with timestamping: https://video2.skills-academy.com/en-us/azure/trusted-signing/how-to-signing-integrations#use-signtool-to-sign-a-file
If the information helped you, please Accept the answer. This will help us and improve searchability for others in the community who may be researching similar questions.