[bug] .ico generated using tauri icon is incompatible when building on Windows.

[ferferga]

Describe the bug

I generate the icons of my app every time I build it using tauri icon, since I don't want to have lots of assets in my repo's commit history and tauri icon ensures that they're always strictly appropiate for my app.

Although in the command's output its stated that .ico files are generated, building on Windows always fail.

Reproduction

This reproduction was created using create-tauri-app, modifying just the bare minimum to demonstrate the issue (see the commit history for reference:

https://github.com/ferferga/tauri-reproduction-11220

The Windows build log is located in a GitHub Action's run: https://github.com/ferferga/tauri-reproduction-11220/actions/runs/11178007324

Expected behavior

The icons generated by tauri icon work out of the box

Full tauri info output

> tauri-app@0.1.0 tauri
> tauri info


[✔] Environment
    - OS: Debian 12.0.0 x86_64 (X64)
    ✔ webkit2gtk-4.1: 2.44.3
    ✔ rsvg2: 2.54.7
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 20.17.0
    - npm: 10.8.2

[-] Packages
    - tauri 🦀: 2.0.1
    - tauri-build 🦀: 2.0.1
    - wry 🦀: 0.44.1
    - tao 🦀: 0.30.3
    - @tauri-apps/api : 2.0.1
    - @tauri-apps/cli : 2.0.1

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.1
    - @tauri-apps/plugin-shell : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - bundler: Vite

Stack trace

Compiling open v5.3.0
    Finished `release` profile [optimized] target(s) in 10m 06s
    Built application at: D:\a\tauri-issue\tauri-issue\src-tauri\target\release\tauri-app.exe
thread '<unnamed>' panicked at crates\tauri-cli\src\interface\rust.rs:1227:8:
the bundle config must have a `.ico` icon
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Additional context

There are possibly 2 things failing here:

• The icons generated are not suitable
• The glob pattern doesn't work properly in Windows. However, I also tested icons/*.ico without success.

Builds were succeeding in my end before v2 with this setup.