Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strings not translated to the preferred language #77

Open
katerinanikolovska-QM opened this issue Feb 4, 2025 · 4 comments
Open

Strings not translated to the preferred language #77

katerinanikolovska-QM opened this issue Feb 4, 2025 · 4 comments

Comments

@katerinanikolovska-QM
Copy link

katerinanikolovska-QM commented Feb 4, 2025

SDK version: 3.10.2
Tested SDK versions: 3.10.2, 3.10.1 and 3.9.0

Some of the strings are not getting translated when switching System language, even though translations are provided.
One thing we noticed is that if we change language, clean app cache and storage, and open the app: the translations are correct.
Second time we open the app, some translations are incorrect.

    private fun configurePhraseOTA() {
        Phrase.setup(
            context = this,
            distribution = DISTRIBUTION_ID,
            environment = ENVIRONMENT_TOKEN
        )

        Phrase.setAppVersion(VersionInformation.versionNameWithDate)
        Phrase.updateTranslations(
            object : TranslationsSyncCallback {
                override fun onSuccess(translationsChanged: Boolean) {
                    L.i { "Update translations successfully. Translations changed: $translationsChanged" }
                }

                override fun onFailure() {
                    L.i { "Update translations did fail. Error is unknown." }
                }
            }
        )
    }

      override fun attachBaseContext(base: Context) =
        super.attachBaseContext(Phrase.wrapContext(base))
}
@katerinanikolovska-QM
Copy link
Author

@hahmed-dev could you assist on this please?

@forelabs
Copy link
Member

forelabs commented Feb 24, 2025

Hi @katerinanikolovska-QM,

I am sorry that we haven't got back to you earlier.
We will take this issue and clarify it's priorization.
Once we knew more, will will come back to you.

@katerinanikolovska-QM
Copy link
Author

@forelabs any update on this?

@forelabs
Copy link
Member

@katerinanikolovska-QM We have discussed this within our last planning and scheduled it for development. The team first needs to be able to reproduce the issue, so I can not give an ETA yet unfortunatly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants