iOS keyboard is no longer presenting the @ or numbers when 123 is pressed #62659
Description
From version 1.20 to 1.21 of Flutter, our users became incapable of logging in our apps as the @ symbol can't be presented anymore. Only the numeric keypad is presented when we click the 123 button (no more special symbols keyboard). The previous default was to show the standard symbols keyboard.
Steps to Reproduce
- Build iOS app with flutter 1.21.
- Select an input field and try to type the @ symbol
- Rebuild the app with 1.20 and repeat. Now you can.
Expected results:
I should be able to type something@somewhere
Actual results:
Can't open the keyboard to show @ symbol
Logs
verbose` and attach all the log output below between the lines with the backticks. If there is an
exception
1.21 with problem
All done!
[✓] Flutter: is fully installed. (Channel master, 1.21.0-2.0.pre.114, on Linux, locale en_US)
[!] Android toolchain - develop for Android devices: is partially installed; more components are available. (Android SDK version 29.0.2)
[✗] Chrome - develop for the web: is not installed. (Cannot find Chrome executable at google-chrome)
[!] Android Studio: is not available. (not installed)
[✓] Connected device: is fully installed. (1 available)
1.20 without the problem
All done!
[✓] Flutter: is fully installed. (Channel master, 1.20.0-1.0.pre.118, on Linux, locale en_US)
[✓] Android toolchain - develop for Android devices: is fully installed. (Android SDK version 29.0.2)
[✗] Chrome - develop for the web: is not installed. (Cannot find Chrome executable at google-chrome)
[!] Android Studio: is not available. (not installed)
[✓] Connected device: is fully installed. (1 available)
Metadata
Metadata
Assignees
Labels
Critical issues such as a build break or regressionEntering text in a text field or keyboard related problemsIt was better in the past than it is nowflutter/packages/flutter/cupertino repositoryflutter/packages/flutter/material repository.Found to occur in 1.21flutter/packages/flutter repository. See also f: labels.The issue has been confirmed reproducible and is ready to work oniOS applications specifically