Bug 37823 - Focus OnAppearing Entry with Numeric Keyboard
Summary: Focus OnAppearing Entry with Numeric Keyboard
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-01-20 01:17 UTC by Adam
Modified: 2016-02-23 17:09 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Adam 2016-01-20 01:17:09 UTC
A simple scenario.

I have an entry control called PinNumberEntry. I set the Keyboard to Numeric.

In the OnAppearing() method I do


It will show the Default Keyboard not the Numeric one. If i manually tap away to lose focus, then tap the control again, the numeric keyboard is shown.

I receive this issue in WinRT, I have not tested with other platforms as yet.

There were a few other bugs that looked fairly similar but didn't quite show my use case, hence the new bug report.
Comment 1 Paul DiPietro [MSFT] 2016-01-21 23:16:21 UTC
Would you be able to put together a small reproduction project? It would be appreciated in investigating the issue.
Comment 2 Adam 2016-02-22 23:47:15 UTC
I went to create a repro in -pre5 and it is now resolved. Looks like it was resolved by accident somewhere in 2.1.0.

Happy for this to be closed.
Comment 3 Adam 2016-02-23 02:47:57 UTC
Just with some more testing, I can confirm the issue is present in 2.0.1 Latest Stable but resolved in 2.1.0-pre5
Comment 4 Paul DiPietro [MSFT] 2016-02-23 17:09:43 UTC
I suppose we can close this then. :)