Bug 60841 - PanGestureRecognizer some times don't fire "complete" event
Summary: PanGestureRecognizer some times don't fire "complete" event
Status: RESOLVED DUPLICATE of bug 39768
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-11-23 20:18 UTC by Jaekov
Modified: 2018-01-23 15:31 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

PanGesture project (54.20 KB, application/zip)
2017-11-23 20:18 UTC, Jaekov

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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.

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.

Related Links:

Description Jaekov 2017-11-23 20:18:12 UTC
Created attachment 25821 [details]
PanGesture project

The PanGestureRecognizer on Xamarin.Forms 2.5 is not working properly on Android. 
The "PanComplete" event is not triggered when the user finish the touchEvent.

On Xamarin.Forms The PanGesture is working fine.

On the attached project you are able to see the behaviour of the Pan Gesture on a Carousel. This is just a RelativeLayout.
Comment 1 Jaekov 2017-11-23 20:34:35 UTC
Sorry, On Xamarin.Forms is not working too.
The PanGesture is working fine on Xamarin.Forms
Comment 2 Paul DiPietro [MSFT] 2017-11-28 22:40:47 UTC

*** This bug has been marked as a duplicate of bug 39768 ***