Q: Localazy CLI is not working on macOS Big Sur

After upgrading to macOS Big Sur, there’s a chance you may run into an issue with executing Localazy CLI. This is usually caused by incorrect configuration of <code>brew</code> package manager. (Note that this doesn’t apply to binaries downloaded directly from our website, they should be working fine.) The symptoms look like this, the process is killed without any further output. <img src="https://directus.localazy.com/_/assets/Screenshot_cli_inner_3.png" alt=""> To resolve the issue, go to App Store -&gt; Updates and make sure, there’s no update available for Xcode. If yes, click “UPDATE” and wait for it to finish. <img src="https://directus.localazy.com/_/assets/Screenshot_cli_inner_2.png" alt=""> After the update, try to run <code>brew doctor</code> and read the output carefully. There could be a warning about outdated CLT and suggested fix. <img src="https://directus.localazy.com/_/assets/Screenshot_cli_inner_1.png" alt=""> Let’s run the commands in the specified order and confirm all dialogues that might appear. <ul> <li><code>softwareupdate --all --install --force</code>,</li> <li><code>sudo rm -rf /Library/Developer/CommandLineTools</code></li> <li><code>sudo xcode-select --install</code></li> </ul> Upgrade Localazy CLI to the latest version by running <code>brew upgrade localazy/tools</code> And that’s all! You can now verify that Localazy CLI is working again with the <code>localazy -h</code> command.

Q: Why some translations cannot be exported correctly into XML?

You might encounter a message such as: <pre><code class="hljs">Phrases 1dbb1f96d2b25755ec8ce882766596c150efecc7 and aaa97c82019600566b80fe5645341518337208ae in Czech cannot be exported correctly - malformed XML. Skipping.</code></pre>This means that the translation cannot be exported into XML because the translator probably didn’t insert tags correctly, didn’t close them etc. Please verify these translations and try again.

Question 1

Localazy CLI is not working on macOS Big Sur

Accepted Answer

After upgrading to macOS Big Sur, there’s a chance you may run into an issue with executing Localazy CLI. This is usually caused by incorrect configuration of brew package manager. (Note that this doesn’t apply to binaries downloaded directly from our website, they should be working fine.)

The symptoms look like this, the process is killed without any further output.

To resolve the issue, go to App Store -> Updates and make sure, there’s no update available for Xcode. If yes, click “UPDATE” and wait for it to finish.

After the update, try to run brew doctor and read the output carefully. There could be a warning about outdated CLT and suggested fix.

Let’s run the commands in the specified order and confirm all dialogues that might appear.

softwareupdate --all --install --force,
sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --install

Upgrade Localazy CLI to the latest version by running brew upgrade localazy/tools

And that’s all! You can now verify that Localazy CLI is working again with the localazy -h command.

Question 2

Why some translations cannot be exported correctly into XML?

Accepted Answer

You might encounter a message such as:

Phrases 1dbb1f96d2b25755ec8ce882766596c150efecc7 and aaa97c82019600566b80fe5645341518337208ae in Czech cannot be exported correctly - malformed XML. Skipping.

This means that the translation cannot be exported into XML because the translator probably didn’t insert tags correctly, didn’t close them etc.

Please verify these translations and try again.

Question 3

Why are recent changes or new translations not downloaded?

Accepted Answer

When you encounter this problem, it most likely means that you are running over your account’s source key limit. Please visit the Marketplace and upgrade your account or increase your source key limit from there.

CLI FAQ