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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Issue with MonoScript loading.
Requires building a MonoScript bundle introduced in 1.18.2 in order to prevent conflicts in MonoScripts