Update google maps pods to 3.1.0 #2881
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@TVke 🤗 what was the error fixed by this upgrade? Just curious |
|
@rborn This was the issue with the problem and solution: |
|
Yes! I'm on an older version of maps and can't update due to the google maps pods version -- just tested this version and it's working for me now. Can't wait for the next release. |
|
When this will be released? and what will be the corresponding compatible react-native version? |
|
Waiting impatiently for this to be released. Any updates?? |
pohnean
pushed a commit
to pohnean/react-native-maps
that referenced
this pull request
Jul 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Does any other open PR do the same thing?
No other PR does the same thing
What issue is this PR fixing?
It fixes a error that occurs in react-native-google-maps 3.0.3 and not in 3.1.0
How did you test this PR?
I tested it by changing the node modules in my project and the bug was fixed
iOS (android the bug did not occur)
on simulator