Update: There’s any existing bug report:

https://github.com/aeharding/voyager/issues/1602

Original post:

Fellow voyagers,

For several weeks now I’ve been having Android keyboard issues when using the Voyager app and I’m just trying to figure out if it’s a me thing, or a voyager thing.

I use Gboard as my default keyboard, and I’ve noticed that when creating a post, or replying to a post by selecting a reply icon, the keyboard isn’t raised into focus automatically. Once I manually select the input field, a completely crippled Gboard keyboard pops up. The keyboard defaults to lower case lettering, 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 just back out of the input method popup without selecting anything, a proper working version of Gboard now appears, 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. The issue only seems to appear 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.

  • Voyager v2.18.2 (app.vger.voyager)
  • Gboard v14.6.03.665297282-release-arm64-v8a (com.google.android.inputmethod.latin)

Any thoughts?

Edit: I found the related post here from last month. It sounds like it might be related to GrapheneOS, but it’s strange that it only happens within Voyager. I’m wondering if Voyager is triggering input in a way that is contrary to GOS’ hardened security.

  • QuadratureSurfer@lemmy.worldEnglish
    1·
    1 month ago

    i’m also experiencing this issue.

    One way to narrow down this issue would be to downgrade voyager to an older version before this started happening and figure out at which version it was introduced.

    If downgrading doesn’t fix it, then it’s likely a GrapheneOS update that caused it… But considering I haven’t seen this happen on any other apps I’m leaning towards this being a Voyager issue.

    • thayerwOPEnglish
      2·
      1 month ago

      It seems to be isolated to GrapheneOS users, but I do think it’s something that Voyager is doing since it isn’t happening anywhere else. Either there’s an issue with the reply function, or the way it’s being called in certain circumstances. Anecdotally, I recall that it started after a GOS update, and Voyager hadn’t been updated at the time. Maybe something changed in GOS’ Vanadium/WebView which has essentially broken Voyager.