Skip to content

Conversation

@jokerttu
Copy link
Contributor

@jokerttu jokerttu commented Dec 5, 2025

Fixes two critical iOS bugs preventing Fleet Engine location reporting:

  1. Fixed module export names to match JavaScript expectations

    • Changed RCTDeliveryDriverModule -> DeliveryDriverModule
    • Changed RCTRideSharingModule -> RideSharingModule
    • JavaScript code expects NativeModules.DeliveryDriverModule, not RCTDeliveryDriverModule
  2. Fixed event dispatcher initialization to enable event emission

    • Added startObserving() call after allocating DriverEventDispatcher
    • Without this, hasListeners remained false and all events were silently dropped
    • Affects didSucceedVehicleUpdate and didFailVehicleUpdate events

Fixes #70

It's a good idea to open an issue first for discussion.

  • Tests pass
  • Appropriate changes to documentation are included in the PR

@jokerttu jokerttu force-pushed the fix/ios-fleet-engine-location-reporting branch from 74f4658 to 3c8e10c Compare December 8, 2025 14:44
Fixes two critical iOS bugs preventing Fleet Engine location reporting:

1. Fixed module export names to match JavaScript expectations
   - Changed RCTDeliveryDriverModule -> DeliveryDriverModule
   - Changed RCTRideSharingModule -> RideSharingModule
   - JavaScript code expects NativeModules.DeliveryDriverModule, not RCTDeliveryDriverModule

2. Fixed event dispatcher initialization to enable event emission
   - Added startObserving() call after allocating DriverEventDispatcher
   - Without this, hasListeners remained false and all events were silently dropped
   - Affects didSucceedVehicleUpdate and didFailVehicleUpdate events

These changes enable proper location reporting to Fleet Engine on iOS,
achieving parity with the Android implementation.

Fixes #70
@jokerttu jokerttu force-pushed the fix/ios-fleet-engine-location-reporting branch from 3c8e10c to 894efcf Compare December 18, 2025 11:32
@jokerttu jokerttu marked this pull request as ready for review December 18, 2025 11:41
Copy link
Contributor

@illuminati1911 illuminati1911 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but are those yarn.lock changes intentional?

@jokerttu
Copy link
Contributor Author

LGTM but are those yarn.lock changes intentional?

It's fine to upgrade the dependencies to yarn.lock time to time.
These are mostly for development purposes.
This is locking to the latest navigation sdk here: https://github.com/googlemaps/react-native-driver-sdk/pull/74/changes#diff-51e4f558fae534656963876761c95b83b6ef5da5103c4adef6768219ed76c2deR1833

@jokerttu jokerttu merged commit 0bd12f1 into main Dec 19, 2025
21 of 22 checks passed
@jokerttu jokerttu deleted the fix/ios-fleet-engine-location-reporting branch December 22, 2025 12:50
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.

[iOS] Multiple issues preventing Fleet Engine location reporting

3 participants