Search Issue Tracker
Won't Fix
Won't Fix in 1.20.X
Votes
0
Found in [Package]
1.20.5
Issue ID
ADDR-3015
Regression
No
UnityEngine.AddressableAssets.InvalidKeyException is thrown when changing localization
Reproduction steps:
1. Open the user’s attached project
2. Enter Play Mode
3. In Game View, click on any language
4. Observe the Console Window
Expected result: Localization is changed without thrown exception
Actual result: Throws “OperationException : GroupOperation failed because one of its dependencies failed
UnityEngine.AddressableAssets.InvalidKeyException: Exception of type 'UnityEngine.AddressableAssets.InvalidKeyException' was thrown. No Location found for Key=ba5a6c87df7d7634496e34cecfa9cd9a”
Reproducible with: 1.19.19 (2020.3.40f1, 2021.3.11f1), 1.20.5 (2020.3.40f1, 2021.3.11f1, 2022.1.20f1, 2022.2.0b10, 2023.1.0a14)
Reproducible on: Windows 11 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
- Project Auditor's "Install Rules" button has to be pressed twice to proceed when any compilation error in the Editor is present
- Crash on Scripting::UnityEngine::SubsystemManagerProxy::ClearSubsystems when adding a Mesh Collider Component to a GameObject
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (1.20.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.