Open blastframe opened 1 year ago
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:
"packages": {
"": {
"name": "my_cep",
"version": "0.1.0",
"dependencies": {
"brutalism": "^2.3.2",
"cep-spy": "^1.3.4",
"cluecumber": "^0.1.1",
"core-js": "^3.1.2",
"gehenna": "^1.1.4",
"starlette": "^1.0.7",
"vue": "^2.6.10"
},
"devDependencies": {
"@vue/cli-plugin-babel": "^4.0.0",
"@vue/cli-plugin-eslint": "^4.0.0",
"@vue/cli-service": "^4.0.0",
"babel-eslint": "^10.0.1",
"bombino-commands": "^1.0.4",
"boxen": "^4.1.0",
"chalk": "^2.4.2",
"eslint": "^5.16.0",
"eslint-plugin-vue": "^5.0.0",
"fs-extra": "^8.1.0",
"inquirer": "^7.0.0",
"make-runnable": "^1.3.6",
"ora": "^4.0.2",
"shelljs": "^0.8.3",
"types-for-adobe": "^1.5.0",
"vue-template-compiler": "^2.6.10"
}
},
Try npm i bombino-commands@latest
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?
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)