onPress and onCalloutPress doesn't trigger on markers in iOS

[gmarinosyan]

Here is my code:

render() {
    return (
      <MapView style={styles.mapView} region={this.state.region}>
        <MapView.Marker
                coordinate={{latitude: 45, longitude: -75}}
                onSelect={this.markerPressed}
         />
      </MapView>
    )
}

markerPressed(){
    console.log("MarkerPressed");
}

The function is being called if I use onSelect or onDeselect, but not onPress or onCalloutPress. Is this an issue with something I am doing or a bug?

[christopherdro]

@gmarinosyan Is this for iOS or Android. onSelect and onDeselect if specifically for iOS and is what triggers the callout.

[gmarinosyan]

It is on iOS. Do the onPress and onCalloutPress functions not work on iOS?

[DennisMG]

I'm experiencing the same problem... Did you solve it @gmarinosyan ??

[gmarinosyan]

No, was not able to solve.

[christopherdro]

@gmarinosyan Did you guys already try the most recent release 0.6.0?

[cjbutcher]

Think I'm having this issue on 0.6.0

[klaste]

@christopherdro I have the same problem. It seems as if the _handleTap gesture recognizer delegate method of AIRMapMarkerManager is never called. I am on 0.6.0, React Native 0.29-rc, and iOS 10, so I don't know if this is of any relevance or if I am looking in the right place anyway.

[klaste]

@christopherdro I will look into it. Do you have any idea what could be the cause?

[nickw]

@christopherdro @lelandrichardson I'm experiencing this issue as well using v0.6.0 and react-native v0.28.0. I'm happy to open a PR if anyone can point me in the right direction.

[KunwarSingh]

Hey man I'm also facing same issue, onSelect is working but not onCallbackPress. Please try to solve this issue.

[itsdevcoffee]

Yup, onPress isn't working at all for me on IOS. Any update on a work around or PR?

[KGALLET]

+1 onPress isn't working for me too on iOS.

[zelll]

@DmsChrisPena @KGALLET , I found this issue. It's a better place than #403 to answer your question.

See patch below, it only affects native pin marker. I'm not a iOS developer. Can someone review it and create a PR? @nickw ?

--- map2/node_modules/react-native-maps/ios/AirMaps/AIRMapMarker.m  2016-07-10 04:47:31.000000000 +0800
+++ map/node_modules/react-native-maps/ios/AirMaps/AIRMapMarker.m   2016-07-19 22:04:56.000000000 +0800
@@ -72,6 +72,10 @@
         if (_pinView == nil) {
             _pinView = [[MKPinAnnotationView alloc] initWithAnnotation:self reuseIdentifier: nil];
             _pinView.annotation = self;
+            _pinView.center = CGPointMake(16, 20); // make position/size of AIRMapMarker to match the pin
+            self.centerOffset = CGPointMake(-16, -20);
+            self.frame = CGRectMake(self.frame.origin.x, self.frame.origin.y, 32, 39);  // TODO: remove hard-coded size
+            [self addSubview:(UIView *) _pinView]; // add pin as child of marker and return marker itself
         }

         _pinView.draggable = self.draggable;
@@ -83,7 +87,7 @@
             _pinView.pinTintColor = self.pinColor;
         }

-        return _pinView;
+        return self;
     } else {
         // If it has subviews, it means we are wanting to render a custom marker with arbitrary react views.
         // if it has a non-null image, it means we want to render a custom marker with the image.

ps: A workaround is using a custom view marker. Only the default pin marker has this problem.