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
Install and enable another keyboard (I've tested this with my own https://codeberg.org/natkr/flickboard but the mechanism triggers the same against HeliBoard itself from other apps)
Install, enable, and select HeliBoard (order is important, HeliBoard must be installed after the other keyboard)
Open a text field in some app
Long-hold space to open HeliBoard's keyboard picker
Note that HeliBoard and the system keyboard(s) (probably GBoard) are both listed, but the other third-party keyboard (FlickBoard) is not
Tap the system-native keyboard picker button
Note that all enabled keyboards are listed
Expected behavior
All enabled keyboards should be listed.
This seems to be due to an Android bug with how package-privacy works. The other keyboards list fine if I add a query for <action android:name="*"/>, but obviously it's weird that the current android.view.InputMethod doesn't work. I agree that what you do matches what I'd expect from the documentation.
Screenshots
ONLY add screenshots when they add real value.
If you add screenshots, reduce the size or use thumbnails to keep the issue nicely readable.
The other keyboards list fine if I add a query for
Where do you add this?
Another option would be to just use the standard keyboard picker
The problem with the standard picker is that it only shows subtypes that are registered in the system. Up to Android 13 or 14 it was necessary to use a system screen for registering the subtype, and this screen is simply broken on some devices (#12).
So the custom subtype picker is the only choice if people want more than default enabled subtypes.
It could be changed for new Android versions, but I didn't look up details.
Describe the bug
To Reproduce
Expected behavior
All enabled keyboards should be listed.
This seems to be due to an Android bug with how package-privacy works. The other keyboards list fine if I add a query for
<action android:name="*"/>
, but obviously it's weird that the currentandroid.view.InputMethod
doesn't work. I agree that what you do matches what I'd expect from the documentation.Another option would be to just use the standard keyboard picker (https://developer.android.com/reference/kotlin/android/view/inputmethod/InputMethodManager?hl=en#showinputmethodpicker) instead.
Screenshots
ONLY add screenshots when they add real value.
If you add screenshots, reduce the size or use thumbnails to keep the issue nicely readable.
App version
2.3 and main (7c77f4d)
Device:
Android 14 emulator, Android 15 emulator (The official Play API ROMs)
The text was updated successfully, but these errors were encountered: