Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
1
Found in
2019.4
2020.1.0b10
2020.2.0a12
Issue ID
1251974
Regression
Yes
[iOS] Building with Default Icon for the second time causes the Build to fail "System.IO.__Error.WinIOError DirectoryNotFound"
Reproduction steps:
1. Create a new project
2. Switch platform to iOS
3. Import any PNG file ("pnggrad16rgb.png" in edits)
4. Set the PNG as Default Icon in Player Settings
5. Go File -> Build Settings -> Build
6. Select folder and Save
7. You will receive errors regarding unfreed allocations ALLOC_TEMP_THREAD, but the build will succeed
8. Go File -> Build And Run (read note 1)
Expected result: build succeeds
Actual result: build fails with errors: DirectoryNotFoundException System.IO.__Error.WinIOError (System.Int32 errorCode, System.String maybeFullPath)...
Reproducible with: 2020.2.0a12, 2019.4.1f1
Not reproducible with: 2018.4.22f1, 2019.3.15f1, 2020.2.0b11, 2020.2.0a11, 2020.2.0a13 -> fix version
Notes:
1. In step 8 you can also Append an existing build
2. The issue is fixed in 2020.2.0a12
Comments (3)
-
savantedroid
Jun 20, 2020 13:40
How come LTS version has a bug that prohibits a build :)
-
ivug
Jun 18, 2020 04:13
You should fix this in 2019.4 LTS
How do you expect we can build for iOS with this issue?
-
magnetica
Jun 12, 2020 12:52
also present in 2019.4 LTS.. OMG
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a13
Resolution Note (fix version 2019.4):
Fixed in 2019.4.7f1 (e992b1a16e65)