https://github.com/iampeterbanjo/react-native-v59-maps

MVP to show react-native 0.59.10 works with react-native-maps 0.25.0
https://github.com/iampeterbanjo/react-native-v59-maps

issues react-native react-native-maps

Last synced: about 1 month ago
JSON representation

MVP to show react-native 0.59.10 works with react-native-maps 0.25.0

• Host: GitHub
• URL: https://github.com/iampeterbanjo/react-native-v59-maps
• Owner: iampeterbanjo
• Created: 2019-10-16T09:27:11.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2021-05-11T05:24:00.000Z (over 3 years ago)
• Last Synced: 2023-03-23T01:47:07.349Z (almost 2 years ago)
• Topics: issues, react-native, react-native-maps
• Language: Objective-C
• Homepage:
• Size: 1.03 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 6
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# React Native Maps with React Native 0.59.x

## Background

After reporting an [issue with React Native Maps not working on Android][react-native-maps-issue-2665] 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.

## Result

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:

``` JavaScript

  handleRegionChange = async () => {

    try {

      const result = await this.mapRef.getMapBoundaries();

      this.setState({ mapBoundaries: JSON.stringify(result) });

    } catch (error) {

      console.error(error);

    }

  };

```

## Steps

* Clone this repository 

* Run `yarn install`

* Run `yarn watch:android`

[react-native-maps-issue-2665]: https://github.com/react-native-community/react-native-maps/issues/2665