Strings not syncing after app update, could it be resource handling?

General Questions
,
1

Hi everyone, hope you’re all doing great!

I’m working on a localization project, and after pushing a new build with updated strings, some of the updated texts aren’t appearing in the app at all, even though crowdin shows they’ve been approved and downloaded. We’ve checked the integration and it looks right, but the old strings are still showing up on some devices.

It reminded me of a discussion I saw about how large app packages or cached data from apps can affect how updates actually take effect on devices, and it got me wondering whether this mismatch could be due to device cache, resource bundling, or delayed asset refresh.

Has anyone experienced text updates not showing up even after successful sync? Do you think it’s more likely a problem with local caching on devices, build-time resource bundling, or maybe the distribution process not invalidating older assets? Any tips on debugging this kind of issue before assuming it’s a crowdin integration problem would be really helpful!

Thanks in advance!

2

Hi @adri992,

If I understand the case correctly, you updated the translations in Crowdin, then released a distribution (possibly using OTA) or exported the translation via another integration, but the translations did not update in your app. In this situation, it can indeed be related to caching or delays in over-the-air delivery

You can check the distribution to verify whether the translations are present there

If you continue to face the issue, please share more details with us (the project, which integration you’re using, and links to examples of strings whose translations are not being exported), so we can check this from our side