Fixed
Status Update
No update yet.
Comments
si...@google.com
de...@gmail.com
Forgot Build #
QQ2A.200405.005
Android 10, April 2020 Security
QQ2A.200405.005
Android 10, April 2020 Security
si...@google.com
si...@google.com
I also have this problem, Pixel 4.
si...@google.com
Having the issue all day today after a reboot in the morning, Pixel 4, QQ2A.200501.001.B2
ap...@google.com
Same here. Also with Pixel 4, QQ2A.200501.001.B2
ap...@google.com
I'm having the same problem. Sometimes it doesn't work at all.
Description
Component used: BasicTextField Version used: 1.0.0-beta04. I've checked previous compose versions and the bug is reproducible since beta01. Devices/Android versions reproduced on: Any device not using Google's keyboard.
Steps to reproduce:
BasicTextFieldto your project. Do not specify any keyboard option or IME action.BasicTextFieldand try to introduce a newline char.Expected behavior:
The newline char should be added to the BasicTextField content.
Actual behavior:
The
onValueChangeconfigured lambda is invoked but the newline char is not working.A repository reproducing the error can be found here:https://github.com/Karumi/BasicTextFieldKeyboardBug
Attached to this bug report you'll find three screencasts. One of the shows the component working with Google's keyboard and two of them shows the component not working as expected using Swiftkey and Emoji keyboards.
It could be great if we could find a workaround before fixing the bug. For now the only solution we've found is to let our users know our app will not work as expected if they don't use Google's official keyoard.