Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.21.20
Issue ID
ADDR-3646
Regression
No
Addressables.LoadResourceLocationsAsync throws a "NullReferenceException" when the Asset it is searching for is deleted using external tools
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Project window, open the context menu of “Assets/AddressableAssets/ExampleAsset“ Asset and select “Show in Explorer”
3. In the opened Windows File Explorer, delete “ExampleAsset.prefab” and “ExampleAsset.prefab.meta“
3. Enter Play Mode
4. Observe the Console window
Expected result: No exceptions are logged in the Console
Actual result: “NullReferenceException” is logged in the Console
Reproducible with: 1.21.20 (2022.3.20f1) (By user)
Reproducible on: Windows 11 (By user)
Not reproducible on: No other environment tested
Notes:
- Not reproducible by CQA
- A workaround for this issue is restarting the Editor
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.21.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.