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.
The AnimationExtensions.AnimateKinetic method accepts a 'finished' action that presumably should be invoked whenever the animation stops. The Animate<T> method accepts a similar parameter, and if present, the action is always invoked, even if the animation is stopped prematurely using AbortAnimation.
For kinetic animations, though, the 'finished' action is only invoked if the animation stops normally (i.e. when the velocity goes to zero). Calling AbortAnimation does not result in the 'finished' action being invoked.
To be consistent Animate<T>, the 'finished' action should be invoked for kinetica animations as well, even if the animation is stopped prematurely.
RELATED: AnimationIsRunning does not return true if a kinetic animation is running -- only normal animations. Not sure if this is by design or not.
IMPACT: This bug along with the current behavior of AnimationIsRunning makes it hard for an element to respond differently to user input based on its animation state, since we don't have a reliable way to determine whether the animation is running or has completed.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team