Keyboard disappears when moving cursor in certain app

[JamieJamersonJr]

Describe the bug App crashes when trying to move cursor past text in Voyager for Lemmy

To Reproduce

1. Create a post on Voyager for Lemmy (only app i've encountered this bug in so far)
2. Select the title input
3. Add any character (won't happen without at least one character)
4. Place the cursor at the end of the string
5. Move the cursor to the right with either the toolbar right key or the space trackpad

Expected behavior Cursor doesn't move and app doesn't crash

Screenshots Not applicable

App version 1.3-beta1

Device:

• Model: [e.g. OnePlus 9 LE2113]
• OS: [e.g. Android 14 Manufacturer ROM]

Additional context i will attach the crash logs here, app detected two of them despite having crashed multiple times while i was testing this crash_reports.zip crash_reports2.zip
This is a log i managed to get, crash occurs after the second RIGHT command BUGREPORT_HeliBoard_log_1713530759852.txt

[Helium314]

According to the first crash report, Voyager returns null on getTextAfterCursor, which means that the app either intentionally returns null (it really should not), cancels the input connection, or does not respond. Anyway, HeliBoard should not crash in that case.

Could you upload another log for the right arrow press? crash_reports2.zip is broken, and the log is only after the crash, so it does not help here.

[JamieJamersonJr]

According to the first crash report, Voyager returns null on getTextAfterCursor, which means that the app either intentionally returns null (it really should not), cancels the input connection, or does not respond. Anyway, HeliBoard should not crash in that case.

Could you upload another log for the right arrow press? crash_reports2.zip is broken, and the log is only after the crash, so it does not help here.

i can try HeliBoard_log_1713556667494.txt can't upload an actual crash log because the app doesn't always prompt to save one, it seems that crash logs are only generated when the app "officially" crashes and does the "heliboard has crashed" popup, which it only does some of the times for some reason.

[Helium314]

Actually it looks like there is no app crash. It looks like at 21:56:03 there is an selection update, and then nothing happens until you enter a new input field at 21:57:29. If HeliBoard had crashed, then the "normal" log before the crash would be lost (unless it's saved in a crash log, but that wasn't the case).

If Voyager actually closes the input connection however, then the keyboard should go away without a crash. I'll add a log entry for this.

[Helium314]

The logging was already added in 1.3. Could you provide a new log with HeliBoard 1.3?