Thank you for bringing this synchronization issue to our attention. The problem you are seeing—the “404 page” link and the lack of translation updates for the app..values/strings.xml (release/4.0) file—is directly caused by an error in the source file itself. When our system attempts to sync with your GitHub repository, it must first successfully parse the XML file to identify all the strings that need to be localized.
The file is failing this critical parsing step because of one specific string, <string name="smb_instructions">, which contains unescaped characters, primarily apostrophes and double quotes, inside a CDATA block. Although the CDATA block is intended to allow for literal character data, the Transifex parser still applies strict checks to ensure the content is compatible with Android’s string standards. The presence of these characters, such as literal double quotes (") and backslash-escaped apostrophes (\'), is causing the parser to crash or reject the entire file. In the GitHub integration wizard, you can see the details about this issue:
When the parsing fails, the system cannot read the content of the strings.xml file. This inability to process the file means the synchronization effectively fails. In some cases, this failure to create a valid resource link within our platform manifests to the user as the “404 Not Found” error you are seeing, even though the file technically exists in GitHub. To fix this synchronization issue and restore your translation updates, you must commit a corrected version of the strings.xml file to your release/4.0 branch. The fix involves replacing those problematic characters with their proper HTML entities: replace the double quotes (") with " and replace the apostrophes (') with ' (or ') within the affected string. Once this corrected XML is in your repository, please trigger a new sync, and the integration should be fully restored.
Please let us know once you have pushed the fix to the source file, and we can confirm the resource link is working again.
