Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.3f1
2020.2
Issue ID
1223627
Regression
No
Awake is called in a different order when IProcessSceneWithReport.OnProcessScene() is called in the Editor and the Build
How to reproduce:
1. Open the attached project's Scene labeled "OnProcessSceneTest"
2. Enter the Play Mode
3. In the Console Window, inspect the order of the "Awake" and "OnProcessScene" callbacks
4. Build the project
5. Play the Build
6. Inspect the Player.log
Expected result: Player.log has the same order of callbacks logged
Actual result: Player.log has a different order of callbacks logged
Reproducible with: 2018.4.18f1, 2019.3.4f1, 2020.1.0a25, 2020.2.1.0a1
Couldn't test with: 2017.4.37f1 (IProcessSceneWithReport does not exist)
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
The ProcessScene callback has always been called after the scene is loaded. In the case of an editor build though, the call to Awake is blocked while in Playmode it is not blocked.