Search Issue Tracker
Fixed in 1.14.2
Votes
1
Found in [Package]
0.8.6, 1.1.7
Issue ID
1173999
Regression
No
[Addressables] Exceptions are thrown at runtime when Play Mode Script option is set to Fast Mode
How to reproduce:
1. Open the attached project ("case_1173999-steel-flood.zip")
2. Open the repro scene ("World")
3. Build Player Content
4. Enter the Play Mode
5. Inspect the console
Expected results: No exceptions are thrown
Actual results: Exceptions are thrown (in operation "UnityEngine.AddressableAssets.Initialization.InitializationOperation")
Reproducible with: 2018.4.5f1, 2019.1.14f1, 2019.2.1f1
Couldn't test with 2019.3 branch, because of project crashing
Reproducible with package versions: 0.8.6, 1.1.7
Notes:
Changing the "Play Mode Script" option to "Virtual" or "Packed Play Mode" fixes this issue
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
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
- [Quest 2] Input field selected state getting stuck when dragging and selecting on Quest
- Render Objects Renderer Feature are not writing to the Depth Buffer when Write Depth is enabled
- Field names under "Anchors" in the RectTransform Component don't get focused when "tabbing" through the fields
Resolution Note (fix version 1.14.2):
This has been resolved in 1.14.0. There was also an accompanying issue that has been resolved with this which was loading assets from a label causing similar issues.