[Feature request] Missing MapView camera change event listeners in the Navigation SDK for React Native
Maintainer antworten meist innerhalb von 5 Tagen
@illuminati1911 arbeitet bereits daran.
Seit 16.7.2025.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
Is there an existing issue for this?
- I have searched the existing issues
Description of the bug
I'm trying to detect camera movement events (e.g. onCameraIdle, onCameraMove) using the Navigation SDK for React Native, but these listeners don't appear to be exposed in the current version. I’ve checked the documentation and tried using mapViewCallbacks, but no camera-related events are triggered.
Would it be possible to expose these listeners or provide an alternative way to track camera changes?
React Native version
0.73.6
React version
18.2.0
Package version
0.9.3
Native SDK versions
- I haven't changed the version of the native SDKs
React Native Doctor Output
$ npx react-native doctor
⠴ Running diagnostics...'"adb"' is not recognized as an internal or external command,
operable program or batch file.
Common
✓ Node.js - Required to execute JavaScript code
✓ npm - Required to install NPM dependencies
● Metro - Metro Bundler is not running
Android
✖ Adb - No devices and/or emulators connected. Please create emulator with Android Studio or connect Android device.
✖ JDK - Required to compile Java code
- Version found: 11.0.16.1
- Version supported: >= 17 <= 20
✖ Android Studio - Required for building and installing your app on Android
✖ ANDROID_HOME - Environment variable that points to your Android SDK installation
✓ Gradlew - Build tool required for Android builds
✖ Android SDK - Required for building and installing your app on Android - Versions found: N/A
- Version supported: .b34.0.0
Errors: 5
Warnings: 1
Steps to reproduce
Add a component to your screen.
- Pass the following mapViewCallbacks:
<MapView
mapViewCallbacks={{
onCameraMoveStarted: (reason) => {
console.log('Camera move started:', reason);
},
onCameraMove: () => {
console.log('Camera is moving');
},
onCameraIdle: () => {
console.log('Camera is idle');
},
}}
onMapViewControllerCreated={setMapViewController}
/>
-
Interact with the map by dragging or zooming.
-
Observe the console
Expected vs Actual Behavior
<MapView
mapViewCallbacks={{
onCameraMoveStarted: (reason) => {
console.log('Camera move started:', reason);
},
onCameraMove: () => {
console.log('Camera is moving');
},
onCameraIdle: () => {
console.log('Camera is idle');
},
}}
onMapViewControllerCreated={setMapViewController}
/>
The following logs should be printed during user interaction:
- Camera move started: [reason]
- Camera is moving
- Camera is idle
Code Sample
<MapView
mapViewCallbacks={{
onCameraMoveStarted: (reason) => {
console.log('Camera move started:', reason);
},
onCameraMove: () => {
console.log('Camera is moving');
},
onCameraIdle: () => {
console.log('Camera is idle');
},
}}
onMapViewControllerCreated={setMapViewController}
/>
Additional Context
No response
- Vorherrschende Sprache
- TypeScript
- Sterne
- 226
- Forks
- 39
- Ø Merge
- 1 T. 20 Std.
- Gemergte PRs (30 T.)
- 7
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus googlemaps/react-native-navigation-sdk
-
[Support Request]: Status of Expo config plugin release (prebuild fails on 0.19.0)Evtl. vergeben @jokerttu hat das vor 1 Tag übernommen. Offen
googlemaps/react-native-navigation-sdk#711 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen
-
[Bug]: In-navigation notification can't be stoppedEvtl. vergeben @jokerttu hat das vor 8 Tagen übernommen. Offentriage me type: bug
googlemaps/react-native-navigation-sdk#696 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen
-
[Bug]: [iOS] Navigation SDK init/quota retry loop pins the main thread; React Native's Settings module and addMarker's temporary GMSMarker add to the costEvtl. vergeben @illuminati1911 hat das vor 14 Tagen übernommen. Offentriage me type: bug
googlemaps/react-native-navigation-sdk#687 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen
-
[Bug]: iOS crash in GMSObjectDataCache Core Data save (fatal optimistic locking failure)Evtl. wieder frei @illuminati1911 hat das vor 60 Tagen übernommen, und es ist kein Pull Request offen. Offennative sdk issue
googlemaps/react-native-navigation-sdk#647 · 1 Kommentar · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen
-
[Bug]: CarPlay map view never sets GMSMapViewOptions.screen, so the navigation header and footer are sized for the phoneEvtl. wieder frei @jokerttu hat das vor 73 Tagen übernommen, und es ist kein Pull Request offen. Offen
googlemaps/react-native-navigation-sdk#640 · 4 Kommentare · 1 Reaktion · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen
Alle Issues in googlemaps/react-native-navigation-sdk
Ähnliche Issues
-
pending close triaging
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 74/100
anomalyco/opencode#63090 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
ai-driven-qa bug claude Cosmetic
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
ai-driven-qa bug claude Minor
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
linagora/twake-mail-admin#609 ·
Maintainer antworten meist innerhalb von 1 Tag