Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4, 2023.3.0a1, 2024.1.0a1
Votes
0
Found in
2021.3.27f1
2022.3.2f1
2023.1.0f1
2023.2.0a12
2023.2.0a19
2024.1.0a1
Issue ID
UUM-40467
Regression
Yes
Wrong directory is opened when "BuildOptions.ShowBuiltPlayer" is used
Reproduction steps:
1. Open project “{_}BuildScriptBugReport{_}” in Windows Editor
2. Select “Builds\Windows Build” in the Editor menu (This is a custom script that adds an editor button to the top off the unity editor)
Expected result: the folder locating the built Player is opened after compiling (The built project should be located within a build folder of the editor project)
Actual result: the “Documents” folder is opened after compiling (The build is not located here)
Reproducible with: 2021.3.27f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a19
Issue regressed in 2023.20a12 and was working in 2023.2.0a11
Reproducible on: Windows 10, Windows 11
Not reproducible on: macOS Ventura 13.2.1 (Intel)
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
Resolution Note (fix version 2023.3.0a1):
Editor: Fix BuildOptions.ShowBuiltPlayer on Windows not working when the player build path contains ".." (parent directory).