[updater] Updating macOS app from Tauri v1 to v2 fails to restart

Question

[updater] Updating macOS app from Tauri v1 to v2 fails to restart

Closed this issue a month ago · 13 comments

I have a Tauri app, and when I attempt to update a v1 app to a v2 version, the program gets stuck when I select "Yes" after being asked to restart.

The v1 version ends up being replaced in the /Applications folder, but it just doesn't restart to the v2 version.

Answer 1 · 2024-09-09T08:31:58.000Z

Can you check whether it's the same as #1724? So, do the file names differ?

edit: also linking tauri-apps/tauri#10355 just so we don't forget to close anything once resolved.

Answer 2 · 2024-09-09T08:34:24.000Z

The files names don't differ. They both end up being You Are Typing.app. I check the Applications folder and only one version exists. When I manually reset it, I check the About menu option and I see that the old version was properly replaced.

These seem to be two different problems.

Answer 3 · 2024-09-09T08:42:43.000Z

Okay, thanks. Since this is the v1 updater failing and not this plugin i'll mark this as an upstream issue. On that note, is the project in question public so we can check it out?

Answer 4 · 2024-09-09T08:42:50.000Z

/upstream tauri-apps/tauri

Answer 5 · 2024-09-09T08:46:56.000Z

Yeah, it's You Are Typing.

I should mention that 1.3.3 and 1.3.4 are the ones with Tauri v2. I eventually went back to v1.

Sorry for all the issues, but thank you for working on it!! 🫡

Answer 6 · 2024-09-09T08:49:17.000Z

so i assume updates from v1 to v1 work fine meaning it's not a permission issue (which would be a known issue on macos) 🤔

Answer 7 · 2024-09-09T08:50:26.000Z

Yup! v1->v1 work perfectly fine. :)

Edit: v1 -> v2 is where issues arise. ~~and v2 -> v2 doesn't display the update dialog, as mentioned in #1747.~~

Edit 2: Found out the Updater plugin requires us to manually check for updates. My bad!

Answer 8 · 2024-09-11T05:19:46.000Z

Is the issue solved on your end then @calejvaldez?

Answer 9 · 2024-09-11T10:05:10.000Z

@tweidinger Issue is resolved for #1747, not for this issue. The v2 -> v2 problem was unrelated to this one, I just thought I should mention it. :)

Answer 10 · 2024-09-13T01:47:49.000Z

hmm I've recently written a e2e test for the v1->v2 updater, it's working but i'll test with your repo to see what's missing.
EDIT: oh it's actually the restart step.. interesting, i'll get to it tomorrow

Answer 11 · 2024-09-13T02:01:45.000Z

@lucasfernog That might be a bit tricky because I reverted the project to v1 in 1.3.5.

The v2 projects are 1.3.3 and 1.3.4... though I don't know how we'd test the updater if the latest version is 1.3.6 which is built with v1. :c

Answer 12 · 2024-09-13T02:04:11.000Z

no worries we'll figure it out

Answer 13 · 2024-09-16T07:58:24.000Z

Closing as a fix was merged! :)