Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
Issue ID
834325
Regression
No
Improve error handling for command line activation
Repro:
1. Attempt to activate Unity editor from command line (refer to https://docs.unity3d.com/Manual/CommandLineArguments.html)
2. During activation miss one of the arguments - e.g. -password, enter incorrect password
3. Observe that editor is not activated, it times out and there is no error message shown in the terminal window
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Add comment