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 for Bug 60899 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I am having a unique issue while using pinch gesture on android device using Xamarin.
While zooming out using two fingers pinch I am getting a Gesture.Completed status while my two fingers are still on the screen and are moving closer together as soon as my fingers are almost 1 to 1.5 cms apart. This issue does not happen on iOS. I have been able to reproduce this on different android devices to confirm this is not a device related issue (Namely Asus Zenphone 3, New Moto E, etc.)
I am attaching a test project along with this bug and you can see an overlay with text when a pinch is running. The overlay goes away as soon as pinch is completed, which happens when zooming out and fingers are closer together (but still not touching).
Please Note: The issue is not reproducible on Windows Android Emulators. However, I was able to reproduce it on Android Emulator that is downloaded with Visual Studio for Mac.
I can confirm that this issue exists only on Android versions >= 7.0 and not on older versions of Android.
Yes Buddy Agree with you this issue exists only on Android versions >= 7.0 and not on older versions of Android.
I have also tried different Xamarin Forms versions. We cannot build our project with the latest version of Xamarin forms as we get the issue filed in bug 60293. So the latest Xamarin forms version that I can use to build is 220.127.116.11020 and the issue exists in that version as well.
Xamarin.Android is *just* a binding to the underlying Android APIs. Xamarin.Android should not have different behavior *compared to Java on Android* for the "same" app (same logic, same `AndroidManifest.xml` contents, and in particular the same `<uses-sdk/>` values, as those values will change Android's compatibility behaviors for the app.)
I cannot think of anything in Xamarin.Android *itself* which would trigger the behavior described in Comment #0.
My conclusion is that this is an Android "bug"/"feature". To convince me otherwise, you'd need to provide an equivalent Java app which *doesn't* exhibit the behavior you're seeing with Xamarin.Android.
As per your comment/suggestion I have created an app in Android Studio to demonstrate that this is not an Android issue but infact a Xamarin issue. Please find the Android Studio project attached.
Created attachment 26017 [details]
Please find attached the Android studio app to demonstrate that the mentioned bug is infact a Xamarin bug and not an Android issue.
(In reply to Abhishek D Malwankar from comment #7)
> Created attachment 26017 [details]
> Please find attached the Android studio app to demonstrate that the
> mentioned bug is infact a Xamarin bug and not an Android issue.
I can not see any difference when porting over the Android Studio application to Xamarin.Android.
Here are a couple videos:
I do not believe this would be an issue with Xamarin.Android and rather an oddity with Android.
Attaching my sample project as well.
Created attachment 26018 [details]
Thank you for your prompt reply Jon Douglas. You are absolutely right the ported Android app works exactly as expected in Xamarin.Android for Anndroid version >= 7.0. This also confirms what Jonathan Pryor mentions in his comment dated 2017-12-01 19:00:18 UTC.
So does that mean that there might be an issue in code between Xamarin.Forms and Xamarin.Android, since the original issue I encountered was using PinchGestureRecognizer in Xamarin forms?
(In reply to Abhishek D Malwankar from comment #10)
> Thank you for your prompt reply Jon Douglas. You are absolutely right the
> ported Android app works exactly as expected in Xamarin.Android for Anndroid
> version >= 7.0. This also confirms what Jonathan Pryor mentions in his
> comment dated 2017-12-01 19:00:18 UTC.
> So does that mean that there might be an issue in code between
> Xamarin.Forms and Xamarin.Android, since the original issue I encountered
> was using PinchGestureRecognizer in Xamarin forms?
I would say it's either an oddity with the device you're testing on, or a Xamarin.Forms specific issue. Please update this bug wth a sample repository built with Xamarin.Forms that demonstrates the difference from Xamarin.Android / Native Android. I am moving this bug to the Forms category instead.
Created attachment 26034 [details]
Xamarin Forms Pinch Gesture Test app
Please find attached the Xamarin Forms project that I had posted originally demonstrating the issue. I have tested this project on a Asus Zen phone 3 (model ASUS_Z012DC) Android version 7.0 and a Moto E4 with Android version 7.1.1 (path level Nov 2017) along with several Android emulators. Please note that this
Sorry for the incomplete comment above. Please note that the above test project was build using Visual Studio for Mac.
Jon, I would also like to mention that in the above Xamarin forms app, that I posted, it shows a text overlay when zoom gesture is in progress. You can see the reproduction of issue when you are zooming out and when two fingers are approximately 1 to 1.5 cm away (still moving closer) that the zoom gesture finishes (overlay disappears). This is the issue that does not happen on the Java app or the Xamarin.Android app.