The NineOldAndroids binding project fails to compile with class-parse enabled, as shown below. This same project compiles and runs against cycle8 based builds which use jar2xml.
> obj/Debug/generated/src/Xamarin.NineOldAndroids.Animations.Keyframe.cs(153,92): error CS0533: `Xamarin.NineOldAndroids.Animations.Keyframe.FloatKeyframe.Clone()' hides inherited abstract member `Xamarin.NineOldAndroids.Animations.Keyframe.Clone()'
> obj/Debug/generated/src/Xamarin.NineOldAndroids.Animations.Keyframe.cs(311,90): error CS0533: `Xamarin.NineOldAndroids.Animations.Keyframe.IntKeyframe.Clone()' hides inherited abstract member `Xamarin.NineOldAndroids.Animations.Keyframe.Clone()'
> obj/Debug/generated/src/Xamarin.NineOldAndroids.Animations.Keyframe.cs(435,93): error CS0533: `Xamarin.NineOldAndroids.Animations.Keyframe.ObjectKeyframe.Clone()' hides inherited abstract member `Xamarin.NineOldAndroids.Animations.Keyframe.Clone()'
##### Supplemental Info #####
Log File #1: http://xqa.blob.core.windows.net/gist/log-32612001223b470883268056d8ec5cf8.txt
##### Environment #####
Operating System: Mac OS X 10.10.5
Repo Name: monodroid.git
Branch Name: master
Build Revision: ab8f5949bf6f54ce79266ca54fe94045710c0fe6
It is indeed class-parse+api-xml-adjuster issue. Built fine with `xbuild /p:AndroidClassParser=jar2xml` on master.
https://github.com/xamarin/java.interop/pull/94 should fix it.
It was already merged.
I have checked this issue with build xamarin.android-7.0.99-86_ab8f5949bf6f54ce79266ca54fe94045710c0fe6 and getting same behaviour. Here is the screencast for the same: http://www.screencast.com/t/Yw1oqhfhm
I have checked this issue with latest C9 build and observed that it is working fine. Here is the screencast for the same: http://www.screencast.com/t/tEUjmA5mG
Environment info: https://gist.github.com/NaqeebAnsari/23e452af6eb96ffe9a806aa3505fe21d
Hence closing this issue.
Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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.
Create a new report for Bug 44531 on Developer
Community or GitHub if you have new information to add and do not yet see a matching
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
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.