Search Issue Tracker
By Design
Votes
0
Found in
2022.1.0a2
2022.1.0b4
2022.2
Issue ID
1397993
Regression
Yes
[Android] Build fails with error message "UnityException: Invalid project path" when using non-ASCII characters in project name
Reproduction steps:
1. Open Unity Hub
2. Press the "New project" button at the top right corner
3. In Project Settings > Project name set the name using non-ASCII characters (e.g "ąąąčččęęę")
4. Press "Create project" and wait for the Editor to open
5. Go to Build Settings, switch to Android Platform, and build the project
Expected result: The project is built, no errors in the Console window
Actual result: The project build fails, the error is thrown in the Console window: "UnityException: Invalid project path
Project path '/Users/*username*/*projectpath*/ąąąčččęęę' contains non-ASCII characters at position 32, Android Tools don't work properly with non-ASCII paths. Please move your project to path containing only ASCII characters."
Reproducible with: 2022.1.0a2, 2022.1.0b7, 2022.2.0a4
Not reproducible with: 2019.4.36f1, 2020.3.29f1, 2021.2.12f1, 2022.1.0a1
Could not test with: 2022.2.0a5 (Unity Hub does not allow to create a new project with non-ASCII characters)
Notes:
- Issue is reproducible on macOS and Windows
- Issue is not reproducible when building for Mac Standalone, iOS, and WebGL Platforms
- Issue is reproducible with Lithuanian, German, Chinese language special characters
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This is by design, the error explains why you can't have non ASCII characters in path