-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple properties with name 'BadgeView.Shared.CircleView.CornerRadius' found #11
Comments
I don't know what causes the issue but after spending 8 hour I finally made it. CircleView.cs
For android:
For iOS:
That's it! |
I get the same exception after updating from xamarin forms 3.1 to 3.5 for the following code
|
I am getting the same exception, with this plugin Xamarin.Forms.Xaml.XamlParseException: Position 8:81. Multiple properties with name 'BadgeView.Shared.CircleView.CornerRadius' found. ---> System.Reflection.AmbiguousMatchException: Ambiguous match found. Could you please fix this issue, it will be really helpful, Thanks |
The issue lies in the names of the CircleView properties CornerRadius and CornerRadiusProperty. They're declared alongside the inherited BoxView properties of the same name, which confuses reflection in later versions of Xamarin for some reason. If you put the CircleView.cs file from the repository's source into a new project with the latest Xamarin libraries installed, these properties are said to be hiding the derived members and that, if this is what you're intending (which it is), you need to use the new keyword with the property. These issues have already been fixed with the October 2018 commit (renaming CornerRadius to BadgeCornerRadius). The NuGet repository only has the October 2017 version, however, so pushing these latest changes to it should solve the problem. |
Details about Problem
Versions:
Xamarin.Forms: 3.3.0.967583
BadgeView: 2017.10.17
Problem
I am getting this error after updating xamarin forms to the latest stable version with BadgeView nuget packages.
Verbose Logs
XAML code
Expected behaviour
The text was updated successfully, but these errors were encountered: