Fabian-Lars
Fabian-Lars
> So it seems that Tauri is silencing stderr of the custom sign command? It may be hidden behind the --verbose flag (or -vv / -vvv, not sure if the...
`tauri build --verbose`, or in tauri-action `args: --verbose`. The signCommand will be executed the same way, we'd just check if the tauri cli is hiding some command output from us.
This has been added quite a while ago in #3194 with a relatively recent rework in #3444
To install the cli you currently need to use the --locked flag ``` cargo install tauri-cli --version "^2.0.0-rc" --locked ``` On first glance I don't see why this started to...
> I didn't need to use this the first time I installed the rc version, weird Yeah, the issue should be that there were some dependency updates after that that...
> [v2.tauri.app/start/create-project](https://v2.tauri.app/start/create-project/) yeah i pushed an update shortly after i wrote the above comment but the build pipeline failed :/ > Does the cargo command for create-tauri-app install the cli?...
did you run or build the app (just the frontend is enough) already? The .svelte-kit folder is auto generated. (btw this config should be the same as in svelte-kit's official...
Then that's something unrelated to this issue here.
did you add aditional rust dependencies? are you compiling for macos or ios? are dev and build affected?
No ETA. Some reproduction examples/steps, or at least some kind of descriptions on where/when this happens in your app would probably help. Afaik we haven't been able to reproduce this...