Search Issue Tracker
Fixed
Votes
4
Found in [Package]
1.18.2
Issue ID
ADDR-2070
Regression
Yes
Loading a Scene with Addressables.LoadSceneAsync from an Scene built using "Use Existing Build" thows an error
Reproduction steps:
1. Open the user's attached "Addressables_NullReference.zip" project
2. Go Window -> Asset Management -> Addressables -> Groups
3. In the Addressables Groups window go Build -> New Build -> Default Build Script
4. Enter the Play Mode
5. Observe the console
Expected result: Three Debug.Logs are printed out
Actual result: A NullReferenceException is thrown
Reproducible with: 1.18.9, 1.18.2 (2021.2.0a21, 2021.1.11f1)
Not reproducible with: 1.17.17 (2021.2.0a21, 2021.1.11f1) 1.18.9, 1.18.2 (2020.3.12f1)
Could not test with: 2019.4.26f1, 2018.4.36f1 (project cannot be downgraded)
Note:
- Full exception is: NullReferenceException: Object reference not set to an instance of an object
TestMonoBehaviour.Awake () (at Assets/TestMonoBehaviour.cs:9)
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
- UI Toolkit Dropdown list elements use default color instead of USS color override when hovering mouse over them
- BuildOptions.Development is ignored when running a batch mode build for the win64 buildTarget
- VisionOS Player Memory Usage continuously rises when the Player has a VisionOSVideoComponent running that is set to a URL Video
- Terms of Service agreement checkbox is invisible under specific OS system themes (UI Accessibility)
- Tile Palette: "Create New Tilemap" dropdown area is displayed in several colors
Resolution Note:
Issue with MonoScript loading.
Requires building a MonoScript bundle introduced in 1.18.2 in order to prevent conflicts in MonoScripts