Closed Sebastian1989101 closed 6 years ago
@ryanharding that fixed it! Thanks for the suggestion.
Getting it even with [XamlCompilation(XamlCompilationOptions.Compile)] (both page and assembly level)
I just migrate from Xamarin Forms 2.5 to 3.1.0 and everything failed with AmbiguousMatchException at application start :(
You should clean and rebuild. This issue has been fixed in the June version.
On Wed, 1 Aug 2018 at 16:00 vodevil notifications@github.com wrote:
I just migrate from Xamarin Forms 2.5 to 3.1.0 and everything failed with AmbiguousMatchException at application start :(
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/xamarin/Xamarin.Forms/issues/2632#issuecomment-409566070, or mute the thread https://github.com/notifications/unsubscribe-auth/AHbkI3r9wR8pFvWvtRo-hRHTMYmN3gtrks5uMaZcgaJpZM4T27Os .
-- Best Regards, Gena
I'm getting this error since I upgraded from Xamarin 2.5 to 3.2. I removed all the "Source={x:Reference Page}}" in my xaml file but still the error is there. any ideas what else can be the cause?
@alicint please open a new issue, with a reproduction. thx
Hello, i'm getting this error on new Project.
VS2017 15.9.3, Xamarin Forms 3.4.0.1008975, .net Estándar 2.0
Page definition:
<ContentPage x:Name="ViewX"...>
In a control:
Parent="{x:Reference ViewX}"
Remove last line solve runtime error, but obviously it's doens't works as expected.
Any workaround, solution?.
Many thanks
@txarito please open a new issue, with a reproduction. thx
it is strange but this error was caused by livesharp for me. as referenced link
After the update to Xamarin.Forms 3.0 I got
AmbiguousMatchException
all over the place in my code. I'm not 100% why this happens and what it causes yet. A friend of mine got the same exceptions after the update - he has a complete different coding style and uses complete different libraries. Sadly he dosn't know why this happen and where it comes from.