Search Issue Tracker
Fixed
Fixed in 1.3.1
Votes
0
Found in [Package]
1.0.0-pre.10
Issue ID
LOC-400
Regression
No
New localization assets created automatically and/or old assets are modified when loading project without Library folder
How to reproduce:
1. Download the attached project "1358410.zip"
2. Download and install Version Control software "SmartGit": https://www.syntevo.com/smartgit/download/#installation-instructions
3. In SmartGit, go to the Menu bar and press Repository > Add or Create
4. Select the "AddressableAssetsData" folder to add it to the Version Control (~/1358410/Assets/AddressableAssetsData/AssetGroups)
5. In the "Repositories" window, select the "AddressableAssetsData" repository
6. In the Toolbar, press "Commit", select all files, and press the "Commit" button
7. Open the project in Unity
8. Inspect changes in the Files window of SmartGit
Expected result: No new localization assets are created and old ones are not modified
Actual result: New localization assets are created and/or old ones are modified
Reproducible with: 1.0.0-pre.10 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5)
Note:
- In Unity 2020.3 and 2021.1 no new files are created, only old localization assets are modified
- Any Version Control software can be used to observe the issue
Comments (1)
-
Peter77
Aug 17, 2021 15:50
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.3.1):
Fixed in: Localization 1.3.1