Bug 21064 - Xamarin.Forms - Entry.Completed does not fire on Android softkeyboard, only hardkeyboard
Summary: Xamarin.Forms - Entry.Completed does not fire on Android softkeyboard, only h...
Status: VERIFIED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.1.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-07-02 17:48 UTC by Jon Douglas [MSFT]
Modified: 2015-02-02 09:28 UTC (History)
12 users (show)

Tags:
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:
Status:
VERIFIED FIXED

Description Jon Douglas [MSFT] 2014-07-02 17:48:05 UTC
It seems that the Completed event will not fire unless using a hardkeyboard within Android. To reproduce, run the sample on a device/emulator with a softkeyboard installed and notice the event will not fire. You can then run a stock emulator and turn on keyboard support in which after hitting "Enter" on the field, the event fires.

https://www.dropbox.com/s/8ppy05wjxsqmzrm/EntryTest.zip
Comment 1 John Hair 2014-07-17 14:44:41 UTC
Confirmed, still exists in 1.2.2.6238 pre1
Comment 2 rwakelan 2014-08-01 16:28:13 UTC
Still exists in the full 1.2.2 release.  Why is this marked fixed?
Comment 3 Barton 2014-11-24 21:50:29 UTC
Yes, Xamarin.Android
Version: 4.20.0 (Trial Edition)
I'm having this issue. Delays in fixes could be a real barrier to investing in this product. Thanks.
Comment 4 rwakelan 2014-11-25 09:34:54 UTC
Barton - If you haven't invested yet, don't.  This is one of several bugs in Xamarin.Forms I have personally encountered. None of those bugs have even been touched by Xamarin.  This product should be in alpha/beta. Instead, they have paying customers reporting bugs that never get looked at, let alone fixed.
Comment 5 earchambault 2015-01-13 12:45:11 UTC
Is there any timeline on when this may be fixed.  I have the latest stable release of xamarin.forms and it is still occurring.
Comment 6 Seth Rosetter 2015-01-14 19:11:04 UTC
Should be fixed in 1.3.2-pre1
Comment 7 Parmendra Kumar 2015-01-30 09:28:38 UTC
I have checked this issue and observed that the application throw exception on Xamarin.Forms.1.3.2.6309-pre2.

On Xamarin.Forms.1.0.6186 :

Enter some text to Textbox and press the enter the popup show message "Completed Event Fired", "Time to dances a jig".

On Xamarin.Forms.1.3.1.6296 :

Enter some text to Textbox and press the enter no event fire.

On Xamarin.Forms.1.3.2.6309-pre2 :

Enter some text to Textbox and press the enter the application throw a exception.

Note: I have checked this issue on Emulator and Device. I am getting same behavior on both.

Screencast: http://www.screencast.com/t/SWdc7UqW7

Debug Log: https://gist.github.com/Parmendrak/60b90bbf1c28c4d621a0
IDE Log: https://gist.github.com/Parmendrak/ba7c29bf959729f0d1f7

Environment info:

Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.5.51641

Installed Version: Professional

Xamarin   3.9.291.0 
Xamarin.Android   4.20.0.34 
Xamarin.iOS   8.6.1.0
Comment 8 Jason Smith [MSFT] 2015-02-02 01:49:47 UTC
This crash is because the sample is out of date. The overload in usage requires the cancel button be passed valid text. There is an overload which does not take a cancel button instead.
Comment 9 Parmendra Kumar 2015-02-02 09:28:49 UTC
As per comment #8 the sample is out of date  So I am going to closing this issue.