Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2020.1
Issue ID
1183783
Regression
No
[MacOS] Manual input requiring pop-up appears in batch mode if Unity didn't close properly on the last launch
Reproduction steps:
1. Create a New project
2. Exit and Re-Open Unity
3. Force Quit Unity before it properly starts
4. Run it in batch mode with these Command Line Arguments: "-batchmode -projectPath"
5. Notice a pop-up requiring manual input
Expected Result: No pop-up or manual input requiring actions can be prompted in batch mode
Actual Result: A pop-up appears in batch mode
Reproduced with: 2020.1.0a6, 2019.3.0b5, 2019.2.7f2, 2018.4.10f, 2017.4.32f1
Note:
Tested on MaOS HighSierra, doesn't affect Windows
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a11
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.26f1