You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All four overloads contain the same <param> values, regardless of their signature:
/// <param name="target">The object whose properties are to be animated.</param>/// <param name="xProperty">The property for the x coordinate being animated.</param>/// <param name="yProperty">The property for the y coordinate being animated.</param>/// <param name="path">The <code>Path</code> to animate values along.</param>
Looking at the generated ObjectAnimator.cs MCW, we seem to have an issue with Javadoc conversion related to certain overloads:
https://gist.github.com/pjcollins/8f5d3d30877dab7f4f58d7324c8e9672
All four overloads contain the same
<param>values, regardless of their signature:This is seemingly causing some issues with a recent API docs update, where we have a handful of invalid
<param/>values in:https://github.com/xamarin/android-api-docs/blob/fda1236a384b228b46033fd624854851a87c08df/docs/Mono.Android/en/Android.Animation/ObjectAnimator.xml#L204-L418
A similar issue was noted in #931.