OK, that is not a swipe component in the Glide sense. What seems to be happening is that when you “swipe” with your finger, it’s functioning like a back button. I am familiar with this happening in web browsers. My windows laptop has a touchscreen and I can swipe back a page (same as clicking the back button).
I just did some testing an I can definitely reproduce the issue. Doesn’t seem to be an issue if the map is on a top tab level screen or in an overlay, but if you navigate to the screen from a collection any other way then it becomes an issue.
A little technical, but it seems that Glide needs something like a ‘touchmove’ listener with this code below to prevent default touch actions, used for navigation, from interfering with using the map. I just recently had to implement something like this in a custom audio player where you can scrub through audio by touching and dragging on a progress bar. This little bit of code fixed the issue for me…but what I’m working on is not exactly a Glide App in the traditional sense. @NoCodeAndy
event.preventDefault();
It’s nothing we can fix as end users unfortunately. Glide would have to fix it.
For the time being, I recommend changing your Target for the Show Detail Screen action on the collection to use an Overlay. Seems that you can move the map on an overlay without inadvertently navigating backwards.
