React-native-background-geolocation: Background service stop working when app is killed

[karimkhamwani]

Your Environment

• Plugin version:
• Platform: iOS or Android
• OS version:
• Device manufacturer and model:
  
• Running in Simulator:
• React Native version:
• Plugin configuration options:
• Link to your project:

Context

Expected Behavior

Actual Behavior

Possible Fix

Steps to Reproduce

1.
2.
3.
4.

Context

Debug logs

[karimkhamwani]

BackgroundGeolocation.configure({
  desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
  stationaryRadius: 50,
  distanceFilter: 50,
  debug: true,
  startOnBoot: true,
  stopOnTerminate : false,
  locationProvider: BackgroundGeolocation.ACTIVITY_PROVIDER,
  interval: 1000,
  fastestInterval: 5000,
  activitiesInterval: 1000,
  stopOnStillActivity: false
});

[eacbkk]

I implemented react headless js to work around this...

https://github.com/eacbkk/react-native-background-geolocation

Here's what you need to do:
https://github.com/eacbkk/react-native-background-geolocation#react-android-headless-location-service-experimental

Here is the commit:
https://github.com/eacbkk/react-native-background-geolocation/commit/8e0645588b7e950e6abadd8808523506ebca11c5

@mauron85 This could be useful. would you consider adding this feature?

[karimkhamwani]

@eacbkk thanks for reply
After implementing this it's working in background when app is kill but i see multiple logs of it, instead of one log
componentWillMount(){
AppRegistry.registerHeadlessTask('RNLocationHeadlessService', () => this.locationHeadlessService);
}

locationHeadlessService = async (location) => {
console.log(location , "kia scene ha");
return Promise.resolve();
};

[eacbkk]

It's because you've put the AppRegistry.registerHeadlessTask in componentwillmount. It should go to your indexjs where you register the React application. Search for AppRegistry.registerComponent in your source. you have to put AppRegistry.registerHeadlessTask on the same place.

[karimkhamwani]

@eacbkk how should i able to update the state then?

[mauron85]

@eacbkk is your experimental branch replacing my impl of headless with react native headless version? If so feel free to push PR, so I wont loose track of this.

[karimkhamwani]

@mauron85 i have test this commit it works great.

[karimkhamwani]

@eacbkk ^^^ ?

[eacbkk]

@mauron85 it does not replace it. Because 'background-geolocation-android' currently doesn't have React as a dependency. My implementation is on 'react-native-background-geolocation'. If you think it's okay to include react as a dependency in that layer, I can look into replacing that.

[eacbkk]

@eacbkk how should i able to update the state then?

your headless implementation shouldn't be used to update ui state... It doesn't work when UI is visible. It's only for background operation.

[karimkhamwani]

@eacbkk even i place code in root file still getting multiple logs.
import { AppRegistry } from 'react-native';
import App from './App';
import { name as appName } from './app.json';

/* call the endpoint in background */
locationHeadlessService = async location => {
console.log(location, 'kia scene ha');
return Promise.resolve();
};

AppRegistry.registerHeadlessTask(
'RNLocationHeadlessService',
() => this.locationHeadlessService,
);

AppRegistry.registerComponent(appName, () => App);

[karimkhamwani]

@eacbkk I was calling background.start() multiple times that why multiple logs happens

[karimkhamwani]

@eacbkk is there any way to de register headlesstask
AppRegistry.registerHeadlessTask('RNLocationHeadlessService', () => this.locationHeadlessService);

[eacbkk]

@eacbkk is there any way to de register headlesstask
AppRegistry.registerHeadlessTask('RNLocationHeadlessService', () => this.locationHeadlessService);

what's the use case. I don't believe react native supports deregistering.

[karimkhamwani]

@eacbkk I'm working on live tracking app, i want to use background location only when rides starts and stop using background location when rides ends.

[eacbkk]

@eacbkk I'm working on live tracking app, i want to use background location only when rides starts and stop using background location when rides ends.

Yah. But why would you need to de-register the headless service? Calling the stop function should suffice. If you don't want to do that, check for some condition in your js function I guess.

[hadnazzar]

