Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0a1
2020.1
2020.1.5f1
2020.2
Issue ID
1278242
Regression
Yes
Fatal error is not thrown and Editor continues to function when working directory is changed with Directory.SetCurrentDirectory
Reproduction steps:
1. Open the attached project ("case_1278242-dirbug.zip")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Exit Play Mode
5.Unfocus and re-focus the Editor
Expected result: Fatal error is thrown, explaining that changing the working directory is not supported
Actual result: Fatal error is not thrown, Editor continues to function, creating any asset yields errors
Reproducible with: 2019.3.0a1, 2019.4.11f1, 2020.1.6f1, 2020.2.0b3
Not reproducible with: 2018.4.27f1, 2019.2.21f1
Note: When setting Editor's working directory through a script, it has to be set back to the original path manually, or fatal error should be thrown explaining that this is not supported
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b11