Error failed to get project out directory: failed to get cargo metadata: cargo metadata command exited with a non zero exit code: error: failed to parse manifest at `/home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml`
Caused by:
can't find library `app`, rename file to `src/lib.rs` or specify lib.path
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
#mobile build not works
301 messages · Page 1 of 1 (latest)
This error typically means that you're missing this part: https://next--tauri.netlify.app/next/mobile/development/integrate#create-the-library-source-code
I have that file!
Oh wait, git didn't add the files
Let me verify if this works now!
Doesn't work:
error: failed to run custom build command for `gdk-sys v0.15.1`
Caused by:
process didn't exit successfully: `/home/runner/work/Plan2Go/Plan2Go/src-tauri/target/release/build/gdk-sys-8fa82a75c6d5ad1c/build-script-build` (exit status: 1)
yarn build for whatever reason runs tauri build which compiles the app for the current host, meaning linux for which you're missing the system deps (gtk, webkitgtk etc)
Oh wait it install dependcies not because if: matrix.platform == 'ubuntu-22.04' and it not runs in matrix
Btw is there maybe a 'correct' workflow for mobile builds?
error[E0599]: no method named `into_i32` found for enum `timeout::Timeout` in the current scope
--> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/xdg/zbus_rs.rs:72:38
|
72 | notification.timeout.into_i32(),
| ^^^^^^^^ method not found in `timeout::Timeout`
|
::: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/timeout.rs:3:1
|
3 | pub enum Timeout {
| ---------------- method `into_i32` not found for this enum
For more information about this error, try `rustc --explain E0599`.
error: could not compile `notify-rust` due to previous error
warning: build failed, waiting for other jobs to finish...
Error failed to build app: failed to build app
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
afaik notify-rust does not work on android (and ios?) so i think you won't get around removing that dep on mobile targets
But how?
for example by specifying the dep like this ```rs
[target.'cfg(any(target_os = "windows", target_os = "linux", target_os = "macos"))'.dependencies]
notify-rust = {}
and then use the same config in your code on the dep imports/usages ```rs
#[cfg(any(...))]
{
// desktop only
}
But I kind of really need notifications... So yeah I think I might just fallback to the PWA for mobile app
either PWA or other crates. notifications on mobile work quite differently. you could also modify the android studio and xcode projects to do it directly in kotlin and swift(?) if there's no other crate out there
Error failed to get project out directory: failed to get cargo metadata: cargo metadata command exited with a non zero exit code: error: failed to parse manifest at `/home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml`
Caused by:
failed to parse `cfg{any(target_os = "windows", target_os = "linux", target_os = "macos")}` as a cfg expression: invalid target specifier: unexpected `(` character, cfg expressions must start with `cfg(`
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
whoops lemme edit the example
[] instead of {}
or ()
one of them was it x)
okay yeah, it was () if i can trust my own file
Uhmm it still says:
error[E0599]: no method named `into_i32` found for enum `timeout::Timeout` in the current scope
--> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/xdg/zbus_rs.rs:72:38
|
72 | notification.timeout.into_i32(),
| ^^^^^^^^ method not found in `timeout::Timeout`
|
::: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/timeout.rs:3:1
|
3 | pub enum Timeout {
| ---------------- method `into_i32` not found for this enum
For more information about this error, try `rustc --explain E0599`.
error: could not compile `notify-rust` due to previous error
warning: build failed, waiting for other jobs to finish...
Error failed to build app: failed to build app
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
``` ...
Maybe you have got an github workflow file for me?
nope, i don't build for mobile and i don't know of any repo/workflow doing it either
actually another cause could be the missing android target for the toolchain
because in theory the android init command runs this rustup command: https://next--tauri.netlify.app/next/guides/getting-started/prerequisites/linux#android
but since you're still running yarn build in that step the target/toolchain won't be installed yet
Hmm... When to run the rustup command? Can it be done apart from the github action?
it must be inside the action because it must be installed on the runner
but like i said, ideally this line does that automatically for you: https://github.com/TheDutchProgrammers/Plan2Go/blob/test/.github/workflows/build_mobile.yml#L61
but yarn build prevents the runner from ever reaching that line
to be clear: remove yarn build from the Install app dependencies step. you're only wasting build time there.
or alternatively, remove tauri build from your package.json build script, the intention of this step is only to build your frontend not the whole tauri app (which is also unnecessary if you configured beforeBuildCommand to build your frontend), buuuut i'm just repeating myself here lol
UHmmmm
Uhmm please edit the file so it works
if the latest run (now running) not works
and send file here
Just keep the yarn install?
error: failed to run custom build command for `wry v0.22.0`
Caused by:
process didn't exit successfully: `/home/runner/work/Plan2Go/Plan2Go/src-tauri/target/debug/build/wry-8477385d03914511/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-env-changed=WRY_ANDROID_REVERSED_DOMAIN
cargo:rerun-if-env-changed=WRY_ANDROID_APP_NAME_SNAKE_CASE
cargo:rerun-if-env-changed=WRY_ANDROID_KOTLIN_FILES_OUT_DIR
--- stderr
thread 'main' panicked at '`WRY_ANDROID_REVERSED_DOMAIN` is not set, which is needed to generate the kotlin files for android.', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wry-0.22.0/build.rs:19:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
Error `Failed to run `cargo build`: Command "cargo build --package app --manifest-path /home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml --target aarch64-linux-android --color always" didn't complete successfully, exiting with code 101.
Error: Process completed with exit code 1.
wait, are you not using tauri's next branch? the wry version the error reports (0.22) is what tauri 1.2 used
You have seen the github workflow. It does clone and build the next branch, but yeah... I got the workflow file from someone else's repo, but that one never actually worked... But I was thinking that it might had been because their code was not working (not the workflow file)
Yeah I've seen the workflow, but the issue is that the project itself uses Tauri 1.2
As in, the Cargo.toml file lists 1.2 instead of the 2.0 alpha
Oke...
what is the correct version name/string
Oh wait, it was generated in the first place
2.0.0-alpha.1 for tauri-build
2.0.0-alpha.3 for tauri
Check
let me test the desktop building first
Mobile build:
error[E0432]: unresolved imports `tauri::SystemTray`, `tauri::SystemTrayMenu`, `tauri::SystemTrayMenuItem`, `tauri::SystemTrayEvent`, `tauri::api::dialog`
--> src/main.rs:6:13
|
6 | use tauri::{SystemTray, SystemTrayMenu, SystemTrayMenuItem, SystemTrayEvent, CustomMenuItem, Manager, api::dialog::ask, RunEvent, WindowE...
| ^^^^^^^^^^ ^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^ ^^^^^^ could not find `dialog` in `api`
| | | | |
| | | | no `SystemTrayEvent` in the root
| | | no `SystemTrayMenuItem` in the root
| | no `SystemTrayMenu` in the root
| no `SystemTray` in the root
error[E0599]: no method named `system_tray` found for struct `tauri::Builder` in the current scope
--> src/main.rs:16:6
|
16 | .system_tray(SystemTray::new().with_menu(tray_menu))
| ^^^^^^^^^^^ method not found in `tauri::Builder<tauri_runtime_wry::Wry<EventLoopMessage>>`
warning: unused import: `Manager`
--> src/main.rs:6:94
|
6 | use tauri::{SystemTray, SystemTrayMenu, SystemTrayMenuItem, SystemTrayEvent, CustomMenuItem, Manager, api::dialog::ask, RunEvent, WindowE...
| ^^^^^^^
|
= note: `#[warn(unused_imports)]` on by default
Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
AL right
so it doesn't allow systemtray
which is logic
but shouldn't it skip it because:
#![cfg_attr(
all(not(debug_assertions), target_os = "windows"),
windows_subsystem = "windows"
)]
```?
Do you have any recommendations on how to cache the tauri next branch thingy?
Cause I don't want to have to wait like 5 minutes for that thing to be build so I can then see that MY CODE still not works
Do you have any recommendations on how to cache the tauri next branch thingy?
you could use a prebuilt binary from tauri's gh release, it was recently released so there shouldn't be too many changes you'd be missing
or try switching these 2 steps idk
I will do this for now and will try using prebuilt after that
no, that does not influence the code at at all. this is an attribute specific to windows
Oh that makes sense
I always was thinking like that that action thing cached it when it was runned.. but it just initializes it and then it just appends the save action at the end... I now see and understand it
Btw this is now just for Android, not yet IOS
Oh shit it failed
I forgot to remove the checker thingy
#[cfg(desktop)]
fn main() {
maybe just try 2 main functions, one for desktop one for mobile, and guard them with #[cfg(desktop)] (and not(dekstop) )
cfg!(desktop) resolves to a boolean
while #[cfg()] will completely remove the irrelevant code
yes
Oh
Maybe it will work the way I have it now, else I will change it up again
Oke will just use that other way
Btw why does this error happen at IOS:
tauri ios init
error: The subcommand 'ios' wasn't recognized
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Usage: yarn run tauri [OPTIONS] <COMMAND>
For more information try '--help'
error Command failed with exit code 2.
Error: Process completed with exit code 2.
wrong cli version
But where is the version selected and what version should it be?
you're not using the cli download from git in the ios job so it uses whatever is listed in package.json
But this downloads cli from git, right?
git clone -b next https://github.com/tauri-apps/tauri
cd tauri/tooling/cli/node
yarn
yarn build
correct, you download and build it, but you don't actually use it
just compare your android and ios jobs i guess
It installs the tool, right?
Android is now successful! Lets goo!
nice
Oke, but how to use it? IOS just builds the node version of the cli and not the - i dont even know what - version of the cli
well, the first question would be, why? :D
can't it just do the same as the android version?
IDK, I didn't write it!
I think it uses that because it works better and because it is the yarn tauri / tauri command
So my next question would be, what do we get out of yarn build of the next branch cli thingy? Where is the tauri command file thingy located after building it?
Or Maybe better: How to replace the yarn tauri with the newly builded tauri command?
because it works better
i doubt that, it's the same cli, just wrapped with napi-rs so that it's shippable as a npm package.
where is it
tooling/cli/node/tauri.jsi think
honestly i'd just use the same thing you used in the android version, it should even be slightly faster to build
Hmm...
at android: ```yml
- name: Build apk
run: tauri/tooling/cli/target/debug/cargo-tauri android build --split-per-abi --debug
Thats where the cargo builded thingy is at least...
and yarn build runs: cross-env TARGET=node napi build --platform as seen in the package.json of the cli/node
Btw also one quick question: Does IOS also not need to run the yarn build inside my app folder or does ios need the yarn build (and then of course combined with yarn tauri ios build)
I guess I will switch to the cargo version
After 10 minutes of waiting:
Run tauri/tooling/cli/target/debug/cargo-tauri ios init
Error No code signing certificates found. You must add one and set the certificate development team ID on the `tauri > bundle > iOS > developmentTeam` config value or the `TAURI_APPLE_DEVELOPMENT_TEAM` environment variable. To list the available certificates, run `tauri info`.
Error: Process completed with exit code 1.
afaik there is no alternative than to actually pay apple
The following warnings were emitted during compilation:
warning: `"pkg-config" "--libs" "--cflags" "javascriptcoregtk-4.1" "javascriptcoregtk-4.1 >= 2.24"` did not exit successfully: exit status: 1
error: failed to run custom build command for `javascriptcore-rs-sys v0.5.1`
Caused by:
process didn't exit successfully: `/home/runner/work/Plan2Go/Plan2Go/src-tauri/target/release/build/javascriptcore-rs-sys-d80cdd012bd7e89b/build-script-build` (exit status: 1)
with just normal ubuntu run
tauri alpha.3 changed the webkit version. change this line https://github.com/TheDutchProgrammers/Plan2Go/blob/test/.github/workflows/build-and-release.yml#L35 to ```yml
sudo apt-get install -y libgtk-3-dev libwebkit2gtk-4.1-dev libappindicator3-dev librsvg2-dev patchelf
And now ubuntu has the ```
error[E0599]: no method named into_i32 found for enum timeout::Timeout in the current scope
--> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/xdg/zbus_rs.rs:72:38
|
72 | notification.timeout.into_i32(),
| ^^^^^^^^ method not found in timeout::Timeout
|
::: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/timeout.rs:3:1
|
3 | pub enum Timeout {
| ---------------- method into_i32 not found for this enum
For more information about this error, try rustc --explain E0599.
error: could not compile notify-rust due to previous error
warning: build failed, waiting for other jobs to finish...
Error failed to build app: failed to build app
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
problem
no idea why tbh. but you can delete this step https://github.com/TheDutchProgrammers/Plan2Go/blob/test/.github/workflows/build-and-release.yml#L95-L97
a) it's not building the web but the tauri app because your package.json script still does tauri build, and your frontend doesn't need to be built since it's all static
still weird tho
cause even if you remove that step, it will fail in the last step with the same error
Do I then just run npm install @tauri-apps/cli@next @tauri-apps/api@next? (and the other commands from https://next--tauri.netlify.app/blog/2022/12/09/tauri-mobile-alpha)
I guess I will just do that
Uhmm
FAILURE: Build failed with an exception.
* What went wrong:
Could not determine the dependencies of task ':app:compileArm64DebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:arm64DebugCompileClasspath'.
> Could not resolve project :tauri-android.
Required by:
project :app
> No matching configuration of project :tauri-android was found. The consumer was configured to find an API of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'com.android.build.api.attributes.ProductFlavor:abi' with value 'arm64', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.3.1', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- None of the consumable configurations have attributes.
no idea tbh. can't remember seeing that before
What I did was update the version of tauri to the newest 2.0-alpha, but I did not disable the next branch building task afaik
Any updates or ideas?
I think I will be trying the build at least now again, to see if the updated Next branch might already have fixed it. (btw it is using the next branch binary, but still for android builds the branch)
Any ideas for this now?
nope
tauri/tooling/cli/target/debug/cargo-tauri android build --split-per-abi --debug
did alpha.3 uses javascriptcore-4.1?
Is there any workaround because webkit2gtk is still in javascriptcore-4.0
yes, alpha.3 switched the jsc version, but it also switched webkit2gtk versions to libwebkit2gtk-4.1
alright thanks, didn't realize there was webkit2gtk-4.11 in Arch repo
Hmm...
don't worry about it, we already changed that in your workflow :D
Had to comment some lines, it runs. Thanks
the strange thing is that tauri android init does work, but tauri android build not
well, i wouldn't call it strange. init only inits your project, like adding the android studio project. build actually tries to build the project so that's where all the juicy stuff actually happens
But the build says:
No matching configuration of project :tauri-android was found. The consumer was configured to find a runtime of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'com.android.build.api.attributes.ProductFlavor:abi' with value 'arm64', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.3.1', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
Maybe I should actually remove the building of the tauri next branch and completly use the the release thingy
did you ever try it locally before?
Nope, I don't have a linux enviroment
you don't need to. you can build android on windows and macos too
And my laptop is not really going to be able to run it
that's fair
It cannot even run MInecrfat Bedrock good enough
and like too less space
But it did work once... and then I updated the tauri version with npm and it now no longer works
now that's interesting
Yeah true.. But maybe I should just remove the tauri next branch building step... (or bettter just remove the usage, for now)
would definitely speed up the workflow a bit at least
let me just try with using tauri commnd first
fwiw it builds fine in my fork of your repo, but it always gets stuck at the end of the build step for some reason
it's yarn tauri android x (or npm run tauri android x)
debug turns rust's debug mode on (faster but bigger binaries)
split-per-abi is something android specific that i don't know either
oke
not sure if tauri even understands and forwards it like this 🤔
Maybe since you are in Working-Group, you can ask on #archive-mobile
you can ask too :D
ohoh somebody didn't read #rules 👀
(just kidding btw, but it's indeed mentioned there)
it should be, but hard to check since the message was deleted a few times 🤔
doesn't matter
Hmmm is it correct that it takes more than 1 hour?
nope
But it is sort of doing things
that's the timeout i was talking about
it is showing the Compiling xxx thingys
Did you talk about timeout?
^
different wording, used stuck instead of timeout
for me it always gets stuck here
Oh... I didn't made that out of it
for 90 minutes now
while the build in tauri's main repo takes 20 minutes
and does not get stuck there
Hmmmmm
the --split-per-abi --debug stuff also didn't make a difference
hmm, why is this sooo difficult...
easy:
- tauri v2 is in early alpha, explicitly to figure out issues like this
- github actions are a pain to work with x)
well, we need to know what it's doing so that we can fix whatever is happening
Uhmm, oh right...
But still, WHY did it work before I upgraded it so we could disabled the tauri next branch?
same answer basically. that is what we're trying to figure out right now
Oke sure
I will firstly disabled the build of the unused branch building thingy
And what do I need to add to enable verbose?
add --verbose behind the --debug flag
Oke
Oke it will now start building
Btw can you also look at how we could combine the action (of the apk build) into the Build App Action?
(as in what with: fields have to be chnaged so it will add the android build argument thingy)
Oke
Uhmm after
Debug [tauri_mobile::bossy] setting stderr to Stdio { .. } on command "cargo build --package app --manifest-path /home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml --target aarch64-linux-android --features custom-protocol --color always"
it doesn't show actual verbose info anymore (cause the compiling of cargo)
So I dont know if it is going to be usefull, but we will see
Oh wait it does the cargo per target
I see a lot of file or directory '/home/runner/work/Plan2Go/Plan2Go/src-tauri/gen/android/app/app/src/*/*', not found (where * is replaced by text)
Uhmmm....
Since the builded cargo one didn't work, it now runs: yarn tauri android build --split-per-abi --debug --verbose
we tried both actually
ok 😦
AAPT2 aapt2-7.3.1-8691043-linux Daemon #0: shutdown
BUILD SUCCESSFUL in 10m 9s
147 actionable tasks: 147 executed
Watching 1051 directories to track changes
Watching 1050 directories to track changes
Watching 1049 directories to track changes
Watching 1048 directories to track changes
cargo install tauri-cli just succeeded https://github.com/FabianLars/Plan2Go/actions/runs/4233076972/jobs/7353575762
this is where it is now stuck at
I know the currently published node CLI is a little weird at least
but maybe it will be continuing
Hmmmmm
So what do you recommend?
But I will wait untill it hits 30 minutes (max)
It is still 'building'
and still nothing after
...
Watching 1051 directories to track changes
Watching 1050 directories to track changes
Watching 1049 directories to track changes
Watching 1048 directories to track changes
So yeah, why does your work, and mine not
wdym, mine is stuck in the same place
but i had 2 runs side by side
one with npm run tauri android build and one with cargo tauri android build
Oh wait you used cargo tauri
so it comes down to lucas' I know the currently published node CLI is a little weird at least 
But is there rn any way for it to work?
did it work with Cargo?
for me yes
ok, I just need swift-rs to be released to publish tauri
But is cargo tauri android build different from npm run tauri android build?
yeah, the npm one uses Node-API and it's a little weird with stdout/stderr so spawning some commands freeze the app (don't ask me why)
Hmm I am now using cargo install tauri-cli --version "^2.0.0-alpha" && cargo tauri android build and it still is stuck after 1:40 hours
No history is available.
Transforming savedstate-1.2.0.aar (androidx.savedstate:savedstate:1.2.0) with DexingNoClasspathTransform
Caching disabled for DexingNoClasspathTransform: /home/runner/.gradle/caches/transforms-3/46aa139b01fdf81b2b9389a46adcf412/transformed/savedstate-1.2.0-runtime.jar because:
Build cache is disabled
DexingNoClasspathTransform: /home/runner/.gradle/caches/transforms-3/46aa139b01fdf81b2b9389a46adcf412/transformed/savedstate-1.2.0-runtime.jar is not up-to-date because:
No history is available.
The input changes require a full rebuild for incremental DexingNoClasspathTransform: /home/runner/.gradle/caches/transforms-3/46aa139b01fdf81b2b9389a46adcf412/transformed/savedstate-1.2.0-runtime.jar.
that's the exact same thing i did
Yes, thats why I tried
Oh wiat
it is my client/browser
it didnt update
the .zip is 439 MB
Btw there are some anotations:
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions-rs/toolchain@v1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Possibly yes
you can update actions/checkout to v3 and replace actions-rs/toolchain@v1 with dtolnay/rust-toolchain@stable https://github.com/FabianLars/Plan2Go/blob/test/.github/workflows/build-and-release.yml#L45-L46. the warnings should be gone then.
Sure
Oke, btw where are my linux, windows, mac installables?
I dont see them
v0.1.0 is old, it is November 14
check the upload dates
Oh, it updates the assets
Btw I just see whilst I was copying my folder on my laptop, that the target folder is 9,76 GB
Shall I btw remove --debug from the android build command?
you probably don't wanna share debug builds with users, so yes
that's a bit large. it should be something around 2GB for each target (2gb for debug, 2gb for release, 2gb for other platforms/arch etc)
Oke
release = 2,23 GB
debug = 7,52 GB
debug folder:
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 7-2-2023 11:41 482042778 Plan2Go.lib
-a---- 10-2-2023 09:16 481982666 app.lib
-a---- 10-2-2023 16:32 123179008 app.pdb
-a---- 7-2-2023 11:41 482042778 deps\Plan2Go.lib
-a---- 10-2-2023 09:16 481982666 deps\app.lib
-a---- 5-12-2022 09:51 203813176 deps\libwindows-c3a28a5e1e0dc926.rlib
-a---- 10-11-2022 19:18 188125966 deps\libwindows-539a3251dc00f06a.rlib
-a---- 10-2-2023 16:32 123179008 deps\app.pdb
Maybe I should just run a 'clean' command, like at maven exists
yeah, if your debug folder is older, and may have lived through some rust version updates it will grow over time
rust does not clean after itself
yeah, there's cargo clean
where do I run it inside
but your app will be built from scratch on the next run as it removes everything
src-tauri/
just delete it
delete the target folder?
and I guess just the debug folder inside
I will move it to trashbin
then now I will run the dev command
don't worry about it. rust can regenerate all the files inside target/ just fine - it just takes a bit longer to compile your app the first time afterwards