Keyboard apps stop working correctly in Voyager comment section. (slrpnk.net)

submitted 1 day ago* (last edited 12 hours ago) by Sunny@slrpnk.net to c/voyagerapp@lemmy.world

13 comments fedilink hide all child comments

Hi there.

I love this app to bits, but recently have stumbled upon a weird issue I cannot seem to resolve. Normally I use the Swift keyboard app from Microsoft but for whatever reason, only when writing a comment to someone, it doesn't work as expected. For instance I cannot use backspace to correct my writing and autocorrect gets disabled.

Ive tried to switch to googles keyboard app and the same thing happens there. This strictly only happens in comments as far as I've noticed, and not when writing this. Also only an issue here in Voyager app, nowhere else.

Has anyone stumbled upon this issue? Is it known?

Update; Created a bug-report on the matter for those interested. https://github.com/aeharding/voyager/issues/1602

top 13 comments

sorted by: hot top controversial new old

[-] QuadratureSurfer@lemmy.world 5 points 21 hours ago

This has been driving me crazy.

I'm using a Pixel with GrapheneOS and the FUTO Keyboard.

Slight workaround for everyone on Android: Click the keyboard selector at the bottom right of your screen and just select the already active keyboard. This will temporarily fix it until you start to type up a different comment.

[-] ada@lemmy.blahaj.zone 5 points 22 hours ago

If you put a leading space at the start of your comment, it will bypass the bug

[-] QuadratureSurfer@lemmy.world 3 points 21 hours ago

hmm doesn't seem to work for me.

Only thing that works is to manually re-select the keyboard among my keyboard selection/input method.

[-] BenM2023@lemmy.world 2 points 19 hours ago* (last edited 19 hours ago)

Sorry to spoil the party but this comment was typed on Microsoft swift key 9.10.44.22, Huawei p20 pro, Voyager 2.17.1, emui 12.0.0

No bother with swipes (don't usually use them), backspace, predictive text - though word suggestions only appear when I stop the swipe.

Eta: Voyager is from Play Store.

[-] vulgarcynic@sh.itjust.works 6 points 1 day ago* (last edited 1 day ago)

same issue here. as you can tell by lack of capitalization.

One thing I've noticed is, if I quick switch to another app and open the keyboard, it resolves the issue in Voyager.

Environment details:

Pixel 7

GrapheneOS

HeliBoard keyboard

Voyager installed from F-Droid

[-] helenslunch@feddit.nl 2 points 22 hours ago

Oh good it's not just me then...

[-] Longmactoppedup@aussie.zone 3 points 1 day ago

identical environment.

if I tap out words, then they will appear as i hit each letter. if i use swipe, then i get no preview of the word, the word just appears after i lift off and touch another key.

very annoying, cant live without gesture/swipe typing.

[-] Monstanner@lemmy.ml 5 points 1 day ago

What device do you have? Do you have Android Vanilla / Android from the manufacturer, or do you have a Custom Rom? Sorry for the stupid question, but you only mentioned two keyboard apps. Have you tried other keyboard apps, for example Fossify Keyboard? Where did you get Lemmy from (Google Play, GitHub, F-Droid)?

[-] Sunny@slrpnk.net 2 points 18 hours ago* (last edited 18 hours ago)

Pixel 7A running GrapheneOS. While there are other keyboard apps there that are Foss, none of them have worked out for me so far. I write in two different languages and don't want to switch between different layouts and such. So instead I have disabled Network access for these keyboard apps.

Based on other comments this seems to be an issue with all(?) keyboard apps.

[-] Monstanner@lemmy.ml 1 points 17 hours ago

Maybe it's because of GraphenOS? I tested it on Android 13 Vanilla (Nokia X1) with Voyager 2.17.1 (F-Droid) and Swiftkey 9.10.44.22 and it works. Are you also using version 2.17.1? Did it work with 2.17.0?

[-] Sunny@slrpnk.net 2 points 16 hours ago

It wasn't an issue before, only started a few weeks ago.

[-] Monstanner@lemmy.ml 2 points 16 hours ago

Ok, that's really strange. The others seem to have the same problem with different solutions, which doesn't work for everyone. That's why I would suggest opening a new issue on GitHub. And post the link below your post so that others can contribute.