Repository navigation
Target debug_android_application failed: FileSystemException: Cannot copy file to <elided>, path = <elided> (OS Error: Cannot create a file when that file already exists. #74227
Description
I have an issue with flutter giving out semi-random errors on a larger project when I am performing flutter run. When I run the flutter clean the error went away for the first build, but any consecutive after that gave out an error on part of the gradle process. It happens like this like clock-work, every single time.
So I did some digging into the error, and what I found is that it's related to the flutter.bat with the ampersand exit. I don't know why, or how (judging from the big wall of text, people put some thought into the chaining) but truth be told when I move the exit /b part onto a separate line the error stopped occurring and I was able to perform flutter run consecutively without any errors!
This was the error description I was given:
FAILURE: Build failed with an exception.
* Where:
Script 'D:\SDK\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 904
* What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
> Process 'command 'D:\SDK\flutter\bin\flutter.bat'' finished with non-zero exit value 1
Contents of the flutter.bat
REM To debug the tool, you can uncomment the following lines to enable checked mode and set an observatory port:
REM SET FLUTTER_TOOL_ARGS="--enable-asserts %FLUTTER_TOOL_ARGS%"
REM Chaining the call to 'dart' and 'exit' with an ampersand ensures that
REM Windows reads both commands into memory once before executing them. This
REM avoids nasty errors that may otherwise occur when the dart command (e.g. as
REM part of 'flutter upgrade') modifies this batch script while it is executing.
REM
REM Do not use the CALL command in the next line to execute Dart. CALL causes
REM Windows to re-read the line from disk after the CALL command has finished
REM regardless of the ampersand chain.
"%dart%" --disable-dart-dev --packages="%flutter_tools_dir%\.packages" %FLUTTER_TOOL_ARGS% "%snapshot_path%" %* & exit /B !ERRORLEVEL!
When I change the last line into this flutter run started to work.
"%dart%" --disable-dart-dev --packages="%flutter_tools_dir%\.packages" %FLUTTER_TOOL_ARGS% "%snapshot_path%" %*
exit /B !ERRORLEVEL!
I am not quite sure what makes my fix actually work or not work, but I assumed there might be some quirks in cmd.exe that maybe windows not only caches both commands but also cached error level instead of delay evaluating it. Can I safely use this fix or is there some idea on a more proper fix?
Activity
pedromassangocode commentedon Jan 19, 2021
Hi @phr34k
We don't expect you to modify Flutter tool files by yourself!
Can you please revert the changes you made and then provide the output of
flutter doctor -v, yourflutter run --verboseand yourpubspec.yaml.Thank you
phr34k commentedon Jan 19, 2021
Young padawan, much learn you have to. No in all seriousness, I totally agree.
Here's the flutter doctor output, note it says flutter plugins are missing because the android studio changes folder layouts, flutter does in fact just work normally.
logs
Here's pubspec.yaml
Here's
flutter run --verbose(stdout) successfull invocation.Here's flutter run (stderr) of an unsuccessful run.
And here's the stdout of an unsuccesfull run
pedromassangocode commentedon Jan 19, 2021
Hi @phr34k
Can you please provide
flutter run --verbosewith only the crash logs reported in your first comment? It is a little bit confusing to me all the different logs you provided above. If you are facing any different issue other than in the OP, please file a new issue!Thank you
phr34k commentedon Jan 20, 2021
@pedromassango I did two runs, one was a success, and one that failed (so you have a comparison.
Basically, due to the length of the log, I had to pipe the output to a file in order to capture it fully. But apparently, piping only captured the stdout stream, and so I copied over stderr from the console. I provided you both parts of the log to give you the full log.
From what I can tell from the log (stderr) by glancing over it, there seems to be an error copying one of the assets over. Am I right to read that this right that error propagates into the build failing? If so, any thoughts on what can I actually do about it on my side?
So if the filehandle stays open with exclusive access, it's probably due to an orphaned process either from flutter or vscode or something else that doesn't play nice (thumbnail generation? windows indexing?).
[-]Build failed with an exception, script 'D:\SDK\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 904[/-][+]Target debug_android_application failed: FileSystemException: Cannot copy file to <elided>, path = <elided> (OS Error: Cannot create a file when that file already exists. [/+]phr34k commentedon Feb 8, 2021
Any update on this problem? The build error is getting more and more disruptive the bigger of an application I am working on.
danagbemava-nc commentedon Oct 6, 2022
Considering the age of the issue and lack of any activity for an extended period (over a year), I am going ahead and closing this as stale.
@phr34k If by any chance, you see the same error using latest stable version of the framework, kindly file a new issue and provide any relevant information that you can.
github-actions commentedon Oct 20, 2022
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.