All Fossify apps crash when selecting Language option in settings on some MIUI-based devices

Checklist

• I can reproduce the bug with the latest versions.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
• This issue contains only one bug.

Affected Android/Custom ROM version

Android 13 / MIUI Global 14.0.4

Affected device model

POCO M3 Pro 5G

How did you install the apps?

F-Droid / IzzyOnDroid

Which apps are affected?

All Fossify Apps

Steps to reproduce the bug

1. Open any Fossify app
2. Go to settings
3. Select Language

Expected behavior

The app shouldn't crash

Actual behavior

The app crashes due to MIUI 14's missing implementation of per-app language settings, despite being based on Android 13.

Screenshots/Screen recordings

No response

Additional information

11-14 22:24:20.027 3257 3257 D AndroidRuntime: Shutting down VM
11-14 22:24:20.028 3257 3257 E AndroidRuntime: FATAL EXCEPTION: main
11-14 22:24:20.028 3257 3257 E AndroidRuntime: Process: com.android.settings, PID: 3257
11-14 22:24:20.028 3257 3257 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.localepicker.AppLocalePickerActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.ActionBar.setDisplayHomeAsUpEnabled(boolean)' on a null object reference
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3839)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3985)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2420)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:211)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.os.Looper.loop(Looper.java:300)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8227)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1028)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.ActionBar.setDisplayHomeAsUpEnabled(boolean)' on a null object reference
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at com.android.settings.localepicker.AppLocalePickerActivity.onCreate(AppLocalePickerActivity.java:82)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:8537)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:8501)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1437)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3820)
11-14 22:24:20.028 3257 3257 E AndroidRuntime: ... 12 more

[naveensingh]

The crash is happening in the MIUI settings app. It can't be fixed in-app.

You may comment on #344 if you'd like it to be reconsidered.

The crash is happening in the MIUI settings app. It can't be fixed in-app.

You may comment on #344 if you'd like it to be reconsidered.

@naveensingh I see, however, I still think this is at least somewhat a bug, as I think the apps should handle the fact that the ACTION_APP_LOCALE_SETTINGS intent doesn't work properly (relevant read: https://xiaomi.eu/community/threads/miui-14-per-app-language-support.69022/) on some ROMs despite isTiramisuPlus() returning true and just hide the Language option or replace it with a notice asking the user to adjust the system language instead.

[naveensingh]

relevant read: xiaomi.eu/community/threads/miui-14-per-app-language-support.69022

I already read that thread before closing this issue :)

I still think this is at least somewhat a bug, as I think the apps should handle the fact that the ACTION_APP_LOCALE_SETTINGS intent doesn't work properly

There is a bug, but it's in the MIUI ROM, and there's no precise way to tell if the system implementation is broken. Xiaomi and other vendors often make changes that break apps (e.g., https://dontkillmyapp.com).

The only way to "fix" this app side is to stop using the system language picker completely, and that's what #344 is about.

relevant read: xiaomi.eu/community/threads/miui-14-per-app-language-support.69022

I already read that thread before closing this issue :)

I still think this is at least somewhat a bug, as I think the apps should handle the fact that the ACTION_APP_LOCALE_SETTINGS intent doesn't work properly

There is a bug, but it's in the MIUI ROM, and there's no precise way to tell if the system implementation is broken. Xiaomi and other vendors often make changes that break apps (e.g., https://dontkillmyapp.com).

The only way to "fix" this app side is to stop using the system language picker completely, and that's what #344 is about.

I've left a comment on that issue, thanks for the information.