You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connect iPhone to an external keyboard via bluetooth
Run/open an iOS flutter app (on a physical device)
Try to navigate the app using only an external keyboard
Expected results
Able to access & interact with all input elements (text fields, buttons, checkboxes, etc.) by making use of keys such as tab, up, down, space, enter, etc.
Actual results
I tried using the 1Keyboard app to use my Mac keyboard through bluetooth, and I also bought a bluetooth keyboard to try. Both yielded same result.
There is one workaround I have found but it only applies to text fields. That is to set autofocus to true and then adding this code to the text field: textInputAction: TextInputAction.next, onEditingComplete: () => FocusScope.of(context).nextFocus(), But, I would expect it to work out of the box and for any type of input element. Also this requires autofocus to be set to true which is not ideal in many cases.
I have tried using a small sample app I've built, as well as the Flutter Catalog app which I read should have this support.
Flutter Doctor output
Doctor output
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Copy of issue #76497 by @hkwinslow which was closed.
Steps to reproduce
Expected results
Actual results
textInputAction: TextInputAction.next, onEditingComplete: () => FocusScope.of(context).nextFocus()
, But, I would expect it to work out of the box and for any type of input element. Also this requires autofocus to be set to true which is not ideal in many cases.Flutter Doctor output
Doctor output
The text was updated successfully, but these errors were encountered: