Open heiyehk opened 4 months ago
Can you double check whether the private key you used to sign the updater bundle (that generated the .sig file) belongs to the pubkey defined in tauri.conf.json? And also check whether the "signature" field in the server json is the full content of the .sig file that belongs to the updater bundle your server hosts (the .sig file changes every time you re-build your app!)
Can you double check whether the private key you used to sign the updater bundle (that generated the .sig file) belongs to the pubkey defined in tauri.conf.json? And also check whether the "signature" field in the server json is the full content of the .sig file that belongs to the updater bundle your server hosts (the .sig file changes every time you re-build your app!)
I found this problem, I configured it in tauri.config.json
"wix": {
"language": [
"zh-CN",
"en-US"
]
}
Then the signature
of the generated latest.json is zh-CN
, but the updated package is en-US
. And there is only one language update package in latest.json, and signature
does not correspond to it. How should I deal with this?
I am following below steps
run : npm run tauri signer generate
Got public and private keys
Put public key in tauri.config.json (pubkey) node
Put private key in system environment variable using cmd: set TAURI_PRIVATE_KEY=
cmd : npm run tauri build
Got updated build (myapp_1.0.2_x64_en-US.msi.zip) and .mis.zip.sig files
Because I have my old version build i.e. 1.0.1 run this app and got that error (Verify signature error: UnexpectedKeyId)
Now please suggest where I had done mistake in the process..
I had used below packages:
"dependencies": { "@tauri-apps/api": "^1.5.2", "axios": "^1.6.7", "react": "^18.2.0", "react-dom": "^18.2.0", "react-router-dom": "^6.22.1" }, "devDependencies": { "@tauri-apps/cli": "^1.5.8", "@types/react": "^18.2.15", "@types/react-dom": "^18.2.7", "@vitejs/plugin-react": "^4.2.1", "typescript": "^5.0.2", "vite": "^5.0.0" }
=================
tauri.config.json { "$schema": "../node_modules/@tauri-apps/cli/schema.json", "build": { "beforeDevCommand": "npm run dev", "beforeBuildCommand": "npm run build", "devPath": "http://localhost:1420", "distDir": "../dist" }, "package": { "productName": "myapp", "version": "1.0.2" }, "tauri": { "allowlist": { "all": false, "shell": { "all": false, "open": true } }, "windows": [ { "decorations": true, "maximized": true, "closable": true, "minimizable": true, "maximizable": true, "resizable": true, "fullscreen": false, "minWidth": 800, "minHeight": 600, "visible": false, "title": "myapp" }, { "maximized": true, "closable": true, "minimizable": true, "maximizable": true, "resizable": true, "fullscreen": false, "minWidth": 800, "minHeight": 600, "decorations": true, "title": "myapp", "url": "splashscreen.html", "label": "splashscreen" } ], "security": { "csp": null }, "bundle": { "active": true, "targets": "all", "identifier": "my-app", "publisher": "my app", "shortDescription": "my app", "category": "cricket", "copyright": "Copyright © 2024 myapp", "icon": [ "icons/32x32.png", "icons/128x128.png", "icons/128x128@2x.png", "icons/icon.ico" ], "windows": { "webviewInstallMode": { "type": "offlineInstaller" }, "certificateThumbprint": "bc2404889120b9f130ff5iouubbaad69b8c5aa46", "digestAlgorithm": "sha256", "timestampUrl": "http://timestamp.digicert.com", "tsp": false } }, "updater": { "active": true, "endpoints": [ "https://domain/windows/x86_64/1.0.1" ], "dialog": true, "pubkey": "dW50cnVzdGVkomlkio1lbnQ6IG1pbmlzaWduIHB1YmxpYyBrZXk6IDY4OTQ4NzY5MzNBQjNCMjYKUldRbU82c3phWWVVYUY5SmFFZ21CaTk4T1lGMHA1dlVZUXlWZmFSUkpQclJQUVRNSzY3dTROUDcK", "windows": { "installMode": "passive" } } } }
Describe the bug
When I use the updater function, it has triggered the check. Then I use update.downloadAndInstall and the download completes, but the error
Uncaught (in promise) InvalidSignature
is returned. I first used the release address of github, and then I used a separate https domain name to test, but the same error was reported.Reproduction
No response
Expected behavior
No response
Full
tauri info
outputStack trace
No response
Additional context
No response