Helium314

Can't reproduce, it works normally for me. Was it always like that with the new settings?

I meant with the _new_ settings, i.e. starting with 3.0. > Happy to fix this, but need guidance. My only idea so far is investigating what's happening when you change...

> Apparently, [a known bug](https://issuetracker.google.com/issues/320452319). Unfortunately that's only that the bug exists, no further information, especially no reply to "_Could you provide what your onValueChange is doing?_" (which is a...

There was no update on the linked bug report... let's hope it really was a compose issue that's fixed now.

I just tried, and works same as when installing the normal version. Android 10 / LinageOS 17, Samsung Galaxy A3 2017

Did you find any way of reproducing this? The `RichInputMethodManager` makes it look like the app was not registered as a keyboard in the system, but for not showing the...

The crash happens because `RichInputMethodManager` doesn't find any `InputMethodInfo` belonging to the Heliboard debug package. So a start would be logging which IME package names are actually found in `mImm.getInputMethodList()`,...

I added information about found IMEs to the exception message, so we have some more data when it happens again.

Do you have a way to reproduce this? For me it works normally. Are the languages also listed twice in _Languages & Layouts_?

> Possibly an artifact of settings restore in some scenario? I don't think settings restore would be an issue here. There was an issue where duplicate subtypes were added when...