Search Issue Tracker
Not Reproducible
Votes
1
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
Comments (1)
-
SEVEN7HeavenFoxmail
Nov 02, 2025 13:56
I reporoduced it with 6000.0.58f2 and localization package 1.5.8. And I changed the localization package 1.5.7 it works now.
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
This support was added in 1.5.8; however, there was a bug that prevented it from working correctly sometimes. It should now be working in 1.5.9