Bug 39909 - SearchButtonPressed not working in .Net Native tool chain UWP Release
Summary: SearchButtonPressed not working in .Net Native tool chain UWP Release
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.1.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-25 10:03 UTC by Francesco
Modified: 2016-12-05 22:59 UTC (History)
3 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 Francesco 2016-03-25 10:03:34 UTC
The following exception is raised in Release mode whenever I add an event handler for SearchButtonPressed of SearchBar control.

System.Reflection.MissingMetadataException in System.Private.Reflection.Core.dll AdditionalInfo:Arg_InvokeMethodMissingMetadata, System.EventHandler

The exception is not raised if I uncheck Compile with .Net Native tool chain on the app properties.
Comment 1 E.Z. Hart [MSFT] 2016-03-29 16:06:11 UTC
Thank you for taking the time to submit the bug. We tried to reproduce the issue you reported but were unable given the description. If you could please attach a reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue, we would very much appreciate it.

Other information which may be helpful:
Which platform(s) are you targeting? 
Are you seeing this behavior on a device or on a simulator (or both)?

Warm regards,
Xamarin Forms Team
Comment 2 Paul DiPietro [MSFT] 2016-12-05 22:59:45 UTC
No reproduction has been provided so I am closing this issue. Please reopen with a working reproduction attached if it is in fact still an issue.