You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the app, for the Nutri-score Guide, we use the Crowdin SDK to be able to fetch the latest translations.
We initially used this mechanism to speed up the deployment (and be able to fix potential erros).
Also, we were forced to fork their repo, because of uni_links (incompatible with our Deep links mechanism).
The good news however, is that the latest version of the SDK fixes this.
So now, we have multiple choices:
Re-sync the fork and patch the API url
Create a PR on the official repo, but without any guarantee it will be accepted/ready on time
Ditch the dependency and manually call the API in the app
Hard-code all translations in the current mechanism (but it means losing the auto-update feature)
Also, please bear in mind, that the content is still not validated (and we don't know if it will even be…).
The text was updated successfully, but these errors were encountered:
Hi everyone,
In the app, for the Nutri-score Guide, we use the Crowdin SDK to be able to fetch the latest translations.
We initially used this mechanism to speed up the deployment (and be able to fix potential erros).
However, there is a major issue with the Flutter SDK: it never updates the translation (yes, yes! The main feature of the SDK!).
After digging a little bit, they don't use their API correctly.
Instead of https://distributions.crowdin.net/{distribution_hash}/content/{path_to_file}?timestamp={timestamp_from_manifest}, they use
https://distributions.crowdin.net/{distribution_hash}/content/{path_to_file}
(= thetimestamp
query is missing).Also, we were forced to fork their repo, because of
uni_links
(incompatible with our Deep links mechanism).The good news however, is that the latest version of the SDK fixes this.
So now, we have multiple choices:
Also, please bear in mind, that the content is still not validated (and we don't know if it will even be…).
The text was updated successfully, but these errors were encountered: