Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Signing fails with error #17

Closed
MTRNord opened this issue Jan 5, 2021 · 9 comments
Closed

[BUG] Signing fails with error #17

MTRNord opened this issue Jan 5, 2021 · 9 comments

Comments

@MTRNord
Copy link

MTRNord commented Jan 5, 2021

ℹ️ Info

Version: 0.1.8

💬 Description

The signing fails with:

getting config values..  [√]
validate config values..  [√]
create icons folder..  [√]
copy icons..  [√]
create manifest file..  [√]
copy VCLibs files..  [√]
packing..  [√]
singing..  Error information: "Error: Store::ImportCertObject() failed." (-2146893808/0x80090010)

SignTool Error: An unexpected internal error has occurred.

📜 Pubspec.yaml

msix_config:
  display_name: Famedly
  publisher_display_name: Famedly
  identity_name: com.famedly.chat
  msix_version: 0.28.1.0  
  publisher: CN=Famedly GmbH
  certificate_path: ./code-signing-famedly.pfx
  certificate_password: placeholder
  capabilities: 'internetClient,location,microphone,webcam,chat,picturesLibrary,videosLibrary,documentsLibrary'
@YehudaKremer
Copy link
Owner

Hey @MTRNord

its looks like an internal error of the SignTool

let's check if there a problem with the certificate file,
please import and then export your certificate file as .PFX with the tool certificate-utility-for-windows
as shown here https://www.advancedinstaller.com/forums/viewtopic.php?t=35282

@MTRNord
Copy link
Author

MTRNord commented Jan 5, 2021

That tool seems to not work on linux with wine for me. But i can inspect that cert with openssl pkcs12 -info -in <cert file path> just fine. However another one in our company tried the tool on windows and it was possible to import and export the certificate. Even after that we get the same signtool error.

@MTRNord
Copy link
Author

MTRNord commented Jan 12, 2021

Found the issue :) The publisher field not only needs CN but ALL fields in the CORRECT order. ^^ Now it works

@MTRNord MTRNord closed this as completed Jan 12, 2021
@YehudaKremer
Copy link
Owner

I'm glad you found the problem well done!
Can you please give me an example of valid publisher to put in the documentation

@MTRNord
Copy link
Author

MTRNord commented Jan 12, 2021

Our publisher now is publisher: 'CN=Famedly GmbH, O=Famedly GmbH, L=Berlin, S=Berlin, C=DE' but it is depending on the certificate. Basicly all the fields in the subject part of the certificate. And in the order top to bottom in that.

@YehudaKremer
Copy link
Owner

YehudaKremer commented Jan 12, 2021

thank you Marcel,
i added this example here

@portlek
Copy link

portlek commented Mar 26, 2021

power shell requires
I found the subject of my certificate to run Get-PfxCertificate then it will ask your .pfx file path;
image
just give the .pfx file path then enter, don't fill the FilePath[1]: enter again, it will ask your certificate password, type it, that's it.

@feemagdev
Copy link

pf

Thanks i got the subject and put it in publisher. works like charm.

@acamenhas
Copy link

@feemagdev I'm having this problem too.. what tags in publisher (and in what order) that you have putted?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants