Search Issue Tracker
Active
Under Consideration for 1.5.X
Votes
0
Found in [Package]
1.5.7
Issue ID
LOC-1249
Regression
No
Localization files are not added to Xcode project when building for macOS platform
Reproduction steps:
1. Open the attached “MacOSAppName” project
2. In the Build Profiles window (File > Build Profiles), select the “New iOS Profile” profile
3. Build the project and open the built Xcode project
4. In Xcode, select “Unity-iPhone” project and select Info tab
5. In the Info tab, observe that there are Localizations added to the project
6 In the Unity Editor’s Build Profiles window, select the “New macOS Profile” profile
7. Build the project and open the built Xcode project
8. In Xcode, select “macOSBuild” project and select Info tab
9. Observe the Localizations
Expected result: The project contains the same Localizations from step 5
Actual result: The project does not contain any Localizations
Reproducible with: 1.5.5 (6000.0.52f1), 1.5.7 (6000.0.56f1, 6000.2.2f1, 6000.3.0a6)
Reproducible on: macOS Sequoia 15.6.1 (M1 Max)
Not reproducible on: No other environments tested
Notes:
- When building “new macOS Profile”, make sure that “Create Xcode Project” settings is enabled
- This issue results in the App name not being translated correctly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment