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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a17