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
- Particle System only collides with one Terrain Collider at a time when Collision Type is set to 'World'
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
Add comment