We added a new string to one of the strings.xml files in our project and crowdin started treating all the strings below it as new strings. It seems like crowdin is not parsing the strings file correctly as I don’t see keys being populated. Is there any way to fix this without losing translations? We’re currently using github for integration.
We have other strings.xml files in the project and their keys get populated correctly
Hi @tjaved
Depending on what XML you have, it can be key-based or non-key-based
If it’s non-key based, it’s expected that each new string somewhere in the middle of the file, technically, makes the remaining part “brand new”.
This happens if the file structure changes, affecting the internal identifiers of the strings.
To address this without losing translations, you can restore them from the Translation Memory using the Pre-translate feature
Or, consider using Duplicates (project settings → import), with it, you can upload a new file, and translation will migrate from old one to it (with all authorship, history, etc).
