Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2017.4.25f1
2018.3.4f1
2019.1.0b2
2019.1.4f1
2019.2.0a1
2019.3.0a1
Issue ID
1157976
Regression
Yes
[Linux] Game object Start and Update methods are not called for game objects created from Editor Mode tests
To reproduce:
1) Open the attached project
2) Open Window -> General -> Test Runner
3) "Run all"
Expected: All green
Actual: Only one test green, others fail
Not reproduced - Reproduced
2017.4.0f1 - 2017.4.25f1
2018.3.0b1 - 2018.3.4f1, 2018.4.0f1
[][][][][][][][][] - 2019.1.0b2, 2019.1.4f1
[][][][][][][][][] - 2019.2.0a1, 2019.2.0b3
2019.3.0a3 - 2019.3.0a2, 2019.3.0a1
Not reproduced in Win 10 and Mac
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2019.1):
Fixes to Linux editor window management preventing gameobjects created from editor test scripts from running Start() and Update()
Resolution Note (fix version 2018.4):
Fixed Editor window focus issues causing editor tests to fail.