Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2021.2.0a15
2021.3.0f1
2022.1
2022.2
Issue ID
1422084
Regression
Yes
[macOS] Build fails with command failing to write to output file when using 3rd party plugin
How to reproduce:
1. Download the attached project 'Stream.zip'
2. Build the project on macOS
3. Observe the Console
Expected result: Build succeeds without errors
Actual result: Build fails with errors in the Console:
Failed because this command failed to write the following output files:
Library/Bee/artifacts/MacStandalonePlayerBuildProgram/Features/Assembly-CSharp-FeaturesChecked.txt
Reproducible with: 2021.2.0a15, 2021.3.2f1, 2022.1.0f1, 2022.2.0a14
Not reproducible: 2019.4.39f1, 2020.3.34f1
Could not test with: 2021.2.0a14 (the errors appear to be different)
Tested and reproduced with:
macOS 12.2 (Intel)
Tested and not reproduced with:
Windows 10
Notes:
- Only reproduces when making a build for macOS (Standalone), does not reproduce when building for Android
- Reproducible with Mono and IL2CPP
- Unity 2021.2.0a15 had ~100 'failed to write to output file' errors, latest versions have only 1 error of this type
Comments (2)
-
Grimraider1
Aug 23, 2023 11:13
setting the "Camera Usage Description" and the "Microphone Usage Description" in Project Settings -> Player
see also
https://forum.unity.com/threads/build-failing-with-command-failed-to-write-the-following-output-file.1238776/
https://forum.unity.com/threads/build-failed-from-mac-failed-to-write-output-files.1234633/
https://forum.unity.com/threads/ios-failed-because-this-command-failed-to-write-the-following-output-files.1346090/ -
ina
Jan 20, 2023 11:36
Failed because this command failed to write the following output files:
Library/Bee/artifacts/iOS/Features/Assembly-CSharp-FeaturesChecked.txtAlso occurs for iOS in 2022.1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a17