tauri: [bug] Verify signature error: InvalidSignature

Describe the bug

I have two versions of the test app. One is v1.0.0, and another is v1.0.1. I use a plain JSON file put on the gist as the update file. I put the updates on the github release.

When I opened v1.0.0 the updater dialog shows as expect, but there was no response after clicking on the Yes button.

image

I have listened the tauri://update-status event, and it gave out an error message bellow:

image

I am pretty sure that I have generated the update signing key pairs as the docs said. And the update signing is success without errors(pls check the Stack trace).

I will attach some key fragments in the Additional context section.

Reproduction

No response

Expected behavior

Install the update and relaunch app successfully.

Platform and versions

Environment
  › OS: Mac OS 10.13.6 X64
  › Node.js: 14.18.0
  › npm: 6.14.15
  › pnpm: 7.2.1
  › yarn: 1.22.19
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-apple-darwin 

Packages
  › @tauri-apps/cli [NPM]: 1.0.2
  › @tauri-apps/api [NPM]: 1.0.1
  › tauri [RUST]: 1.0.2,
  › tauri-build [RUST]: 1.0.2,
  › tao [RUST]: 0.12.0,
  › wry [RUST]: 0.19.0,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:3000/
  › framework: Vue.js

App directory structure
  ├─ dist
  ├─ node_modules
  ├─ public
  ├─ dist-isolation
  ├─ src-tauri
  ├─ .git
  ├─ .vscode
  └─ src

Stack trace

Bundling tauri-app_1.0.0_x64.dmg (/Users/soon/projects/tauri-app/src-tauri/target/release/bundle/dmg/tauri-app_1.0.0_x64.dmg)
     Running bundle_dmg.sh
     Signing /Users/soon/projects/tauri-app/src-tauri/target/release/bundle/dmg/tauri-app_1.0.1_x64.dmg with identity "Developer ID Application: xxx"
        Info using entitlements file at entitlements.mac.plist
    Bundling /Users/soon/projects/tauri-app/src-tauri/target/release/bundle/macos/tauri-app.app.tar.gz (/Users/soon/projects/tauri-app/src-tauri/target/release/bundle/macos/tauri-app.app.tar.gz)
    Finished 3 bundles at:
        /Users/soon/projects/tauri-app/src-tauri/target/release/bundle/macos/tauri-app.app
        /Users/soon/projects/tauri-app/src-tauri/target/release/bundle/dmg/tauri-app_1.0.1_x64.dmg
        /Users/soon/projects/tauri-app/src-tauri/target/release/bundle/macos/tauri-app.app.tar.gz (updater)

        Info 1 updater archive at:
        Info         /Users/soon/projects/tauri-app/src-tauri/target/release/bundle/macos/tauri-app.app.tar.gz.sig

Additional context

tauri.conf.json

"updater": {
  "active": true,
  "endpoints": [
      "https://gist.githubusercontent.com/JSoon/2831042583d566c7772bf2a534a41805/raw/f87327ac6ad30252ec09215567937576ff24faf5/tauri-update-file.json"
  ],
  "dialog": true,
  "pubkey": "dW50cnVzdGVkIGNvbW1lbnQ6IG1pbmlzaWduIHB1YmxpYyBrZXk6IDk3MkVBQkY1NDM3NjVEMUEKUldRYVhYWkQ5YXN1bDY1bnY4d1NPM2FLUkhxZ3V1OVFsRExuT2lsUzdVTkxBUGNnRVpRUmNMZTcK"
},

tauri-update-file.json

{
  "version": "v1.0.1",
  "notes": "Test version",
  "pub_date": "2022-07-01T11:25:57Z",
  "platforms": {
    "darwin-x86_64": {
      "signature": "dW50cnVzdGVkIGNvbW1lbnQ6IHNpZ25hdHVyZSBmcm9tIHRhdXJpIHNlY3JldCBrZXkKUlVRYVhYWkQ5YXN1bHhQRmlFbDgyWDVNZ1JRMmNLaGtoSmtLNmE4aHJYMjYyV3o4U3FlbE10TnlxZGI5ZElRZCs0alY5K2RVb1dDRzAzckxpQmwxMUdQNmpYbURBK2NBSlFZPQp0cnVzdGVkIGNvbW1lbnQ6IHRpbWVzdGFtcDoxNjU3MTAwMzU3CWZpbGU6dGF1cmktYXBwLmFwcC50YXIuZ3oKcVFBYkZGRnJFbnQ3MW5QV25adEtBUXJzMmRPRUlPVVNteUROYWFpUU9KSVl2VW9CS3crOUtJbTIwMnRPUkhXeTM1eW1maExZTTdhUWVtWFg5SGhHRFE9PQo=",
      "url": "https://github.com/JSoon/tauri-app-updates/releases/download/t1.0.1-001/tauri-app.app.tar.gz"
    }
  }
}

Updates assets

https://github.com/JSoon/tauri-app-updates/releases/tag/t1.0.1-001

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 21 (5 by maintainers)

Most upvoted comments

@JSoon I’m having the same problem. Did you solve this by moving from GitHub to your own server? 🤔

For me this error occurred because I have my source code and releases in a private repo and and i get a 404 error during an update so i decided to change the url in the latest.json by hosting the binary on a public github repo.

fwiw, I was running into this issue recently with macOS and discovered that the reason was:

  • I was running DMG and then trying to call updater for tar.gz and/or
  • I was running the macOS/app and then trying to call updater for tar.gz

What I had to do was:

  1. unzip the original tar.gz and run that app

then it worked and was able to get the next tar.gz version.

Thank you, @lucasfernog. I believe the docs has been written clear enough on Updater feature.

This issue has being ganked by creating all updates assets, including update JSON file and update packages, on my own HTTPS server.

Finally it works just fine on both Windows and macOS.