Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X
Votes
0
Found in
Issue ID
1058840
Regression
No
Editor exits with return code 0 even with compilation errors when Unity Analytics is enabled
Untiy Editor exits with incorrect return code 0 if there are compilation errors and Editor is launched from the command line in a -batchMmode (e.g. Unity.exe -batchMode -projectPath %projectPath% -quit -logFile)
It happens if Analitics is enabled in ProjectSettings\UnityConnectSettings.asset:
UnityAnaliticsSettins:
m_Enabled: 1
Editor exits with correct return code 1 if Analitics is disabled.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Add comment