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
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.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
should be CAKeyFrameAnimation.AnimationDiscrete, not AnimationDescrete
it's on CAAnimation, not CAKeyFrameAnimation
Reassigning it to the right team.
Sadly changing that would be a breaking change, we could only XAMCORE_4_0-ify it and we don't know when we'll be able to break our APIs again, might never happen.
You already break it at each new iOS release (at least Apple does it for you).
Won't be a bad breaking change.
I won't blame you.
With the current name, it is hard to find.
And I suppose we are not much people using this constant.
No, we're _not_ breaking our binary compatibility with every release (of XI or iOS). That would be breaking all existing components from our store if we did so. Our goal is to ensure a new version of XI can be used with binaries produced with older version. Real breaking changes are very uncommon.
In most cases* we can find a way to "fix" Apple breakage (or our own mistakes*) without breaking our binary compatibility - and whenever it's possible we do so.
* including this one
In this specific case we can add a, correctly named, `AnimationDiscrete` field. What we can't do is remove the one with a typo: `AnimationDescrete`. OTOH we can annotate it with an [Obsolete] attribute that point people to the right name. That solve the issue (easier to find) and maintains compatibility for any existing binary that refers to the typo'ed symbol.
ok perfect !
Fixed in https://github.com/xamarin/xamarin-macios/commit/303926171cc330dafaa8c61f49cb845444ecc8fe