[Help Wanted]: Parallel Execution of Significant Location Monitoring and Geofencing

[safwanidrees]

Required Reading

• Confirmed

Plugin Version

4.18.2

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

iPhone 16

Device operating-systems(s)

iOS 26

What do you require assistance about?

We are using this package for geofencing only. Now we have one question

Can we run significant location change monitoring independently, while also using this package for geofencing, so that the app can be launched by either significant location updates via our integration or geofence events via this package?

Will this create any issues or impact?

[Optional] Plugin Code and/or Config

await _backgroundGeolocation.ready(
        bg.Config(
          notification: bg.Notification(
            channelName: groupChannelName,
            channelId: groupChannelId,
            smallIcon: 'mipmap/ic_launcher',
            title: TextConstants.notificationMainTitle,
            priority: bg.Config.NOTIFICATION_PRIORITY_MIN,
          ),
          locationAuthorizationAlert: {
            'titleWhenNotEnabled': TextConstants.locationServicesDisabled,
            'titleWhenOff': TextConstants.locationServicesDisabled,
            'instructions': TextConstants.pleaseEnableLocationServices,
            'cancelButton': TextConstants.cancel,
            'settingsButton': TextConstants.settings,
          },
          autoSync: false,
          persistMode: bg.Config.PERSIST_MODE_NONE,
          geofenceModeHighAccuracy: true,

          /// Enable it when debugging geofences
          // debug: devToolEnabled,
          debug: AppRunnerMode.instance.isDebugMode,
          logLevel: bg.Config.LOG_LEVEL_VERBOSE,
          geofenceProximityRadius: 2000,
          maxRecordsToPersist: 0,
          locationAuthorizationRequest: 'Always',
          enableHeadless: true,
          stopOnTerminate: false,
          startOnBoot: true,
          geofenceInitialTriggerEntry: true,
          reset: true,
          isMoving: true,
          showsBackgroundLocationIndicator: false,
        ),
      );
      await _backgroundGeolocation.startGeofences();

[Optional] Relevant log output

[christocracy]

See api docs useSignificantChangesOnly

[safwanidrees]

We want to handle significant location changes separately to open the app when it is terminated. For geofencing, I’d like to run this package as it is now, using the current configuration

[christocracy]

useSignificantChangesOnly: true.

Call .start() instead of .startGeofences()

[safwanidrees]

Thanks!

useSignificantChangesOnly: true.

Call .start() instead of .startGeofences()

Enabling useSignificantChangesOnly: true will not affect geofence triggers, geofencing will continue to work as it does today?

Geofencing will not just depend on useSignificantChangesOnly?

useSignificantChangesOnly is only to start the app if it is terminated correct?

Will using both things increase battery consumption and increase the number of locations updated?

Our intent is to rely primarily on geofencing, and use Significant Location Changes only to wake the app if it’s terminated, resulting in fewer location updates and lower battery impact.

[safwanidrees]

@christocracy Could you please clarify this for us? Thanks

[christocracy]

Enabling useSignificantChangesOnly: true will not affect geofence triggers, geofencing will continue to work as it does today?

Yes

Geofencing will not just depend on useSignificantChangesOnly?

They have nothing to do with each other.

useSignificantChangesOnly is only to start the app if it is terminated correct?

No. They have nothing to do with each other.

Will using both things increase battery consumption

No

and increase the number of locations updated?

Do you know what useSignificantChangesOnly does? Read the api docs for detailed description.