Repository navigation
Description
Steps to Reproduce
- Run flutter config --build-dir= in VSCode terminal
- Restart VSCode
- Run flutter create .
- The new build-dir is created and populated, but the original default build folder is also created and populated with stuff.
- This creates a conflict as there is already file named BUILD in the flutter project's root, where it creates the build folder.
Logs
Logs
There are no logs for this, the problem is obvious, and is solved if I remove the BUILD file, by I can't do that as this file is required by the CI/CD system.
PS C:\Users\jfcarroll\source\repos\google73\google3\location\nearby\apps\helloconnections> flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19042.1645], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.1.6)
[√] Android Studio (version 4.1)
[√] VS Code (version 1.66.2)
[√] Connected device (3 available)
[√] HTTP Host Availability
• No issues found!
Activity
danagbemava-nc commentedon Sep 23, 2022
Reproducible using the steps provided above.
NB: You may need to run
flutter buildso the build folders are generated.In the screenshot below, you can see there's a next folder that contains some windows files as well as a build folder that also contains some windows file.
The next folder was set as the build-dir
screenshot
flutter doctor -v
build_windows.log
Moini commentedon Nov 18, 2024
New to Flutter and Dart, and really wondering.
Does this mean that everyone who uses Flutter with VSCode(ium) cannot put the build results into a separate folder but must keep them cluttering the main project folder? Or is there a way to fix/workaround this?
[flutter_tools] Honor configured build-dir across flutter project and…
github-actions commentedon Sep 11, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.