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

submitted 2 months ago* (last edited 2 months ago) by Sunny@slrpnk.net to c/voyagerapp@lemmy.world

12 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

you are viewing a single comment's thread
view the rest of the comments

[-] Monstanner@lemmy.ml 5 points 2 months 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 2 months ago* (last edited 2 months 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 2 months 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 2 months ago

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

[-] Monstanner@lemmy.ml 2 points 2 months 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.