#Recent issue with updater

29 messages · Page 1 of 1 (latest)

trail marten
#

Hello, I've been struggling for hours, looking for an answer and found a few similar cases but still can't make it work.

timber python
#

Is your issue the config complaining? v1 is not impacted.

trail marten
#

I started by updating some dependencies

image.png
#

I have a GitHub workflow set so the project compiles to Windows, Mac and Linux. I've released two versions before but now gives me 'invalid padding' error when compiling

timber python
#

Can you also share the output of npm run tauri info?

trail marten
timber python
#

No problem. It's mainly to check the lock files are correctly updated.

#

The invalid padding problem happened for a lot of people on CLI v1.5.5 but it looks like you're skipping past that to the fixed version.

trail marten
#

This is from my local environment

    - OS: Fedora 38.0.0 X64
    ✔ webkit2gtk-4.0: 2.40.5
    ✔ rsvg2: 2.56.3
    ✔ rustc: 1.66.0 (69f9c33d7 2022-12-12)
    ✔ cargo: 1.66.0 (d65d197ad 2022-11-15)
    ✔ rustup: 1.25.1 (bb60b1e89 2022-07-12)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 14.21.2
    - npm: 9.8.1

[-] Packages
    - tauri [RUST]: 1.2.2
    - tauri-build [RUST]: 1.2.1
    - wry [RUST]: 0.23.4
    - tao [RUST]: 0.15.7
    - @tauri-apps/api [NPM]: 1.5.1
    - @tauri-apps/cli [NPM]: 1.5.6```
timber python
#

Hm... you might have to update the Rust packages as well.

trail marten
#

and node hehe, I actually use nvm for node versions... sorry about that

#

but you think this is related? I mean, the issue is happening compiling with GitHub workflow

timber python
#

Does your Cargo.lock file on GitHub have the same versions?

#

Searching for "tauri" and "tauri-build" will find the version numbers in that file.

trail marten
#

tauri-build: 1.2.1

#

in Cargo.toml

timber python
#

You should be able to run cargo update to get them to the latest.

#

You might also want to update your Rust version (rustup update) but I don't think that's the problem here.

trail marten
#

ok doing it now

#

updated

#

I'll push and trigger the action

#

sadly it didn't work

image.png
#

I'm noticing the command only updated Cargo.lock, Cargo.toml is intact

#

should I manually update something there?

timber python
#

You can if you'd like but so long as Cargo.toml doesn't have an = then it will try to update to the latest version with the same major number.

trail marten
#

Cargo.toml

name = "app"
version = "0.1.0"
description = "A Tauri App"
authors = ["you"]
license = ""
repository = ""
default-run = "app"
edition = "2021"
rust-version = "1.59"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[build-dependencies]
tauri-build = { version = "1.2.1", features = [] }

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tauri = { version = "1.2.2", features = ["dialog-all", "fs-all", "shell-open", "updater"] }

[features]
# by default Tauri runs in production mode
# when `tauri dev` runs it is executed with `cargo run --no-default-features` if `devPath` is an URL
default = [ "custom-protocol" ]
# this feature is used for production builds where `devPath` points to the filesystem
# DO NOT remove this
custom-protocol = [ "tauri/custom-protocol" ]```
timber python
#

Yeah, no =1.2.2 there so you're fine.

trail marten
#

I tried from my laptop (more updated) and the updater signature was successful
definitely there's something wrong with some package versions... I'll keep looking and leave my findings here