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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment