Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 22337 [details]
Korean input bug and correct functionality image
When using the SearchBar in XF, the Korean input in iOS doesn't work, meaning: it doesn't form the Korean characters with each keystroke --Korean characters should be input with multiple keys
*** This bug has been marked as a duplicate of bug 51825 ***
I would like to know if bug 51825 has been resolved. I cannot access the issue.
Not, it is still open and we are really needing a fix for this --App in production in Seoul!
Are there any updates on this issue? It has been marked as resolved, can we expect a fix in XF 2.3.5?
Bump - This is not resolved as the characters do not combine.
If it has been resolved, will the fix be available in XF 2.3.6?
It was resolved as a duplicate which has already been reported.
Is there any improvement on this bug? It seems that this bug still exists on Xamarin alpha version. The only information I can get about this bug is "You are not authorized to access bug #51825."...
It would be very appreciated if somebody gives information about when this bug will be fixed or so (Or any workaround to bypass this bug, like external searchbar library).
I looked into this today and I believe I have a fix in place. The original bug report should no longer be private.