When panning, sometimes the PanGestureRecognizer won't reach its completed state when dragging very slowly. This is noticeable on at least Android, but supposedly occurs on Win 8.1 and WP 8.1.
Project to use, for ease: https://developer.xamarin.com/samples/xamarin-forms/WorkingWithGestures/PanGesture/
Add debug logs or breakpoints at the Gesture.Completed case in the PanContainer.cs's OnPanUpdated method.
When running the application, start a pan, hold it for a moment or two, and release.
The completed state is reached.
Occasionally/frequently, this state is not reached.
I am experiencing this issue as well. Is there a planned fix for this?
I can't believe that this bug has been around so long!!
The recognizer detects GestureStatus.Running without a problem so it sounds like a simple fix to make sure the GestureStatus.Completed state fires the updated event.
Xamarin Forms is a great idea but you cannot leave bugs like this hanging around for months at a time or people will stop developing with it.
Has anyone found a work-around?
I can't seem to reproduce this for Windows platforms, but I can confirm Android has this issue.
Should be fixed in 2.3.3-pre3. Thank you!
I have checked this issue with Xamarin.forms 2.3.3-pre3 and observed that this issue has been fixed. I have checked this issue with NexusP (Android 7.0).
Hence closing this issue.
It is NOT fixed, version 2.3.4 and still easily reproducible on Android 6 and 7.
This bug has come back as of 184.108.40.2060 and persists into 2.5.
Reproducible on Android 4.4 and 7
*** Bug 60896 has been marked as a duplicate of this bug. ***
*** Bug 60841 has been marked as a duplicate of this bug. ***
Hi all, I hope this bug can be resolved soon... it still happening in these versions:
Xamarin support libraries 220.127.116.11
Android SDK 26 (8.0)
Migrated to https://github.com/xamarin/Xamarin.Forms/issues/1495 for future tracking
I can confirm this is still an issue on 2.5.0 on Android.
Bug still exist.
To reproduce this bug,
Just hold your finger and release after few seconds, which do not fire completed neither cancel.
Any work around?
This seems to be fixed in the release 18.104.22.1680555
Good news! :)