After reporting an issue with React Native Maps not working on Android with Expo, I wanted to find out if the root cause was:

1. Expo with React Native Maps
2. Reactive Native Maps

If the issue was with Expo, I could report it correctly and if it was with react-native-maps then perhaps when Expo upgrades their verison of that module it will be fixed.

The bug is in Expo. This repo demonstrates that using the same versions of react-native-maps (0.25.0) and react-native (0.59.10), the react-native-maps map.getMapBoundaries method works correctly. For example:

  handleRegionChange = async () => {
    try {
      const result = await this.mapRef.getMapBoundaries();
      this.setState({ mapBoundaries: JSON.stringify(result) });
    } catch (error) {
      console.error(error);
    }
  };

• Clone this repository
• Run yarn install
• Run yarn watch:android