onLocationChanged event stop firing in backgound

[dukizwe]

The onLocationChanged event triggers correctly when the app is in the foreground. However, when the app goes into the background, the event no longer fires.

According to the documentation, to ensure that the service continues running in the background, you need to set the taskRemovedBehavior property to TaskRemovedBehavior.CONTINUE_SERVICE.

I would like to confirm whether this is the default behavior or if additional adjustments are needed to make the event trigger while the app is in the background.

Platform: Android

[jokerttu]

@dukizwe Thank you for reporting this issue.

@illuminati1911 Could you please take a look?
Since TaskRemovedBehavior.CONTINUE_SERVICE is the default behavior, events should trigger while the app is in the background.

[illuminati1911]

The onLocationChanged event triggers correctly when the app is in the foreground. However, when the app goes into the background, the event no longer fires.

According to the documentation, to ensure that the service continues running in the background, you need to set the taskRemovedBehavior property to TaskRemovedBehavior.CONTINUE_SERVICE.

I would like to confirm whether this is the default behavior or if additional adjustments are needed to make the event trigger while the app is in the background.

Platform: Android

Hey @dukizwe.

It is the default behavior and there shouldn't be a need to do anything else assuming you have started the location updates in the app. Could you test our example app and see if you face the same issue there as well?

[dukizwe]

I tested the example app, and it works perfectly. I discovered that the issue arises from the debounce code I use inside the event to prevent multiple calls. I couldn’t find a way to properly configure the interval and fastestInterval settings:

import debounce from 'lodash.debounce';
import throttle from 'lodash.throttle';

const onLocationChanged = useCallback(
   debounce(
      throttle(location => {
         console.log("onLocationChanged")
      }, 5000),
      900
   ),
   [] // Ensure this callback is stable and not recreated
);

this works perfectly in foreground but not in background