Keyboard features missing when writing a comment

[subcidr]

Describe the bug
When writing a comment on mobile-app, certain features of the keyboard app(no matter which keyboard app) stops working. Such as: autocorrect, spellcheck and backspace(to delete letters). The functions seem to vary on what works and what doesn't work. For example, backspace does not work on Swift keyboard app (by Microsoft), whilst it does work on Gboard (Googles keyboard app). However, autocorrect seem to not work on either of them.

To Reproduce
Steps to reproduce the behaviour:

1. Go to any post
2. Click on comment button
3. Start typing
4. Attempt to use backspace to delete words.
5. See error

Expected behaviour
Expect the autocorrect and all other functions of the keyboard app in use to function with all of its functionality as it does elsewhere.

Video recording of this happening
https://github.com/user-attachments/assets/984b87fa-6508-44c1-b1ab-5cc985a5e569

Smartphone Information):

• Device: Pixel 7a
• OS: GrapheneOS:latest
• Version 2.17.1

Additional context
Voyager app installed via Fdroid.

This bug was also discussed over at Lemmy, where multiple people mention that they have the same issue, also with other keyboard apps. The discussion can be viewed here: https://slrpnk.net/post/13461230

[Brendan-D15]

Same thing with the Pixel 7 Pro running GrapheneOS.

Using the FUTO keyboard, but autocorrect/swipe to text/other features don't work when typing up comments in Voyager. This only started recently.

Workaround: On the keyboard, tap the "Keyboard select" button at the bottom right, then select the already active keyboard and the features will start working again.

Other apps don't have a problem like this. This bug only started happening recently with Voyager.

[subcidr]

Just wanted to chip-in and mention that this is still an active bug.

[thayerw]

I'm also experiencing this bug and just posted the details in Lemmy World's voyagerapp community:

• GrapheneOS (Pixel 7 build 2024101200)
• Vanadium/System Webview v129.0.6668.100.0
• Gboard v14.6.03.665297282-release-arm64-v8a (com.google.android.inputmethod.latin)
• Voyager v2.18.2 (app.vger.voyager)

For several weeks now, I’ve experienced Android keyboard issues only when using the Voyager app.

I use Gboard as my default keyboard, and whenever creating a post, or replying to a post by selecting a Reply icon, the keyboard isn’t raised into focus automatically. Once I select the input field, a crippled Gboard keyboard appears. It defaults to lower case lettering (not sentence casing), has no spell check or predictive text, and doesn’t support any gestures, such as swipe backspace.

If I then bring up the input method selection menu, it shows that Gboard is already selected. If I select Gboard again, or even exit the popup without making any selection, a proper working version of Gboard will appear, with predictive text, swipe gestures, etc.

If I reply to a comment by swiping left, the keyboard is immediately brought into focus and works as expected. Same goes for editing a comment from the 3-dot menu. The issue only appears when selecting a Reply icon, initiating a reply from the 3-dot menu, or when creating a new post.

I can consistently repeat this every time, and it is only happening for me within the Voyager app. Obviously, it's somehow related to GrapheneOS and/or its Vanadium/Webview implementation, but it's a bit unusual that no other apps seem to be affected, and even Voyager is affected only with certain criteria.

[aeharding]

Hi there!

I cannot reproduce this issue with Android 14 on a Pixel 7a. Autocorrect and auto-capitalize work fine.

It sounds like this is a bug with GrapheneOS keyboard logic. Could you open an issue there?

Additionally, if it started happening recently, try downgrading GrapheneOS and/or Voyager to see when the issue first started happening. That could help pinpoint the problem.

[aeharding]

Is it possible this is related? GrapheneOS/os-issue-tracker#4052

[subcidr]

Is it possible this is related? GrapheneOS/os-issue-tracker#4052

Very possible that this is a GrapheneOS issue as you mention. Although I've not experienced this issue in any other app yet. I'll see if I can recreate it other places. Thanks for linking the issue to their GH, hopefully they could have a look into it too 👍