Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Couldn't recognize the current folder as a Tauri project #3527

Closed
The-Mr-L opened this issue Feb 21, 2022 · 11 comments
Closed

[bug] Couldn't recognize the current folder as a Tauri project #3527

The-Mr-L opened this issue Feb 21, 2022 · 11 comments
Assignees
Labels
scope: cli.rs The tauri-cli rust crate type: bug

Comments

@The-Mr-L
Copy link

The-Mr-L commented Feb 21, 2022

Describe the bug

hi, I am trying to upgrade from beta to the latest version, I am using the tauri vite plugin and the author of the project believes the problem is related to the cli. can you please take a look at the issue here:
amrbashir/vite-plugin-tauri#2 (comment)
thank you!

thread '' panicked at 'Couldn't recognize the current folder as a Tauri project. It must contain a tauri.conf.json or tauri.conf.json5 file in any subfolder.', src\helpers\app_paths.rs:64:4
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Reproduction

No response

Expected behavior

builds

Platform and versions

Windows 10
@tauri-apps/cli v1.0.0-rc.5

Stack trace

No response

Additional context

project structure:

dist
node_modules
public
srs
src-tauri
@The-Mr-L
Copy link
Author

I dont know why the link dossnt work tho

@amrbashir amrbashir changed the title [bug] Cant run cli [bug] Couldn't recognize the current folder as a Tauri project Feb 21, 2022
@amrbashir amrbashir added the scope: cli.rs The tauri-cli rust crate label Feb 21, 2022
@The-Mr-L
Copy link
Author

thank you for edit! @amrbashir

@lucasfernog lucasfernog self-assigned this Feb 21, 2022
@lucasfernog
Copy link
Member

Can you provide the steps you used to create your project or a test project on GitHub? I couldn't reproduce this with the vanilla Vite template. Also make sure you don't have the src-tauri folder on your .gitignore file.

@The-Mr-L
Copy link
Author

The-Mr-L commented Feb 21, 2022

well the only thing I did was running pnpm upgrade and cargo upgrade and update using cargo edit. before this it worked fine with the beta version. and the folder structure is standard I have not made any changes . I will look more into it as soon I have some more time. thank you for your time.

@The-Mr-L
Copy link
Author

wow okay when I first read your comment I forgot that I am ignoring the src-tauri folder in git. but what has change? that makes this not work anymore?? :) I had no idea this would have that effect. but it works now! thanks again for your time. btw what is the status of android development it sounds interesting? just in a few words :)

@lucasfernog
Copy link
Member

Yeah you shouldn't gitignore the src-tauri folder.

For the android development, check out the tao-wry channel on our Discord.

@slch
Copy link

slch commented May 26, 2022

Was wondering why getting the same error on fresh project.
Same with different templates.

The issue was having a git repo in ~ - for dot files.
Creating a local git repo for project solved the problem 👌

@dyzdyz010
Copy link

Still not working, have created local git repo, no git repo in ~, still the same error in a fresh-created project.

@rmburg
Copy link

rmburg commented Nov 20, 2024

This is still broken. Can we reopen this?

@rmburg
Copy link

rmburg commented Nov 20, 2024

In my case, I had a .gitignore file in ~ which ignored the entire project. This causes the CLI to fail, even if src-tauri/tauri.conf.json exists in my cwd. This worked with tauri v1, and broke with v2 for me

@sirenoremac
Copy link

Reproducible on MacOS:
Create a .gitignore in ~ and put an asterisk in it
Create a new Tauri project anywhere at all within ~
Try to run Tauri, and it will fail with this error
I don't know much about this, but it seems clear that Tauri is affected by .gitignore files anywhere in the folder hierarchy that it is run from. Seems like it would be more sensible to only look at .gitignore's at perhaps the parent folder that it is run from? Not sure, as I don't really know what all it is doing with the .gitignore, but fundamentally it seems strange that a file WAY outside of the project's structure is affecting it.
For some background, I believe I had a .gitignore created in ~ by venv, which seems like a fairly common thing for developers to be using...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: cli.rs The tauri-cli rust crate type: bug
Projects
None yet
Development

No branches or pull requests

7 participants