I've noticed that genstrings does not include String(localized:) in the .strings exports. I created a feedback but was wondering if anyone had any work arounds. I know there is Export Localizations, but that creates a .xliff which itself has other issues like changing \n and & to html encoded characters. This then also seems to mess up directory structure if you import them back as it puts them into the root folder and not into my localization folders. This would be fine if I wanted to do everything manually but I'm looking to automate this during the CI phase.

We are using a workspace file and have noticed that when we run fastlane commands that utilize xcodebuild command line arguments to run the export localization command from commandline, and it seems that it uses the xcodeproj package.resolved instead of the workspace package.resolved. This is causing issues as the xcodeproj package resolved will not update at all so is on old version of dependencies that cause xcodebuild commands to fail. Why is there multiple package.resolved files and why does the xcodeproj not stay updated with what is in the workspace resolved file? Why won't the xcodeproj resolved file update when I'm opening the xcodeproj file and selecting specific dependencies and telling it to update the package.