Search Issue Tracker
Fixed
Fixed in 1.2.1
Votes
0
Found in [Package]
1.0.5
Issue ID
LOC-523
Regression
No
Asset is not added to the Localization Shared group when the same Asset is used for more than one Locale
How to reproduce:
1. Open the attached "1382726_Repro.zip" project
2. In the Project window select "AssetTable"
3. In the Inspector press "Open in Table Editor"
4. Drag the "GameObject" Asset from Project window to Localization Tables English Locale object reference
5. Repeat the same for Chinese, Japanese, and Korean Locales
6. Open Addressables Groups (Window->Asset Management->Addressables->Groups
7. Expand "Localization-Assets-Shared" and "Localization-Assets-English (en)"
Expected results: "GameObject" Asset is in the "Localization-Assets-Shared" group
Actual results: "GameObject" Asset is in the "Localization-Assets-English (en)" group
Reproducible with: 1.0.0 (2019.4.34f1, 2020.3.24f1), 1.0.5 (2019.4.34f1, 2020.3.24f1, 2021.2.6f1, 2022.1.0b2)
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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Duplicate of LOC-523
Resolution Note (fix version 1.2.1):
Fixed assets that were used by multiple locales not being added to the shared addressables group.