Search Issue Tracker
Fixed
Fixed in 2023.3.X, 2023.3.0b5
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52668
Regression
No
Build folder is empty when built to a shared folder on another machine
How to reproduce:
1. Set up a shared folder on one machine and connect to it with the machine that will be used to reproduce the issue
2. Create a new Unity Project
3. Build the Project to the created shared folder
4. Observe the Build folder
Expected result: Build folder contains the build
Actual result: Build folder is empty and the Editor reports the Build as "Succeeded"
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproduced on:
- Windows 10
Did not reproduce on:
- MacOS 13.6 (Intel)
Notes:
- If the shared folder is a mapped network drive, the build folder correctly contains the Build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment