Search Issue Tracker
Won't Fix
Won't Fix in 1.20.X
Votes
5
Found in [Package]
1.20.3
Issue ID
ADDR-2914
Regression
No
UnityEngine.AddressableAssets.InvalidKeyException is thrown when loading .uxml file using Addressables
Reproduction steps:
1. Open the user’s attached project
2. Enter Play Mode
3. Observe the Console
Expected result: Unity loads the .uxml file using the Addressables package
Actual result: Throws UnityEngine.AddressableAssets.InvalidKeyException
Reproducible with: 1.19.19, 1.20.0, 1.20.3 (2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a5)
Couldn't test with: 1.20.3 (2020.3.37f1 couldn’t downgrade)
Reproducible on: Windows 10 Pro 21H2
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
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.20.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.