Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.6f1
2019.2.0a1
2019.3.0a1
Issue ID
1170364
Regression
No
EditorSceneManager.SaveCurrentModifiedScenesIfUserWantsTo() returns 'true' when 'Don't Save' is selected
How to reproduce:
1. Open user-submitted project (TMPCrashBug)
2. Wait for a scene saving prompt to pop-up
3. Select 'Don't Save'
Expected result: the follow-up pop-up window shows that EditorSceneManager.SaveCurrentModifiedScenesIfUserWantsTo() returned 'false'
Actual result: the follow-up pop-up window shows that EditorSceneManager.SaveCurrentModifiedScenesIfUserWantsTo() returned 'true'
Reproducible with: 2017.4.31f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0f1, 2019.3.0a11
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
- 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
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.1):
Documentation fix - EditorSceneManager.SaveCurrentModifiedScenesIfUserWantsTo() returns 'true' if "Save" or "Don't Save" are selected; if '"Cancel" is selected instead, 'false' is returned