Bug 45299 - Using a custom TypeConverter causes a "Sequence contains more than one matching element" compile error
Summary: Using a custom TypeConverter causes a "Sequence contains more than one matchi...
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.2
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Stephane Delcroix
Depends on:
Reported: 2016-10-12 01:00 UTC by Marco Tambalo
Modified: 2017-07-05 10:34 UTC (History)
5 users (show)

See Also:
Tags: ac
Is this bug a regression?: ---
Last known good build:

Sample solution for checking the issue. (45.31 KB, application/zip)
2016-10-12 01:00 UTC, Marco Tambalo

Description Marco Tambalo 2016-10-12 01:00:42 UTC
Created attachment 17990 [details]
Sample solution for checking the issue.

It seems that XAML compilation is causing this. When it is not used, the error does not manifest.
I attached a sample solution for checking.
Comment 1 Stephane Delcroix 2017-01-25 16:05:23 UTC
fixed in https://github.com/xamarin/Xamarin.Forms/pull/718
Comment 2 Stephane Delcroix 2017-01-25 16:06:27 UTC
in the meantime, you can get going by removing every static from your type converter so there's no static constructor generated, and you won't hit the bug
Comment 3 Samantha Houts [MSFT] 2017-01-30 19:55:51 UTC
Should be fixed in 2.3.5-pre1. Thank you!

Note You need to log in before you can comment on or make changes to this bug.