watchLocation and getCurrentPosition usage conflicts

Hi, I am using both features of your package, watchLocation to detect when I am going to far from a reference position, in background, with low battery consumption, and getCurrentPosition from time to time to get an update of my current location (either in foreground or in background).

My issue is that it seems that the options I am using for the watch are overriden by my getPosition call (especially distanceFilter for example) and so my watch becomes crazy after the first getCurrentPositionCall as it does not take a significant filter after.

Is there a way to use both calls without the options being shared?

Thanks for your help.

Watch setup (once for all):

const watchId = Geolocation.watchPosition(
      (position) => {
        console.log('Geolocation new position:', position);
      },
      (error) => {
        console.log('Geolocation error:', error.message);
      },
      {
        timeout: 15000,
        maximumAge: 10000,
        enableHighAccuracy: true,
        distanceFilter: 50,
        interval: 60000,
        forceRequestLocation: true
      },
    );

Get Current Position (sometimes in either foreground or background):

Geolocation.getCurrentPosition(
          position => {
            console.log('position', position);
          },
          error => {
            console.warn('Location error:', error.message);
          },
          {
            timeout: 15000,
            maximumAge: 0,
            enableHighAccuracy: true,
            distanceFilter: 0,
            forceRequestLocation: true,
          },
        );

[Agontuk]

@OlivierVoyer, I’m trying to implement my own iOS module right now. I’ll try to solve this issue in my implementation. Let me know if you’re willing to test it, and your current xcode & RN version. You can track the progress here https://github.com/Agontuk/react-native-geolocation-service/issues/173.

I’ll update the setup instructions soon.

[OlivierVoyer]

v5.0.0 is fixing the main issue I described in this thread. Thanks @Agontuk