1

I've a workspace with multiple packages, and due to the a bug in Xcode I cannot export the app localizations using the Xcode GUI tool, but I need to resort on using a command from terminal

xcodebuild -exportLocalizations -localizationPath . -workspace <path_workspace> -sdk iphoneos -exportLanguage en

One of my packages contains some macros, and I use them from my code without any problem, the code compile

But when I try to export localizations using that command, the build fails due to "compiler plugin not loaded"

So I cannot use Xcode normal exporting because Xcode bug, and cannot export by running a command due to the macro problem

What should I do? It is very discouraging this situation, do you have any suggestion?

I've found a similar problem

2

Hello, did you manage to find a solution for this error?

I am facing the same problem right now, but no success to make it work.

Someone also posted this problem the developer forums: Export Localization Build failing … | Apple Developer Forums

3

nope, I've not found a solution yet

4

Hello,
For the export command, please try using something like -destination 'platform=iOS,name=Any iOS Device’ instead of -sdk iphoneos . That way the macro plugin itself is not restricted to the iOS SDK since it needs to build for a macOS host.

5

Hi

I've already tried a few months ago, but the problem persists!

This is my CLI command

xcodebuild -quiet -exportLocalizations -localizationPath . -workspace Test.xcworkspace -destination 'platform=iOS,name=Any iOS Device' -exportLanguage en -exportLanguage it

But errors occurs, which are related to macOS, as an example

error: 'Actor' is only available in macOS 10.15 or newer
public protocol FilesStorage: Actor {
                                                        ^