Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
1.22.2
Issue ID
ADDR-3780
Regression
No
"NullReferenceException" error when loading an addressables Scene in Player
Reproduction steps:
1. Make sure that the “AddressableSceneBug“ folder in the “C:\Users\[user]\AppData\LocalLow\Unity\DefaultCompany_AddressableSceneBug\” path is deleted
2. Open the attached “repro_IN-84434“ project
3. Go to “File → Build Settings…” and press “Build“
4. Once the build finishes, launch the “AddressableSceneBug“ executable
5. Observe the messages on the screen and the “Player.log“ file, which is located in the “C:\Users\[user]\AppData\LocalLow\DefaultCompany\AddressableSceneBug\” path
Expected result: The “DOWNLOADED AND SWITCHED SCENE“ message is displayed and the “Player.log“ file contains no errors
Actual result: The “Loading Scene 100.00 %“ is displayed and the “Player.log“ file contains the “NullReferenceException: Object reference not set to an instance of an object“ error
Reproducible with: 1.18.4 (2022.1.0a1), 1.22.2 (2022.3.48f1)
Couldn’t test with: 1.22.2 (2021.3.44f1) - The Editor fails to build the Player with the “NullReferenceException“ error, which comes from “UnityEditor.Rendering.Universal.ShaderBuildPreprocessor.GetSupportedShaderFeatures“, 2.2.2 (6000.0.21f1) - The Player gets stuck on “Unloading 0.00 %“ with “RemoteProviderException“, “System.Exception“ and “OperationException“ errors in the Player.log, and the issue is not fixable when relaunching
Reproducible on: Windows 10 (22H2), Windows 11 (10.0.22631) (user’s)
Not reproducible on: No other environments tested
Notes:
- The issue doesn’t reproduce in the Editor
- Relaunching the executable fixes the issue
- On the 1.18.4 version of the Addressables, the message that gets stuck is “Loading Scene 90.00 %”
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Resolution Note:
Ticket no longer reproduces on newsest version of 1.x or 2.x stream of addressables, so should be fixed. If you find it reproducing again, feel free to submit a new bug.