#NSIS Updater Passive Mode Requiring User Interaction

22 messages · Page 1 of 1 (latest)

abstract badge
#

Hello! Attempting to implement passive mode for the updater from what I've been able to gleam over from https://github.com/tauri-apps/tauri/pull/6998.

The updater is being triggered by system events and correctly sees and attempts to install the update. However, the updater is still requiring user interaction to install the update even though the installer mode is set to passive.

Still pretty new with Tauri so am I doing something incorrect here with the updater? Tried this with and without the manually setting the installer args to no avail. Here's the relevant sections from my tauri.conf.json file:

"bundle": {
  "windows": {
    "nsis": {
      "installMode": "currentUser"
    }
  }
},
"updater": {
  "active": true,
  "dialog": false,
  "endpoints": ["{{ENDPOINT_URL}}"],
  "pubkey": "{{PUB_KEY}}",
  "windows": {
    "installMode": "passive",
    "installerArgs": ["/P", "/R"]
  }
 }
GitHub
Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

hollow bluff
#

The pr you linked is not released yet, will be part of 1.4

abstract badge
#

Little eager to use this 😅

hollow bluff
#

for both the cli and the tauri crate?

abstract badge
#

Correct

hollow bluff
#

did you run cargo update afterwards? cargo is a bit of weirdo with pulling git deps

abstract badge
#

Yup

hollow bluff
#

Interesting, then there should be nothing stopping it from working i think 🤔

#

did you also try it without setting installerArgs manually? (since the updater does it itself)

#

nvm can't read

#

can you also share the output of the tauri info command so we got that off the list?

#

afterwards i'll rebuild my build with the latest dev branch to see if we broke something for everyone (i do have it working with a commit from right around that pr so it indeed worked back then at least)

abstract badge
# 
[✔] Environment
    - OS: Windows 10.0.22000 X64
    ✔ WebView2: 114.0.1823.43
    ✔ MSVC: 
        - Visual Studio Build Tools 2019
        - Visual Studio Community 2022
    ✔ rustc: 1.69.0 (84c898d65 2023-04-16)
    ✔ Cargo: 1.69.0 (6e9a83356 2023-04-12)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.9.0
    - yarn: 1.22.19
    - npm: 8.19.1

[-] Packages
    - tauri [RUST]: git+https://github.com/tauri-apps/tauri?branch=dev#d75c1b829bd96d9e3a672bcc79120597d5ada4a0 (1.3.0)
    - tauri-build [RUST]: git+https://github.com/tauri-apps/tauri?branch=dev#d75c1b829bd96d9e3a672bcc79120597d5ada4a0 (1.3.0)
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.3.0
    - @tauri-apps/cli [NPM]: 1.3.1

[-] App
#

FYI, also updated the tauri command under package.json to point to the CLI built from source: "tauri": "node ./tauri/tooling/cli/node/tauri.js", since that's not being reported in tauri info

abstract badge
#

Interestingly enough, silent mode isn't restarting the app

hollow bluff
#

okay so a debug build still works fine for me, compiling release builds right now

#

same for release builds

#

same for the quiet mode

#

so at least we know that it's not a general problem but i still don't have an idea why it doesn't work for you

abstract badge
#

Wild guesses but:

  1. I'm using system events instead of the built in dialog?
  2. My bundle targets are "targets": ["nsis", "updater"],, and my latest.json updater file is pointing to the .nsis.zip file. Similar for you or maybe something different there?
hollow bluff
#

same for me