Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.2.X
Won't Fix in 5.6.X, 2017.1.X
Votes
0
Found in
2017.1.0p2
Issue ID
950616
Regression
Yes
[iOS] Unity fails to build the project on FAT32 mounted drive
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 new project on a created drive
7. Switch platform to iOS and hit build
Expected: Unity should successfully build an empty project
Actual: On 5.6.x versions UnusedByteCodeStripper2.exe fails to run and so build fails (code stripping is disabled)
On 2017.x versions UnityLinker.exe fails to run and so build fails.
Reproduced with: 5.6.0a1, 2017.1.1p2, 2017.2.0b11, 2017.3.0b1
Not reproducible with: 5.5.0f3, 5.5.4p5
Fixed in: 2018.1.0a2
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
danielgamar
Jun 26, 2019 11:30
This one is not fixed as of 2019.1.6f1.