Map navigation does not work on Android when using Shell
https://github.com/alex-relov/xamarin.froms.maps.shell
Parent: #2415
I can reproduce this against the latest 4.0-pre4, but the navigation (scrolling the map around) technically works, but only slightly and is otherwise inconsistent and choppy.
I've run into this myself. There doesn't seem to be any benefit in container structure (in case of gesture hijacking). Seems to allow horizontal panning so long as gesture remains within about 20dp from original Y gesture position, any vertical deviation past that seems to cut off the gesture entirely. To me that seems to point at it thinking we're attempting to scroll.
I've just experienced this issue today and can easily reproduce with a simple Shell app with an embedded Xamarin Forms Map.
Panning/Zooming the map on Android is not usable.
Is there any update as to when this might be fixed? Thanks.
I've just experienced this issue today and can easily reproduce with a simple Shell app with an embedded Xamarin Forms Map.
Panning/Zooming the map on Android is not usable.
Is there any update as to when this might be fixed? Thanks.
To the release should fix, for now the task in the status To do
I'm really looking forward to the fix. If any got a workaround, please share.
I am also keen to find a workaround, assuming a fix will not be available soon. Anybody got any ideas?
I see that there are 216 todos and 2 is currently in progress and one of them is this case, so it should be done soon.
As a workaround you can create a custom renderer for the Map (like suggested by samhouts https://github.com/xamarin/Xamarin.Forms/issues/5205):
[assembly: ExportRenderer(typeof(CustomMap), typeof(CustomMapRenderer))]
.....
public override bool DispatchTouchEvent(MotionEvent e)
{
Parent.RequestDisallowInterceptTouchEvent(true);
return base.DispatchTouchEvent(e);
}
@samhouts
I saw that this issue is about to be resolved for this sprint, is there any release date to resolve this issue? I'm using xamarin.forms.googlemaps and renderer not worked for me.
Thanks.
closed by #7032
Most helpful comment
I'm really looking forward to the fix. If any got a workaround, please share.