Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed onMapReady no longer getting called on iOS #1853

Merged

Conversation

IjzerenHein
Copy link
Contributor

Hi, this fixes onMapReady no longer getting called correctly in v0.18.x.

Due to this commit (https://github.com/airbnb/react-native-maps/pull/1797/files#diff-8a72baa08460d22c71989ddcbf76d49f), onMapReady was only called when the very first MapView was rendered for the very first time. After unmounting/mounting, or rendering any other MapView, onMapReady would be never called.

@rborn
Copy link
Collaborator

rborn commented Dec 13, 2017

LGTM
@alvelig should I merge, or you do it ? That's a question for all the PRs I can review 😊

@rborn
Copy link
Collaborator

rborn commented Dec 15, 2017

@christopherdro ?

@christopherdro christopherdro merged commit fff00ef into react-native-maps:master Dec 15, 2017
@vendramini
Copy link
Contributor

I'm using the latest version and onMapReady still not being called. Is this PR released?

Thanks!

@emilefleming
Copy link

Same here, running 0.19.0 with Google Maps on iOS and it only fires on the first map load. InitialRegion is working now party but doesn't seem to respect the delta and is very zoomed out. @vendramini are you seeing that as well?

@alvelig
Copy link
Contributor

alvelig commented Dec 20, 2017

@vendramini are you using GoogleMaps iOS? No, this PR not released yet. Please try npm i -S git+ssh://git@github.com:react-community/react-native-maps.git

@emilefleming Could you please open an issue for that? As this PR does not touch GoogleMaps

@emilefleming
Copy link

@alvelig sure thing.

@vendramini
Copy link
Contributor

vendramini commented Dec 20, 2017

@alvelig no, I'm using apple maps.
@emilefleming no, didn't happens here.

EDIT
@alvelig it's working now pointing to react-native-maps.git. Is safe to point package directly to master? Should I change when this PR is released or doesn't matter?

Thanks.

@alvelig
Copy link
Contributor

alvelig commented Dec 20, 2017

@vendramini Sure, with npm you just get the same but through npm and released under some tag (version). Of course, it's better to keep npm version in package.json, because it gives you version control (exact version, not higher than, etc).

@ghost
Copy link

ghost commented Jan 8, 2018

@IjzerenHein @alvelig this doesn't seem to work in the latest release? I still experience the following; I removed cache, rebuilt etc.

onMapReady was only called when the very first MapView was rendered for the very first time. After unmounting/mounting, or rendering any other MapView, onMapReady would be never called.

@IjzerenHein
Copy link
Contributor Author

Seems this hasn't been released yet to npm, you should use the master branch from github until that is done

@rborn
Copy link
Collaborator

rborn commented Jan 8, 2018

@christopherdro do we need to push a new version to npm ? thnx cc: @alvelig

@carsonwah carsonwah mentioned this pull request Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants