Xcode 15 migration to string catalogs failed

Question

Created Oct ’23

Replies 8

Boosts 0

Views 1.8k

Participants 3

I tried to migrate to the new localized string catalogs. But after this I can't build the app anymore. The error message stated something about an "old" .string file... but I checked all directories and there are no old .string files...

Anybody a hint how to go further?

Bildschirmfoto 2023-10-02 um 09.54.52.png

And this is how the directories look after migration ...

Bildschirmfoto 2023-10-03 um 22.29.02.png

Answered by DTS Engineer in 782515022

Your first screenshot shows the following errors:

Localizable.xcstrings cannot co-exist with other strings or .stringsdict tables with the same name.

LocalizableDic.xcstrings cannot co-exist with other strings or stringsdict tables with the same name.

InfoPlist.xcstrings cannot co-exist with other strings or stringsdict tables with the same name.

These errors are typically triggered because the .strings or .stringsdict files exist in the Base.lproj folder in your project.

Base.lproj is for something like a storyboard, which you have a base resource in Base.lproj and each locale (including English) has a .lproj folder with a .strings file that overlays the translations on top of the same base resource. It should not contain any .strings or .stringsdict files.

Xcode doesn't provide a good way to remove the files from Base.lproj, and so I'd consider fixing the issue with the following steps:

Back up your project.
Remove the .strings or .stringsdict files from your project. In this case, they are Localizable.strings, Localizable.stringsdict, and InfoPlist.strings, as mentioned in the error message. Note that you need to trash the files, and not just remove the reference from your project.
Add the files back from your backup project. To do so, place your project and backup project side by side, and then drag and drop the files.
Localize the files for the languages you support. To localize a file, select it in Xcode's Project Navigator, click the Localize button in Xcode's File Inspector, then pick the languages. In this process, Xcode creates a .lproj folder for each language (if not yet), and copy the file to the folder. Replace the file in each .lproj folder with the localized version from your backup. As a result, your project has the localized files in each .lproj folder, but not in Base.lproj.

Now that your project is correctly configured, right-click a .strings or .stringsdict file in Xcode's Project Navigator to show the contextual menu, then select Migrate to String Catalog… menu. Xcode should do the migration for you.

Boost

Answer 1

Developer Tools Engineer OP

Apple

Oct ’23

Can you also share how your file structure looked before the migration? I think it would be especially valuable to see what files were in your en.lproj folder.

0

Answer 2

HardyGermany OP

Oct ’23

Hello, thanks for the reply.. here is the situation shortly before the migration

Bildschirmfoto 2023-10-03 um 19.07.56.png

0

Answer 3

HardyGermany OP

Oct ’23

Maybe also useful...

project file AFTER migration Bildschirmfoto 2023-10-04 um 09.11.40.png

plist file AFTER migration Bildschirmfoto 2023-10-04 um 09.15.02.png

0

Answer 4

HardyGermany OP

Oct ’23

And the same files, after a rollback of the migration...

Bildschirmfoto 2023-10-04 um 09.47.49.png

Bildschirmfoto 2023-10-04 um 09.48.31.png

0

Answer 5

HardyGermany OP

Oct ’23

... and the changes made by Xcode 15 during migration in the .xcodeproj

Bildschirmfoto 2023-10-04 um 09.54.20 (1).jpeg

Bildschirmfoto 2023-10-04 um 09.54.48 (1).jpeg

Bildschirmfoto 2023-10-04 um 09.55.38 (1).jpeg

0

Answer 6

HardyGermany OP

Oct ’23

And this are the changes on file level .. the changes on the .plist files are just increased build numbers

Bildschirmfoto 2023-10-04 um 10.14.51.png

0

Answer 7

HardyGermany OP

Oct ’23

Hi, one told me I have to get rid of the "base.*" files .. is there an easy way to eliminate them?

0

Answer 8

DTS Engineer OP

Apple

Mar ’24

Accepted Answer

Your first screenshot shows the following errors:

Localizable.xcstrings cannot co-exist with other strings or .stringsdict tables with the same name.

LocalizableDic.xcstrings cannot co-exist with other strings or stringsdict tables with the same name.

InfoPlist.xcstrings cannot co-exist with other strings or stringsdict tables with the same name.

These errors are typically triggered because the .strings or .stringsdict files exist in the Base.lproj folder in your project.

Base.lproj is for something like a storyboard, which you have a base resource in Base.lproj and each locale (including English) has a .lproj folder with a .strings file that overlays the translations on top of the same base resource. It should not contain any .strings or .stringsdict files.

Xcode doesn't provide a good way to remove the files from Base.lproj, and so I'd consider fixing the issue with the following steps:

Back up your project.
Remove the .strings or .stringsdict files from your project. In this case, they are Localizable.strings, Localizable.stringsdict, and InfoPlist.strings, as mentioned in the error message. Note that you need to trash the files, and not just remove the reference from your project.
Add the files back from your backup project. To do so, place your project and backup project side by side, and then drag and drop the files.
Localize the files for the languages you support. To localize a file, select it in Xcode's Project Navigator, click the Localize button in Xcode's File Inspector, then pick the languages. In this process, Xcode creates a .lproj folder for each language (if not yet), and copy the file to the folder. Replace the file in each .lproj folder with the localized version from your backup. As a result, your project has the localized files in each .lproj folder, but not in Base.lproj.

Now that your project is correctly configured, right-click a .strings or .stringsdict file in Xcode's Project Navigator to show the contextual menu, then select Migrate to String Catalog… menu. Xcode should do the migration for you.

1