react-native-background-geolocation: The location state doesn't change from stationary to isMoving

Your Environment

  • Plugin version:
  • Platform: Android
  • OS version: 12 & 13
  • Device manufacturer / model: Motorola & Xiaomi
  • React Native version: 0.72.4
  • Plugin config
    desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
    distanceFilter: 0,
    stopTimeout: 14,
    debug: false,
    logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
    stopOnTerminate: false,
    startOnBoot: true,
    batchSync: false,
    locationUpdateInterval: 1000,
    fastestLocationUpdateInterval: 1000,
    triggerActivities: 'in_vehicle, on_bicycle',
    isMoving: true,
    // disableStopDetection: true,
    allowIdenticalLocations: false,
    enableHeadless: true,

Expected Behavior

The device is moving it works fine, then stops for several minutes(10 minutes or more). the device starts to move, the “stationary” should change to “isMoving” and I should be able to track the location again.

Actual Behavior

The device is moving it works fine, then stops for several minutes(10 minutes or more). the device starts to move, but the location does not change. I have to reopen the App or move it to the foreground to be able to track the location.

Steps to Reproduce

  1. call BackgroundGeolocation.start();
  2. call BackgroundGeolocation.changePace(true);
  3. close/move the app to the background
  4. start to move the device
  5. stop moving the device
  6. wait for 10 minutes or more
  7. track the location, which does not update on the map

Context

This App is for tracking some vehicles and we are trying to find where they stop and then start to move. Drivers can’t work with the App while driving. they can just enable it at first and stop it at the end I used “enableHeadless”, which improves the condition, but the issue remains. I have purchased the license key.

About this issue

  • Original URL
  • State: closed
  • Created 7 months ago
  • Comments: 18 (7 by maintainers)

Most upvoted comments

Can it help to solve the issue?

No. Your issue is likely specifically related to your device.

Go outside and field-test. Analyze your logs.