You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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
The text was updated successfully, but these errors were encountered: