Search Issue Tracker
Fixed
Fixed in 1.1.0
Votes
0
Found in [Package]
1.0.3
Issue ID
LOC-464
Regression
No
Duplicate Key Ids are generated in the Localization Table when imported Keys have Duplicate names
Steps to reproduce:
1. Open the attached project "1366174.zip"
2. Select Localization>TestTable in the Project window
3. Press 'Open in Table Editor' in the Inspector window
4. Right-click on the Key column and Select 'Key Id' in the Tooltip in the Localization Tables window
5. Observe 'Key Id' column
Expected result: Every row has unique Key Ids
Actual result: Both 'CollissionKey' rows have the same Key Ids
Reproducible with: 1.0.3 (2019.4.31f1, 2020.3.20f1, 2021.1.19f1, 2021.2.0b15, 2022.1.0a13)
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 (fix version 1.1.0):
Entries with duplicate names will now be ignored when pulling from Google Sheets. A message will be added to the report to notify you when this happens.