Search Issue Tracker
Fixed
Fixed in 1.5.x
Votes
0
Found in [Package]
1.5.3
Issue ID
LOC-1182
Regression
No
“NullReferenceException: Object reference not set to an instance of an object“ error appears when adding an elements to List<LocalizedAsset<T>> or LocalizedAsset<T>[] in the Inspector
Reproduction steps:
1. Open the attached “repro_IN-89353“ project
2. Open the “Assets/Scene.unity“ Scene
3. In the Hierarchy, select the “Test“ GameObject
4. In the Inspector, in the “Test Component (Script)“ Component, expand the “Localize Audio List“ dropdown
5. Press the '' button
6. Observe the Console
Expected result: No errors appear
Actual result: “NullReferenceException: Object reference not set to an instance of an object“ error appears
Reproducible with: 1.0.0-pre.9 (2021.3.47f1), 1.5.3 (2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0a10)
Reproducible on: Windows 10 (22H2), Windows 11 (24H2) (reporter’s environment)
Not reproducible on: No other environments tested
Notes:
- On 2021.3.47f1, after pressing the '' button, the dropdown UI breaks
- On 2021.3.47f1, on the 1.5.3 version of the Localization package, after pressing the ‘+' button, saving the Scene with “Ctrl + S“ button combination doesn’t work
- According to the reporter, the issue is in the “if (baseType.IsArray) BaseType = baseType.GetElementType().BaseType;” line, which is the 33rd line of the “com.unity.localization@1.5.3\Editor\UI\Localized Reference\LocalizedAssetPropertyDrawer.cs” Script
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment