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
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
- Outdated documentation page is linked when clicking on the Help icon for "Virtual Texturing" Module in Profiler Window
- [Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
- Bounding Box Size of Light Probe Proxy Volume and Settings.Max Interaction Distance of Panel Input Configuration Components cannot be added as Properties in Animation window
Add comment