[IOS] After the keyboard is folded, it cannot be popped up again

[xiaohucode]

After the keyboard is folded, it cannot be popped up again.
only IOS devices

Rpreplay.Final1776693054.mp4

[heckmon]

Does this issue occurs when the lineWrap off?

[heckmon]

Seem like an iOS only issue. No issue with android. I don't have an iOS device to test it.
Is there any error log or anything appear on the console?

[heckmon]

@xiaohucode hello?

[xiaohucode]

Seem like an iOS only issue. No issue with android. I don't have an iOS device to test it. Is there any error log or anything appear on the console?

No error logs have appeared. When the keyboard is retracted, it seems that the focus hasn't been lost

[heckmon]

I see that in the video, the lineWrap is set to true. So does this issue occur when the lineWrap is false?.
Could you find any clue or anything related to the issue? So I can try to fix it.
Even if I managed to obtain an IOS device, a macbook is required to run flutter on IOS.

[xiaohucode]

I see that in the video, the lineWrap is set to true. So does this issue occur when the lineWrap is false?. Could you find any clue or anything related to the issue? So I can try to fix it. Even if I managed to obtain an IOS device, a macbook is required to run flutter on IOS.

The cause is not to the 'lineWrap' parameter .

Flutter native components use WidgetsBindingObserver.didChangeMetrics to listen for changes

[heckmon]

I don't think it is related to WidgetsBindingObserver.
Code Forge uses the TextInputClientMixin to connect and show IME and keyboard. The CodeForgeController class extends it.
Make sure that you're using the latest version.

Here are some debugging steps to find the issue:
Clone this repo and open the code_area.dart.
Then go to the 10097th line.
You can see the line focusNode.requestFocus().
This is where the editor calls the keyboard on tapping.
Just add this just below that line (on 10098):

print("##############")
print(focusNode.hasFocus)
print("###############")

Then click on the screen and watch the logs. It probably prints true for the first touch, like in the video. Tell me if it is true or false on further touches.

[heckmon]

Make sure to use the clone's path in the pubspec instead of the pub.dev package, for testing. Like this:

code_forge:
     path: { /path/to/clone/code_forge }

[xiaohucode]

[heckmon]

According to flutter engine logic, if a widget has focus, the keyboard should be shown. But seems like the IOS is not showing the keyboard even after the app has focus. Because the focusNode's listener invokes the IME on focus change. However there is a workaround to forcefully call the keyboard. Wait a minute. I'll give you a patch code to paste in the 10098th line.

[heckmon]

final _connection = _controller.connection;
if (_connection == null || !_connection!.attached) {
          _connection = TextInput.attach(
            _controller,
            TextInputConfiguration(
              readOnly: widget.readOnly,
              enableDeltaModel: true,
              enableSuggestions: widget.enableKeyboardSuggestions,
              inputType: widget.keyboardType,
              inputAction: TextInputAction.newline,
              autocorrect: false,
              viewId: View.of(context).viewId,
            ),
          );

          _controller.connection = _connection;
          _connection!.show();
          _connection!.setEditingState(
            TextEditingValue(
              text: _controller.text,
              selection: _controller.selection,
            ),
          );
        }

[heckmon]

if the above code doesn't work, force the keyboard call without the if condition checks:

final _connection = _controller.connection;
_connection = TextInput.attach(
            _controller,
            TextInputConfiguration(
              readOnly: widget.readOnly,
              enableDeltaModel: true,
              enableSuggestions: widget.enableKeyboardSuggestions,
              inputType: widget.keyboardType,
              inputAction: TextInputAction.newline,
              autocorrect: false,
              viewId: View.of(context).viewId,
            ),
          );

          _controller.connection = _connection;
          _connection!.show();
          _connection!.setEditingState(
            TextEditingValue(
              text: _controller.text,
              selection: _controller.selection,
            ),
          );

[xiaohucode]

The implementation of connectionClosed is overly simplistic

This solved my problem

  void connectionClosed() {
    if (connection != null && connection!.attached) {
      connection?.connectionClosedReceived();
      connection = null;
      focusNode?.unfocus();
    }
  }

[heckmon]

Thank you for figuring it out. I'll update the connectionClosed() method on the upcoming release. Till then keep this issue open. 👍👍

[menghupai]

Items 1 and 2: This problem also persists on the Android platform.

1. In a single row, you cannot select bubbles to move
2. The bubble will not disappear after losing focus
3. missing implementation of updateFloatingCursor