Is it just me or is Attestation signing not giving any comment or
information about why the process failed just now? I tried different
browsers to same effect.
I can only see it failed in Preparation phase, which is too early.
Is it just me or is Attestation signing not giving any comment or
information about why the process failed just now? I tried different
browsers to same effect.
I can only see it failed in Preparation phase, which is too early.
Of course… something broke our automated process and the CAB file was not signed.
I also notice we need to have separate CAB files for x86 and x64 now
Where did you see that you need separate CAB files for x86 and x64? I combine all architectures into one INF, so such a requirement would be astoundingly counterproductive. You’ve always been able to sign multiple packages by making them subfolders of the top level in the CAB.