We're also experiencing this at Savage. We're having to swich back to Xcode 9.2 in order to complete our translations for Procreate.
Unfortunately, because of time pressures, we may not be able to create a sample project for bug reporting - our project is complicated, and uses a number of tables (often in Modules inside the project). Figuring out a minimum test case for what's busted isn't in our power right now.
I can tell you that we're getting some exports of NSLocalizedStringFromTable(), but they're not exporting in the XLIFF to correct location. So, for example, let's say we had an extant table strings file called BlendModes.strings that lived in Resources/Localization (and subfolders therein for each language, of course), we would expect Xcode to export these strings with a file tag of something starting with
<file original="Resources/Localization/en.lproj/BlendModes.strings"
Instead, we get
<file original="Procreate/Support/en.lproj/BlendModes.strings"
which is incorrect, and surprising, because that's not where they currently live, and it's not where Xcode has previously exported them to.
All this leads to the translation team going nuts, and a heap of new files created in the wrong spots with the wrong content when we import the completed XLIFF translations. I had to go back to the original export to find out what was wrong.
Because I can't get comparisons of these files, it's difficult to tell if we're missing any translations or not, but a manual eyeballing of the files suggests that we are.
I'll try to get a bug report done, but I don't hold out any hope, what with the sample project requirement.
Best wishes, always,
Dave Williams @ Savage
