@wes-nz I just tested these examples and the upload result is the same whether I use the UI or the CLI.

@andrii-bodnar weird, are you on macOS? I just created a fresh project, upload the example strings.xml, then linked the project with crowdin init, followed by crowdin file upload ./Localizable.strings -b main I end up with two translations for the same key.

Let me know if you have any questions.

@wes-nz yes, I'm on macOS. Could you please attach the file?

XML+Strings.zip

@wes-nz thanks a lot! I was able to reproduce the problem, it's an API side issue. Already reported to the team.

Hi @jimmysafe, thanks for the feedback, it's very valuable for us!

This is expected behavior in file-based projects. The thing here is that pushing strings from Figma uses different API (Add String) and it modifies the file in Crowdin by adding these strings. The developers may not have these changes locally and when they push the file to the Crowdin project it overwrites the file state there as it updates the entire file.

I would recommend using string-based projects for your workflow. By the way, the --no-cleanup-mode only works for this type of project.

In string-based projects, the focus is on managing translatable content as individual strings rather than source files. In this project type, after uploading source files, Crowdin parses them into source strings. Unlike file-based projects, source files aren’t stored, and the emphasis is on managing the content at the string level. This approach is beneficial when dealing with projects that involve continuous content updates, dynamic content, or where a string-oriented structure is preferred.

In this case, you'll need to use Bundles to download the translations from Crowdin. As you use the JSON file format, you'll need to use the JSON String Exporter in the Bundle configuration.