Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.1.0f2
Issue ID
1146863
Regression
No
[Scripting] IEnumerator is automatically called when named Main()
Reproduction steps:
1. Open the attached project inside of "Corutinas.zip"
2. Open and Play "SampleScene"
Expected result: IEnumerator Main() does not automatically call
Actual result: IEnumerator Main() plays on Scene Play
Reproduces on: 2017.4.25f1, 2018.3.14f1, 2019.1.0f2, 2019.2.0a13
Note:
- IEnumerator Main() is called after the Start() event
Comments (2)
-
CianNoonan
Jul 23, 2020 15:30
Is this fixed or not? The changelog says it is https://unity3d.com/unity/whats-new/2020.1.0
-
FWCorey
Apr 30, 2019 23:35
This could actually be a feature if it was documented
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
- [LinuxEditor] Crash on "XAddExtension" when opening the Unity Editor on Linux with -batchmode and -nographics on a project with a custom default cursor
- Folder attachment size is displayed as 0 bytes when a folder is added to the Hub bug reporter's attachments
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
Resolution Note (fix version 2020.1):
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.