Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2019.1.0b4
Issue ID
1129992
Regression
Yes
[UWP] Build fails when the project folder name has non-ascii character.
When non-ascii character is used in the project folder or folder that is used in the final build, UWP fails to build in VS.
However, this does not apply to the build in Unity. Only the part involves VS.
Repro:
1. Create a new project with non-ascii character, like 新测试
2. Build UWP with any build settings.
3. Build the final app in VS (or use Build & Run in Unity)
Actual: Final build fails.
Found in: 2019.1.0b4, 2019.2.0a6
Doesn't happen in 2018.3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment