Describe the bug
When upgrading from a previous installation, the resources specified in tauri.conf.json are skipped. Uninstalling and re-installing the program fixes it.
I saw this bug on the latest beta/production release of my application. There was a smaller update this Monday (5/16) that worked correctly. Maybe this is a regression in recent changes to the installer?
I can post the diff of tauri.conf.json for the previous and current version if it is helpful.
Reproduction
-
Download and install v0.9.2 of the application: https://hypetrigger-downloads.s3.amazonaws.com/Hypetrigger_0.9.2_x64_en-US.msi.zip
-
Check C:\Program Files\hypetrigger to see that all resources have been bundled (tensorflow.dll, tensorflow.lib, ffmpeg.exe, and data folder)

-
Either accept the auto-update request to v0.10.0, or download the v0.10.0 installer (both approaches cause the bug): https://hypetrigger-downloads.s3.amazonaws.com/Hypetrigger_0.10.0_x64_en-US.msi.zip
-
After installation, attempt to launch Hypetrigger.exe
-
Error: tensorflow.dll is not installed

- Check
C:\Program Files\hypetrigger. Notice that all the assets are missing from this version of the installation, even though all the same resources are present in tauri.conf.json

- Run the 0.10.0 installer again to uninstall the program, and then reinstall from scratch
- Launch
Hypetrigger.exe. This time, the app loads correctly and all the resources are correctly located in the installation folder.
Expected behavior
The installer should always bundle the correct resources when installing.
Platform and versions
$ npm run tauri info
> hypetrigger@0.9.2 tauri
Environment
› OS: Windows 10.0.19044 X64
› Webview2: 101.0.1210.47
› MSVC:
- Visual Studio Community 2019
- Visual Studio Build Tools 2017
› Node.js: 14.18.0
› npm: 8.7.0
› pnpm: Not installed!
› yarn: Not installed!
› rustup: 1.24.3
› rustc: 1.60.0
› cargo: 1.60.0
› Rust toolchain: stable-x86_64-pc-windows-msvc
Packages
› @tauri-apps/cli [NPM]: 1.0.0-rc.11
› @tauri-apps/api [NPM]: 1.0.0-rc.5
› tauri [RUST]: 1.0.0-rc.6,
› tauri-build [RUST]: 1.0.0-rc.5,
› tao [RUST]: 0.7.0,
› wry [RUST]: 0.14.0,
App
› build-type: bundle
› CSP: default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self'; worker-src 'self' blob: https://tauri.localhost/; script-src 'self' 'unsafe-eval' https://unpkg.com
› distDir: ../dist
› devPath: http://localhost:3000/
App directory structure
├─ .git
├─ dist
├─ node_modules
├─ scripts
├─ src
└─ src-tauri
Stack trace
No response
Additional context
Did not happen on any previous version of the installer, as recently as 5/20/22
Describe the bug
When upgrading from a previous installation, the
resourcesspecified intauri.conf.jsonare skipped. Uninstalling and re-installing the program fixes it.I saw this bug on the latest beta/production release of my application. There was a smaller update this Monday (5/16) that worked correctly. Maybe this is a regression in recent changes to the installer?
I can post the diff of
tauri.conf.jsonfor the previous and current version if it is helpful.Reproduction
Download and install v0.9.2 of the application: https://hypetrigger-downloads.s3.amazonaws.com/Hypetrigger_0.9.2_x64_en-US.msi.zip
Check

C:\Program Files\hypetriggerto see that all resources have been bundled (tensorflow.dll,tensorflow.lib,ffmpeg.exe, anddatafolder)Either accept the auto-update request to v0.10.0, or download the v0.10.0 installer (both approaches cause the bug): https://hypetrigger-downloads.s3.amazonaws.com/Hypetrigger_0.10.0_x64_en-US.msi.zip
After installation, attempt to launch
Hypetrigger.exeError:
tensorflow.dll is not installedC:\Program Files\hypetrigger. Notice that all the assets are missing from this version of the installation, even though all the same resources are present intauri.conf.jsonHypetrigger.exe. This time, the app loads correctly and all the resources are correctly located in the installation folder.Expected behavior
The installer should always bundle the correct resources when installing.
Platform and versions
Stack trace
No response
Additional context
Did not happen on any previous version of the installer, as recently as 5/20/22