How to share translations between iOS and Android platforms

General Questions
4

Hello @iosif.moldovan

    • This is correct. “Hide Duplicates” feature specifically works by identifying identical source strings (and potentially keys, depending on settings) that are present in multiple uploaded source files within the same project. If a string (and its key, if strict mode is used) exists only in your iOS file and not in any Android file, Crowdin doesn’t consider it a “duplicate”, it’s just an original IOS string. You can’t pull an iOS-specific key to Android (or vice-versa) unless you’ve explicitly told Crowdin to create a new string in the target platform’s file during export, or if that string eventually gets added to the Android source files. Crowdin primarily translates content from your source files and exports to their respective formats. It doesn’t automatically “merge” or “create” new keys in a target platform’s file if they don’t exist in that platform’s original source file.

  2. This indicates a setting mismatch. When “Hide (regular detection)” (or “strict”) for duplicate strings is correctly applied, identical strings should indeed appear only once in the editor for translators. If they’re appearing twice, it suggests that Crowdin isn’t identifying them as duplicates for some reason (different context/labels, for example). More about duplicate settings can be found here: Import Settings | Crowdin Docs

  3. That’s also the default behaviour of the master-duplicate connection. All string-related changes should be applied to the master string if you want to see them reflected in duplicates as well. If the changes are applied to the duplicates, this connection will be indeed broken, as the duplicated string become the “new master”.

  4. That pop-up message appears when you’re trying to save the already existing translation which was saved previously. It is discussed in more details here: 'An identical translation of this string...' message and how to fix it