-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error - the timestamp returned from the chosen TSA could not be verified #17
Comments
Hello, what version of this package is in your report? |
Hello! Thanks for the reply. I'm not sure if this is what you are seeking or not, but this is from the package-lock.json file:
|
Try |
Thanks for the suggestion. I have tried the command you provided, but got the same error. What should I be running for the certificate password? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I've run
npm run register
thennpm run sign
. The command prompt runs ZXPSignCmd and returnsSelf-signed certificate generated successfully
. When it goes to sign the zxp, I'm getting this error:Error - the timestamp returned from the chosen TSA could not be verified, so the ZXP created is likely to be rejected by other tools. Please recreate your ZXP with a different trusted TSA.
I'm also getting a Signing Complete / .ZXP is ready message when the .zxp hasn't been generated and the archive folder is empty. I am on Windows 11 and using ZXPSignCmd 4.1.103.
Possibly related: ZXPSignCmd Timestamp error (possibly SHA1 issue)
The text was updated successfully, but these errors were encountered: