-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Samsung keyboard composing region duplication on subset of devices #51893
Comments
Hello, This issue is really problematic as it is impossible to production deploy any app as samsung devices are very popular.
Thank you and i hope we will find a fix soon |
The Samsung Fold has the Problem too. |
As a partial workaround just install Gboard on yoiry device and the problem will be fixed as the issue is just coming from the keyboard and not the os itself |
@MichelMelhem Unfortunately, "installing a different keyboard" is not a solution to this. The problem in itself is that Samsung keyboards specifically are not working, and switching keyboards doesn't solve the problem for anyone other than one single end user. Thanks for the additional reports! Will be useful in continued work tackling this problem! |
I can confirm still happening on Galaxy Tab A (SM-T380) with Flutter version 1.12.13+hotfix.8 |
I can confirm still happening on J6 with Flutter version 1.12.13+hotfix.8 |
Samsung S9, S9+ has same problem. I tested it on device. |
I reproduced this with Samsung Galaxy S8 on Flutter Stable: 1.12.13+hotfix.8 |
Is there any update on the way to fix this issue ??? |
Facing similar issue on GalaxyS10e android 10.
|
I have landed flutter/engine#17426 which seems to fix many of the bugs on my test devices. It would be great if others could confirm that this also fixes bugs for them. Please try the change on master channel! |
I just tried and it is fixed for me. Thank you! |
We don't recommend it as there may be major bugs that we still have not caught, but every few days we roll to dev channel, which is still not recommended, but quite a bit safer than master. However, the final decision is still up to you to determine how important certain bugfixes are to include and which channel to use. As a rule of thumb, we try our best to keep master channel usable, and that succeeds a lot of the time, but there is no guarantee. |
@GaryQian Thank you! |
[ Test divice : Galaxy s8 ] *** Problems found in the last test
*** I tested it on the same device (Galaxy s8) as in the last bug report. The duplicate input problem, which was a major problem, did not appear, but the time delay occurred when the keyboard was hidden or visible. I hope you reproduce the above bugs on your Galaxy s8 device. ================================================ *** Log when Keyboard up *** Log when Keyboard down D/ViewRootImpl@b02d8a6MainActivity: ViewPostIme pointer 0 ================================================== Thank you. |
I will close this for now, if anyone still sees this bug, please let me know and we can reopen this! Thanks everyone for the patience given for this quite longstanding issue and the assistance provided in resolving it! |
@GaryQian Great work! As mentioned by @dannyvalentesonos, there are two remaining issues. Especially, I also confirmed "Time delay of the keyboard up and down" issue. |
I'll go ahead and open a separate issue if one doesn't already exist. Those symptoms seem separate from the primary problems tracked in this bug. |
#54310 Is the new bug I filed for the remaining issues mentioned |
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 |
Extracted/continued from #31512
When typing, hiding and reshowing the keyboard and typing punctuation like
.
can cause the composing region to duplicate.The original issue linked above impacted most Samsung devices. Since then, changes have landed that workaround the issue for most devices (flutter/engine#16547 and flutter/engine#15701). These workarounds have been confirmed to work on most devices.
However, it seems that a much smaller subset of devices are still seeing this bug even with the workaround, some with additional minor regressions in the form of the first letter sometimes repeating.
Devices confirmed to still exhibit the bug:
Devices that may have the bug in some form:
We have been in contact with Samsung to work on resolving this. See b/150639528
Please continue to report any specific models that are still experiencing the bug!
The text was updated successfully, but these errors were encountered: