Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X, 2019.3.X
Votes
1
Found in
2019.1.0a7
2019.1.6f1
Issue ID
1166108
Regression
Yes
[IL2CPP] Unity.app/Contents/il2cpp/build/UnityLinker.exe fails to Run when building from FAT32 on MacOS
To reproduce:
1. Open "Disk Utility" on your Computer
2. Select your Internal Drive and click on the partition button
3. In "Partition Device" window hit "+" button
4. Create a drive. Format: MS-DOS(FAT). Select a small size for example 10gb
5. Hit apply
6. Launch Unity and create a new project on a created drive
7. Switch platform to Standalone (IL2CPP), iOS or Android (IL2CPP) and hit Build
Expected results: Unity should successfully build an Empty Project
Actual results: Unity fails to build and throws Error:
"Failed running /Applications/Unity/Hub/Editor/2019.1.6f1/Unity.app/Contents/il2cpp/build/UnityLinker.exe -out="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/tempStrip" -x="/Applications/Unity/Hub/Editor/2019.1.6f1/PlaybackEngines/iOSSupport/Whitelists/Core.xml" -x="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/../platform_native_link.xml" -x="/var/folders/jf/f9hwnd8d6lzfxr7p8936yq2r0000gp/T/tmp5e305ea8.tmp" -x="/var/folders/jf/f9hwnd8d6lzfxr7p8936yq2r0000gp/T/tmp77934080.tmp" -x="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/TypesInScenes.xml" -d="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed" --include-unity-root-assembly="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/Assembly-CSharp-firstpass.dll" --include-unity-root-assembly="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/Assembly-CSharp.dll" --include-unity-root-assembly="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/VuforiaScripts.dll" --include-unity-root-assembly="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/UnityEngine.UI.dll" --include-unity-root-assembly="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed/Vuforia.UnityExtensions.dll" --dotnetruntime=il2cpp --dotnetprofile=unityaot --use-editor-options --include-directory="/Volumes/STORAGE/Work/Gamar/Unity/TrailPlayar/NMM/TrailPlayar_iOS/Temp/StagingArea/Data/Managed" --rule-set=Conservative --engine-stripping-flag=EnableUnityConnect --engine-modules-asset-file="/Applications/Unity/Hub/Editor/2019.1.6f1/PlaybackEngines/iOSSupport/Whitelists/../modules.asset""
Notes:
- This issue does not happen on Mono Scripting Backend
Reproduced on Unity 2019.1.0a7, 2019.1.8f1, 2019.2.0b7 and 2019.3.0a8
Not reproduced on Unity 2018.3.14f1, 2018.4.3f1 and 2019.1.0a6
Regression on Unity 2019.1.0a7
Comments (3)
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
AjJAISWAL
Apr 05, 2020 20:10
I am also getting the same error in unity 2019.3.7f1.
AjJAISWAL
Apr 05, 2020 20:08
Still getting the same error in unity 2018.3.14f1
AxonGenesis
Aug 06, 2019 19:04
Still experiencing this error in 2019.2.0f1