Search Issue Tracker
By Design
By Design in 1.19.X
Votes
1
Found in [Package]
1.19.14
Issue ID
ADDR-3110
Regression
No
Warnings "The referenced script on this Behaviour (Game Object '<null>') is missing!" and error "NullReferenceException: Object reference not set to an instance of an object" thrown when in Play Mode after building Addressables
How to reproduce:
1. Open the project “IN_24945”
2. Open the “SceneTest” Scene in Assets
3. Open the “Addressables Group” window
4. Set the Play Mode script to “Use Existing Build”
5. Build the Addressables
6. Enter the Play Mode
Expected result: no warnings and errors in the Console
Actual result: warnings “The referenced script on this Behaviour (Game Object '<null>') is missing!” and error “NullReferenceException: Object reference not set to an instance of an object” in the Console
Reproducible with: 1.19.15 (2020.3.42f1)
Couldn't test with: 1.19.15 (2021.3.16f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a23 (due to compiler errors))
Reproducible on: Windows 10 Pro
Notes:
- not reproducible in the new project
Workaround: enable “Enter Play Mode options” in the Editor settings
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
After looking into this issue we believe that the null ref exception is caused by the users scripts and is not an issue with Addressables.
Resolution Note (1.19.X):
After looking into this issue we believe that the null ref exception is caused by the users scripts and is not an issue with Addressables.