@eacbkk i tried your commit and it works as expected. I used registerHeadlessTask at the componentDidMount

  componentDidMount() {
    console.log('map did mount');
    AppRegistry.registerHeadlessTask('RNLocationHeadlessService', () => this.locationHeadlessService);

I think you can create pull request about it because otherwise it does not work when app is killed.

[Saqib92]

Do we have better solution or still going for @eacbkk workaround?

[kevinzDzul]

I implemented react headless js to work around this...

https://github.com/eacbkk/react-native-background-geolocation

Here's what you need to do:
https://github.com/eacbkk/react-native-background-geolocation#react-android-headless-location-service-experimental

Here is the commit:
eacbkk@8e06455

@mauron85 This could be useful. would you consider adding this feature?

is possible in IOS ?

[eacbkk]

@mauron85 do you think we can integrate the implementation? It has been in my production application for the last few months. And I can report it has been working great. The only catch is I need to include the react-native library in the android commons project.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed, because it has not had recent activity. If you believe this issue shouldn't be closed, please reopen or write down a comment requesting issue reopening with explanation why you think it's important. Thank you for your contributions.

[littlehome-eugene]

to revive this..

@eacbkk is your experimental branch replacing my impl of headless with react native headless version? If so feel free to push PR, so I wont loose track of this.

I don't see PR in the list ? @eacbkk

[littlehome-eugene]

@eacbkk
Thanks for the patch (https://github.com/eacbkk/react-native-background-geolocation/commit/8e0645588b7e950e6abadd8808523506ebca11c5)

I've managed to run it fine.

However I find sometime the headless task is not called out of sudden , I find restarting app a few times fixes the problem.

Has anyone encountered such problem?

[rosnaib11]

Why on me, headless task only work once. If I close the app for second time headless task does not work anymore.

[rosnaib11]

Sorry my bad, the problem I guess was I keep calling BackgroundGeolocation.stop();. on componentWillUnmount followed by BackgroundGeolocation.start();. The listener might not rebinding, when I remove .stop() it works

[lyseiha]

After call BackgroundGeolocation.stop(); and then i call BackgroundGeolocation.start(); headlesstask won't start again.

[lyseiha]

I implemented react headless js to work around this...

https://github.com/eacbkk/react-native-background-geolocation

Here's what you need to do:
https://github.com/eacbkk/react-native-background-geolocation#react-android-headless-location-service-experimental

Here is the commit:
eacbkk@8e06455

@mauron85 This could be useful. would you consider adding this feature?

It stop working when clear all app from recently. but in few minute foreground notification pop up and i debug in android studio location still update but headlesstask not working.

[rosnaib11]

@eacbkk is it necessary to perform stuff inside headlesssLocationService.js file? Because I'm sending my data directly through url parameter. If my app is terminated, headlesssLocationService.js works. But at the same time my BackgroundGeolocation.configure settings also working.

My headlessLocationService.js. This works if I terminate the app

export default async (Location) => {
  console.log(location);
  // do something here
  return Promise.resolve()
}

But at the same time this also working if I terminate the app.

BackgroundGeolocation.configure({
      desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
      stationaryRadius: 5,
      distanceFilter: 5,
      notificationTitle: 'Trackme GPS Tracking',
      notificationText: 'Enabled',
      notificationIconColor: '#3D80E5',
      notificationsEnabled: true,
      debug: true,
      startOnBoot: false,
      stopOnTerminate: false,
      locationProvider: BackgroundGeolocation.ACTIVITY_PROVIDER,
      interval: interval,
      fastestInterval: 5000,
      activitiesInterval: 5000,
      stopOnStillActivity: false,
      url: `${Config.API_DEV}/api/services/location`,
      syncUrl: `${Config.API_DEV}/api/services/sync_location`,
      syncThreshold: 100,
      httpHeaders: {
        Accept: 'application/json',
        'Content-Type': 'application/json',
      },
      // customize post properties
      postTemplate: {
        id: '@id',
        lat: '@latitude',
        lon: '@longitude',
        gps_time: '@time',
        speed: '@speed',
        bearing: '@bearing',
        altitude: '@altitude',
        accuracy: '@accuracy',

        macaddress: data ? data.macaddress : null,
        objectid: data ? data.objectid : null,
        statusDesc: this.appstate,
      },
    })

Which one should I follow?