Search Issue Tracker
Fixed
Fixed in 1.0.0
Votes
0
Found in [Package]
1.0.0-pre.10
Issue ID
LOC-361
Regression
No
[Localization] Build fails and error is thrown when building on Android Platform with certain Locale codes and Android App info
How to reproduce:
1. Create a new Unity project
2. Open the Package Manager (Window->Package Manager)
3. Install the Localization package via git URL ("+"->Add package from git URL...->com.unity.localization->Add)
4. Open the Localization settings (Edit->Project Settings...->Localization)
5. Create Localization Settings
6. Generate zh-Hans and zh-Hant locales (Locale Generator->Select "zh-Hans" and "zh-Hant" Code Locales->Gnerate Locales)
7. Add Android->App Info to the Metadata
8. Open the Build Settings (File->Build Settings...)
9. Switch to the Android Platform
10. Build
Expected results: The project builds successfully
Actual results: A "Invalid resource directory name" error window pops up, the build fails
Reproducible with: 0.11.0-preview (2019.4.29f1, 2020.3.17f1, 2021.1.18f1), 1.0.0-pre.10 (2019.4.29f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a5)
Could not test with: 0.10.0-preview and earlier because the Metadata section did not exist
Notes:
- This happens with "zh-Hans" and "zh-Hant" codes as well as with "ha-Latn" and "ha-Latn-NG" codes
- The issue is not reproducible when building on Standalone
- The issue is not reproducible when using iOS App Info instead of Android's
- After either multiple atempts or building on diffferent platforms and then again on Android the Android platform will succeed
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 1.0.0):
Confirmed no longer reproducible with:
Version: 2022.1.0a9.1212
Revision: trunk 5a1ba9fbc92d
Built: Fri, 10 Sep 2021 03:09:36 GMT
Tested with Localization 1.0.0 and Samsung Galaxy S9 (Android 10)
Notes: Tested building with locales codes that included "Hans", "Hant", "Latn", "Cyrl", "Arab", "valencia" as they were mentioned to cause issues in the fix PR.