Search Issue Tracker
Fixed in 2022.3.16f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 7000.0.0a1, future release
Votes
1
Found in
2022.2.11f1
2023.1.0b7
2023.2.0a5
2023.3.0a3
Issue ID
UUM-30326
Regression
Yes
[iOS] "Unable to Install" Error is thrown when attempting to install an archived App with certain symbols in the Product Name
How to reproduce:
1. Open the attached Project "JPName"
2. Build the project for iOS and open the Xcode Project
3. Archive the Xcode Project
4. Attempt to install the created .ipa to an iOS device
Expected result: the installation succeeds
Actual result: "Unable to install" error is thrown
Reproducible with: 2022.1.0a12, 2022.2.11f1, 2023.1.0b7, 2023.2.0a5
Not reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.1.0a11
Reproduced with:
- iPhone 7 (iOS 12.3.1)
- iPhone 121 mini (iOS 14.1)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2023.3):
Fix Product Name with non-latin characters to be able to install .ipa to the device