Locale: onConfigurationChanged not called

Question

I want my language to change dynamically and I am trying to use onConfigurationChanged but it is not being called. I have a MainActivity that creates my action bar and viewp

Answer 1

You have to define android:configChanges="layoutDirection|locale" in order for onConfigurationChanged() to be called.

Answer 2

Ok, I've looked into this a bit.

I'm not sure, why the onConfigurationChanged method isn't called, so I'm hoping someone can enlighten us on this part.

In my search I stumbled upon this tutorial , which actually change the Locale, by changing the configuration.

Your code looks a lot like this tutorial actually ;-)

Anyways, the important thing about the tutorial and the code is this method:

private void updateTexts() {
    txt_hello.setText(R.string.hello_world);
    btn_en.setText(R.string.btn_en);
    btn_ru.setText(R.string.btn_ru);
    btn_fr.setText(R.string.btn_fr);
    btn_de.setText(R.string.btn_de);
}

This is where the "magic" happens; after you've changed your locale you will need to reload your resources and since you told Android you want to handle some configurations on your own you need to specifically reload all your text, by setting your UI items texts again.

When this is done, the app will load the strings from the specific locales folder.

The answer to why Android behaves this way, can be found in the official documentation for the Activity saying:

[...]

This is done because any application resource, including layout files, can change based on any configuration value. Thus the only safe way to handle a configuration change is to re-retrieve all resources, including layouts, drawables, and strings. Because activities must already know how to save their state and re-create themselves from that state, this is a convenient way to have an activity restart itself with a new configuration.

The guy writing the tutorial was kind enough to add the whole tutorial project as a download, so I recommend you go check it out to see how it's working, because it is working ;-) You can outcomment the onConfigurationChanged method, as it doesn't seem to be doing anything.

Hope this helps.