saber-notes/saber

Regression since 0.23.3: glitching keyboard keeps toggling infinitely

Closed this issue ยท 9 comments

Before submitting an issue, please check the following

  • I have searched for similar issues (both open and closed) and cannot find a duplicate
  • I agree to follow the Code of Conduct

Describe the bug

On my tablet since the last update saber is almost unusable because the keyboard keeps glitching : it opens on its own, and if I press the back button it toggles on again immediately. It seems to pop up usually when zooming out. When I press back repeatedly to exit the page and go back in : the keyboard is still raised.

To reproduce

  1. Usually I zoom out while panning with my fingers
  2. Notice the keyboard raises on its own
  3. From that point on I quand lower the keyboard

Expected behavior

The keyboard should not raise on its own.

Saber version

0.23.3 from github releasss

Device

  • Device: SM-T580
  • OS: android 12 on lineageos

Anything else?

I'm so sorry my explanation are not more detailed but this bug is too random and makes the app so unusable that I'll have to downgrade.

Update: it seems that the keyboard can be lowered down for good if I stay in vertical mode. I was indeed using my tablet mainly in landscape mode. nevermind, its still here.

Also note that the vertical cursor bar indicating a text field is indeed visible in the top left corner. For no reason. And it keeps blinking even when the keyboard is down

Same issue here. It keeps opening text mode and I'm unable to exit. It's frequently attempting universal clipboard and I'm unable to get it to stop. It's unusable for me as well.

I tried building and loading 0.23.2 but I just get a blank white screen.

If you have any suggestions please let me know! ๐Ÿ™

This also effects me. App is almost unusable.

It seems to open a text input field at the top left of a page when scrolling and in some cases it just goes in and out of text mode in an infinite loop until I trick it into stopping.

@davidbartonau

until I trick it into stopping.

Have you found a consistent way to trick it? I struggle to find repeatable steps that let me take notes.

@JohnmarkBeaty sorry, no. The trick is just to stop the keyboard from popping up and down, otherwise it will go on forever.

I find that once I stop it, if I don't move between pages it tends to work but going from page to page is an exercise in frustration.

Quick update, I was finally able to build and run this locally on my iPad.

Here's what I did:

  1. Checked out v0.23.2
  2. Updated line 36 of pencil_sound.dart ๐Ÿ‘‰ respectSilence: false,
  3. Updated lines 110-124 of file_manager.dart to the following
    ๐Ÿ‘‡๐Ÿ‘‡๐Ÿ‘‡
 if (!Platform.isIOS) {
      rootDir.watch(recursive: true).listen((FileSystemEvent event) {
        final type = event.type == FileSystemEvent.create ||
                event.type == FileSystemEvent.modify ||
                event.type == FileSystemEvent.move
            ? FileOperationType.write
            : FileOperationType.delete;
        String path = event.path
            .replaceAll('\\', '/')
            // The path may or may not be relative,
            // so remove the root directory path to make sure it's relative.
            .replaceFirst(documentsDirectory, '');
        broadcastFileWrite(type, path);
      });
    }
  1. Updated the signing profiles in xcode to use my developer account and ran on device.

I confirmed the text issue is not showing up in this version โœ…

Update : to me it seems triggered by the page transition. If i move far away so that the transition or top right corner is not visible, the keyboard seems to stay down

Edit: actually that's just what @davidbartonau said sorry

Same issue here, the keyboard opens whenever I enter a note and when I scroll down and up. I noticed that although the keyboard is there and does type in the note, the tool is not selected

Edit: Actually it toggles whenever a new page appears on the screen.

That's right, the problem does exist, and here is the related video.
https://github.com/saber-notes/saber/assets/112467275/04a46368-678b-4780-a02d-18718251a890

To me this is fixed in 0.24.0