Bug 53235 - EntryEnded event no longer working in iOS10
Summary: EntryEnded event no longer working in iOS10
Status: RESOLVED DUPLICATE of bug 53174
Alias: None
Product: iOS
Classification: Xamarin
Component: MonoTouch.Dialog ()
Version: XI 10.4 (C9)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-03-10 18:52 UTC by danmiser
Modified: 2017-03-10 19:01 UTC (History)
2 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 danmiser 2017-03-10 18:52:26 UTC
In the Monotouch.Dialog sample in github, make these changes in DemoElementApi.cs:

new EntryElement ("Login", "Your login name", null)
EnablesReturnKeyAutomatically = true,
AlignEntryWithAllSections = true,
// Add the line below
EntryEnded = HandleEnded

void HandleEnded(object sender,EventArgs e)
    throw new NotImplementedException();

1. Run the app
2. Select iPhone Settings Sample
3. Put the cursor in the Login field and type something in
4. Put the focus to the Password field
//expected: Exception to throw from HandleEnded
//actual: HandleEnded is never fired

There is some more discussion on this link:

In summary, it looks like this is affecting iOS10, and started some time after XS 6.1.5.
Comment 1 Vincent Dondain [MSFT] 2017-03-10 19:01:09 UTC

*** This bug has been marked as a duplicate of bug 53174 ***