Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.2.0a3
2019.3.10f1
2020.2
Issue ID
1253812
Regression
Yes
[iOS] Editor throws a "Failed running UnityLinker.exe" error when building iOS project from an ExFAT partition on MacOS
How to reproduce:
1. Create an ExFAT partition on the machine's hard drive (if one is not already present)
2. Create a new Unity project in the ExFAT partition
3. Build any Scene for iOS
Expected result: the build succeeds
Actual result: "Failed running" errors occur and it is not possible to build iOS projects to an ExFAT partition
Reproducible with: 2019.2.0a3, 2019.2.21f1, 2019.4.1f1, 2020.1.0b12, 2020.2.0a11
Not reproducible with: 2018.4.23f1
Could not test with: 2019.1.14f1, 2019.2.0a1, 2019.2.0a2 (cannot open project due to "Fatal error: attempt to write readonly database), 2020.2.0a12, 2020.2.0a14 (the compiling process never finishes and the Editor freezes)
Notes:
1. Opening an existing project located in the partition may cause a Fatal Error to occur, which is due to this bug: https://issuetracker.unity3d.com/product/unity/issues/guid/1248975
2. Not reproducible when building for Standalone
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a17