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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment