Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.1f1
2019.1.0a1
2019.2.0a1
Issue ID
1138314
Regression
No
EditorApplication.projectWasLoaded doesn't fire when the editor is launched with -batchmode -quit -executeMethod
How to reproduce:
1. Download the submitted project (ProjectLoaded)
2. Open Terminal/CMD
3. Run the project with the following arguments: -batchmode -quit -projectPath -logFile and -executeMethod Editor.Builder.Build
4. After the project has quit, see the log file
Expected result: log file contains 'Running project load AutoRuns'
Actual result: log file does not contain 'Running project load AutoRuns'
Reproducible with: 2017.4.23f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Notes:
Tested with macOS and Windows
Running the project without the -quit argument does not cause this issue
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (2019.3.X):
Solution for this should be to use -executeMethod and define another path to the code.