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
Describe the bug
Single-character non-ASCII TEXT_BLOCK input crashes the service.
To Reproduce
Steps to reproduce the behavior: On Android 14 (with that new-fangled proxy thing) use TEXT_BLOCK with a single non-ASCII character. mappings_generated.json. Two characters work fine because they take a different code path.
Expected behavior
Single character is inputted fine.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Device: Samsung S10e
Android version: Android 14 (LineageOS)
Also observed on Samsung Tab S8 Ultra / Stock Android 14
Additional context
IMO, when keyCharacterMap.getEvents(chars) in inputTextRelayService returns null, there should be a fallback.
The text was updated successfully, but these errors were encountered:
Developer TODO (don't remove)
Discord message link/email recipient
Describe the bug
Single-character non-ASCII TEXT_BLOCK input crashes the service.
To Reproduce
Steps to reproduce the behavior: On Android 14 (with that new-fangled proxy thing) use TEXT_BLOCK with a single non-ASCII character.
mappings_generated.json. Two characters work fine because they take a different code path.
Expected behavior
Single character is inputted fine.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
IMO, when
keyCharacterMap.getEvents(chars)
ininputTextRelayService
returns null, there should be a fallback.The text was updated successfully, but these errors were encountered: