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
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
- Play, Pause, Skip Frame buttons in the Toolbar don't have Tooltips when hovering the mouse over them
- Mesh.GetIndexBuffer() requires Mesh's 'Read/Write' flag to be enabled to get its index buffer data in Builds
- [Backport] [Sprite Atlas V1] Editor crashes when calling SpriteAtlasUtility.PackAtlases
- Deterministic builds have different files when built from the same project
- PlayerBuildInterface.ExtraTypesProvider no longer provides types to IL2CPP
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a17