Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
1
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b2
2022.1
Issue ID
1352216
Regression
No
[Xcode] Bundle Identifier parts in Xcode project missing if they contain chinese symbols
Steps to reproduce:
1. Create a new project or open an existing one
2. Use chinese characters for Product Name or Company Name (Edit -> Project Settings -> Player)
3. In Build Settings check "Create Xcode Project" and build for standalone
4. Open the generated Xcode project
5. Notice the Build Identifier (In General tab)
Expected results: Build Identifier consists of three parts, like "com.<company name>.<product name>"
Actual results: Build Identifier has empty Company Name or Product Name parts if they contain chinese symbols, like "com.<company name>." or "com..<product name>" for example
Reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0b2, 2022.1.0a3
Notes:
- If having trouble opening the Xcode project due to Case 1347730 (https://issuetracker.unity3d.com/product/unity/issues/guid/1347730/) it's possible to build for iOS as that generates an Xcode project as well which can be opened without an issue
- Tested with Pinyin-Simplified, Zhuyin-Traditional
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 2021.2):
Fixed in 2021.2.17f1. Even though those characters still can't be used, user facing validation is provided