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.
As per the discussion at
using Xamarin.Forms 126.96.36.199, running on Android, using a physical keyboard, if the Completed handler of one Entry sets the focus to another Entry, that focus setting does not work (it seems the focus ends up on the control after the second Entry).
Note that if a delay is introduced before attempting to set the focus, then it works but introduces a race condition (so only works so much of the time).
This delay is not necessary on other platforms (e.g. UWP), nor on Android devices using a soft keyboard rather than a physical keyboard. Using a delay is not a solution as the race condition makes it unreliable, and increasing the delay to make it less unreliable makes the app sluggish.
I can confirm this bug, having the same issue here.
If needed, I can provide a sample project demonstrating it.
@Giusepe Casagrande: Please do! Thank you!
@Samantha Houts Here it is: https://github.com/GiusepeCasagrande/ScrollLoginBug/tree/FormsWay
If you run it on iOS it will work as expected, but on Android it will go crazy and "skip the fields"
Returning to NEW status for further investigation
The reproduction looks to show the issue against 2.3.5 as well; pressing enter when inside the first field will cause it to jump to the last. Setting to confirmed until this can be further investigated.
Should be fixed on 2.5.1-pre1