Search Issue Tracker
Fixed in 1.2.4
Votes
4
Found in [Package]
0.7.5-preview
Issue ID
1151028
Regression
No
Coroutine does not continue after yield returning loaded Addressable Assets when AsyncOperation.allowSceneActivation is false
How to reproduce:
1. Open the "Boot" Scene in the attached "AddsSceneBug.zip" Project
2. Enter Play Mode
3. Observe the "Main" Scene in the Hierarchy
Expected Behavior: After loading Addressable Assets the "Main" Scene is Activated
Actual Behavior: The "Main" Scene is never Activated
Reproducible with(Unity Versions): 2018.4.0f1, 2019.1.1f1, 2019.2.0a14, 2019.3.0a2
Reproducible with(Package Versions): 0.7.5-preview
Note: According to the Console - the Addressables are loaded, however, the Coroutine does not proceed to set allowSceneActivation to true.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.2.4):
Main scene is activated correctly.