Android keyboard (Gboard) adds backspace to some keystrokes when editing a file

[shaneknysh]

Steps to reproduce

1. Open a text file (not in Android) from your nextcloud
2. On a new line type "abcd1234AbcdABCD" (use shift and capslock)
3. Open the same file in Android
4. On a new line type "abcd1234AbcdABCD" (use shift and shiftlock)

As you type you can see the backspace happening. The backspace is inserted first. I have noticed shift, new line/enter inserts one backspace and shiftlock inserts two - you have to hit shift twice to activate shiftlock.

Expected behaviour

2 new lines are in the file abcd1234AbcdABCD abcd1234AbcdABCD

Actual behaviour

2 new lines are added abcd1234AbcdABCD abcd123AbABCD

Server configuration

Ubuntu 16 nginx Postgres PHP 7 Nextcloud 13 Installed from binaries --Will update versions

List of activated apps: Will update (typing on Android and don't have access to command line)

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or

Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Client configuration

Chrome 66.0.3359.158 Android 7 Android 8.1

[mbattigaglia]

I have the same issue. The cause may be a bug in ace editor (which should have been solved in latest releases): https://github.com/ajaxorg/ace/issues/2038

[01tot10]

I encountered the problem of Android keyboard deleting all text from a text-file when trying to do some edits on mobile. This happened to me on two occasions on consecutive days, which made me come to the conclusion that editing text files in Android is basically unusable.

Is this the correct bug to be following? I see that the related issue [*] is pointing here. Also, in the related issue, it is said that we are waiting for an upstream fix, but since this issue is already opened 2018, it would seem like this might still take a while? I'm sorry about my noobiness / stupid questions!

[*] https://github.com/nextcloud/android/issues/8945

[shaneknysh]

It appears the upstream bug was closed as "appears to be fixed" in July 2018.

Having this issue - and the related Nextcloud issue - closed as "waiting for upstream" while referencing a closed upstream bug is a dead end. This seems to indicate Nextcloud considers this upstream and therefore not their problem, while upstream considers this already fixed- and no one is even trying to change anything to fix it.

Further the two issues also seem unrelated. This issue has a consistent 1 to 1 relationship; tapping the shift key sends a backspace instead of a shift - in every instance. The new related issue has a random effect in at least some cases where multiple lines of text or entire contents are cleared.

On Tue., Nov. 2, 2021, 03:11 01tot10, @.***> wrote:

I encountered the problem of Android keyboard deleting all text from a text-file when trying to do some edits on mobile. This happened to me on two occasions on consecutive days, which made me come to the conclusion that editing text files in Android is basically unusable.

Is this the correct bug to be following? I see that the related issue [*] is pointing here. Also, in the related issue, it is said that we are waiting for an upstream fix, but since this issue is already opened 2018, it would seem like this might still take a while? I'm sorry about my noobiness / stupid questions!

[*] nextcloud/android#8945 https://github.com/nextcloud/android/issues/8945

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nextcloud/files_texteditor/issues/104#issuecomment-957246835, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGVGPKGLUG5KCDVZ64N2DUJ6TK3ANCNFSM4FEHJEGQ .

[01tot10]

Thank you @shaneknysh for clearing things out! So bottom line seems to be, that at the moment the functionality is broken and there's no one "responsible" for fixing it, so to say. I guess I'll try to come up with some other solution when it comes to achieving what I've intended.

[01tot10]

At iOS-side things are apparently working again https://github.com/nextcloud/files_texteditor/issues/485