#Tauri V1 cannot update to Tauri V2 app

9 messages · Page 1 of 1 (latest)

north forge
#

Hello,

I am upgrading our app in production from a version with Tauri V1 to a version with Tauri V2. For V1, I am using the native updater plugin.

However, for some reason, users on the Tauri V1 version get the prompt to update, but when they click update, they go through the process, only to be left in the same (old) version of the app. This only happens on Windows. On Mac, the app successfully updates, but segfaults on first restart.

Does anyone have any idea how to fix this? This is fairly urgent for us as it's preventing us from shipping out an update to users of our desktop app. We are using the option to create v1-compatible artifacts.

north forge
#

Resolved by using the NSIS installer instead

spiral flicker
#

How did you fix the segfault on Mac?

#

And was the move from msi to nsis seamless for the end user? I’ve been thinking of switching too

north forge
#

But it happens only once so it was fine

#

The NSIS switch isn't seamless :/ the install directory is different, and it doesn't uninstall the old program

remote dock
spiral flicker
#

@remote dock does that mean if the product name and cargo name are the same, there should be no issue on v1 to v2?