This repository was archived by the owner on Sep 22, 2025. It is now read-only.
Update to react-native-maps v1.20.1 #23
Closed
Conversation
This file contains hidden or 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
## [1.10.4](react-native-maps/react-native-maps@v1.10.3...v1.10.4) (2024-03-10) ### Bug Fixes * **android:** remove dangling map marker views causing memory leak ([react-native-maps#4992](react-native-maps#4992)) ([02ed7c0](react-native-maps@02ed7c0))
# [1.11.0](react-native-maps/react-native-maps@v1.10.4...v1.11.0) (2024-03-10) ### Features * **android:** add bridgeless support ([react-native-maps#4985](react-native-maps#4985)) ([3ad0265](react-native-maps@3ad0265))
## [1.11.1](react-native-maps/react-native-maps@v1.11.0...v1.11.1) (2024-03-10) ### Bug Fixes * **android:** custom maker performance improvements when view tracking ([react-native-maps#4969](react-native-maps#4969)) ([f30c9d7](react-native-maps@f30c9d7))
…-maps#4973) * fix: removing polylines on ios with googleProvider * chore: code format
## [1.11.2](react-native-maps/react-native-maps@v1.11.1...v1.11.2) (2024-03-11) ### Bug Fixes * **iOS:** removing polylines on iOS with googleProvider ([react-native-maps#4973](react-native-maps#4973)) ([6603060](react-native-maps@6603060))
## [1.11.3](react-native-maps/react-native-maps@v1.11.2...v1.11.3) (2024-03-11) ### Bug Fixes * AnimatedRegion types ([react-native-maps#4909](react-native-maps#4909)) ([5fd9ca6](react-native-maps@5fd9ca6))
…act-native-maps#4990) Co-authored-by: Jan Kozinski <johnny@thewidlarzgroup.com>
# [1.12.0](react-native-maps/react-native-maps@v1.11.3...v1.12.0) (2024-03-29) ### Features * **google-maps:** add onSelect/onDeselect support fo google maps ([react-native-maps#4990](react-native-maps#4990)) ([b9fbe31](react-native-maps@b9fbe31))
…ct (react-native-maps#5016) Co-authored-by: salah ghanim <salah@getaway.pro>
* chore(update-RN): examples: fix linking for android
* feat(google-init): Improve google maps initialisation
- Improve Camera Initialisation on Android
* feat(google-init): Improve google maps initialisation
- Introduce googleRenderer prop to support legacy renderers.
* chore(update-RN): breaking change: remove deprecated enableLatestRenderer method
---------
Co-authored-by: salah ghanim <salah@getaway.pro>
# [1.13.0](react-native-maps/react-native-maps@v1.12.0...v1.13.0) (2024-04-01) ### Features * **google-init:** Improve Google Maps Initialisation on Android ([a1be51b](react-native-maps@a1be51b))
- Migrated unsupported APIs - enabled the new architecture for the iOS example app with MapKit.
- example for android is working as well
- increase android build memory
Co-authored-by: salah ghanim <salah@getaway.pro>
## [1.13.1](react-native-maps/react-native-maps@v1.13.0...v1.13.1) (2024-04-13) ### Bug Fixes * **android:** onSelect was crashing android ([react-native-maps#5032](react-native-maps#5032)) ([b3ce3fc](react-native-maps@b3ce3fc))
…d is buggy (react-native-maps#5034) - reset googleOptions each time a view is initialised and pass initialProps correctly Co-authored-by: salah ghanim <salah@getaway.pro>
## [1.13.2](react-native-maps/react-native-maps@v1.13.1...v1.13.2) (2024-04-13) ### Bug Fixes * **android:** googleMapOptions / initialising multiple maps on android is buggy ([react-native-maps#5034](react-native-maps#5034)) ([be28937](react-native-maps@be28937))
- attempting to fix the android CI by version bumping reanimated, reset cache
- attempting to fix the android CI by version bumping reanimated, reset cache
- attempting to fix CI by removing support for arm64-v8a for the example project
- using pickFirst for now
- pickfirst for all instead of exclude
# [1.18.0](react-native-maps/react-native-maps@v1.17.3...v1.18.0) (2024-08-18) ### Features * add anchor and centerOffset prop to GeoJson component to be passed to Marker ([react-native-maps#5140](react-native-maps#5140)) ([266be79](react-native-maps@266be79)), closes [react-native-maps#5139](react-native-maps#5139)
Update README.md small change which caused confusion
## [1.18.1](react-native-maps/react-native-maps@v1.18.0...v1.18.1) (2024-10-12) ### Bug Fixes * documentation on README.md ([react-native-maps#5174](react-native-maps#5174)) ([b853f3a](react-native-maps@b853f3a))
…-maps#5167) * fix(ios): do not store the original map
….0.0 (react-native-maps#5183) * fix(map): prevent overrideGestureRecognizers from being called multiple times per view * chore(map): update GoogleMaps SDK to v8.4 * chore(map): update Google-Maps-iOS-Utils to v5.0.0 * docs(map): update minimum iOS version to 14 for GoogleMaps projects
…t-native-maps#5184) * feat(iOS): add support for loadingBackgroundColor for GoogleMaps on iOS * chore(iOS): remove call for deprecated setMetalRenderer (already the default) * chore(iOS): enable LoadingMap example for GoogleMaps on iOS
…eact-native-maps#5185) fix: correctly check for iOS OS version before using cameraZoomRange
## [1.18.2](react-native-maps/react-native-maps@v1.18.1...v1.18.2) (2024-10-14) ### Bug Fixes * correctly check for iOS OS version before using cameraZoomRange ([react-native-maps#5185](react-native-maps#5185)) ([4efd881](react-native-maps@4efd881))
… consistency with Android (react-native-maps#5196) fix(iOS): refactor onPress(Marker) to return nativeEvent.position instead of nativeEvent.point for consistency with Android and documentation react-native-maps#4996 followup
## [1.18.3](react-native-maps/react-native-maps@v1.18.2...v1.18.3) (2024-11-09) ### Bug Fixes * **iOS:** Refactor onPress(Marker) to return nativeEvent.position for consistency with Android ([react-native-maps#5196](react-native-maps#5196)) ([956783f](react-native-maps@956783f)), closes [react-native-maps#4996](react-native-maps#4996)
…ative-maps#5150, react-native-maps#5152, react-native-maps#5153, react-native-maps#5154) (react-native-maps#5151) * fix(Android): reapply camera after padding is updated * fix(Android): defer setPadding until the map is laid out. * fix(Android): call moveToCamera() with initialCamera property * fix(Android): keep edgePadding when updating mapPadding property * fix(Android): remove 50px padding specified by fixToXXX() Fixes react-native-maps#5150 Fixes react-native-maps#5152 Fixes react-native-maps#5153 Fixes react-native-maps#5154
## [1.18.4](react-native-maps/react-native-maps@v1.18.3...v1.18.4) (2024-11-09) ### Bug Fixes * **Android:** fix multiple padding related issues on Android ([react-native-maps#5150](react-native-maps#5150), [react-native-maps#5152](react-native-maps#5152), [react-native-maps#5153](react-native-maps#5153), [react-native-maps#5154](react-native-maps#5154)) ([react-native-maps#5151](react-native-maps#5151)) ([0009170](react-native-maps@0009170))
… Map (react-native-maps#5162) (react-native-maps#5163) * fix(ios): setCamera calls before layoutSubviews are ignored on Google Map (react-native-maps#5162) Fixes react-native-maps#5162
# [1.19.0](react-native-maps/react-native-maps@v1.18.4...v1.19.0) (2024-11-09) ### Features * add onRegionChangeStart event to MapView ([react-native-maps#5144](react-native-maps#5144)) ([eeb56f9](react-native-maps@eeb56f9))
fix: Remove unstable_reactLegacyComponentNames New architecture is now enabled by default. chore: Update react-native to 0.76.1 Updated development dependencies for semantic-release
## [1.19.1](react-native-maps/react-native-maps@v1.19.0...v1.19.1) (2024-11-10) ### Bug Fixes * Remove unstable_reactLegacyComponentNames ([react-native-maps#5209](react-native-maps#5209)) ([33112be](react-native-maps@33112be))
…5210) - helps improve android click handling Co-authored-by: salah ghanim <salah@getaway.pro>
# [1.20.0](react-native-maps/react-native-maps@v1.19.1...v1.20.0) (2024-11-10) ### Features * **android:** add support for disabling PoIClick ([react-native-maps#5210](react-native-maps#5210)) ([d92e283](react-native-maps@d92e283))
## [1.20.1](react-native-maps/react-native-maps@v1.20.0...v1.20.1) (2024-11-22) ### Bug Fixes * **ios:** color update in AIRGoogleMap ([react-native-maps#5227](react-native-maps#5227)) ([f445546](react-native-maps@f445546))
![semgrep-code-pbsc-go-lcs-scandocs[bot]](https://avatars.githubusercontent.com/u/4398249?s=60&v=4){kind=small}
| // Shared values for latitude and longitude | ||
| const latitude = useSharedValue(LATITUDE); | ||
| const longitude = useSharedValue(LONGITUDE); | ||
| class AnimatedMarkers extends React.Component<any, any> { |
There was a problem hiding this comment.
Semgrep identified an issue in your code:
class component usage is deprecated. Please use functional components instead.
To resolve this comment:
🔧 No guidance has been designated for this issue. Fix according to your organization's approved methods.
💬 Ignore this finding
Reply with Semgrep commands to ignore this finding.
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by no-class-components.
You can view more details about this finding in the Semgrep AppSec Platform.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
20 participants
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.
Uh oh!
There was an error while loading. Please reload this page.