[Bug]: iOS Geofencing stops when force killing the app

[rick-hl]

Required Reading

• Confirmed

Plugin Version

5.0.5

Flutter Doctor

[!] Flutter (Channel [user-branch], 3.27.0, on macOS 26.2 25C56 darwin-arm64, locale en-PH)
    ! Flutter version 3.27.0 on channel [user-branch] at /Users/k/Documents/GitHub/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0)
[✓] Xcode - develop for iOS and macOS (Xcode 26.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2025.1)
[✓] VS Code (version 1.109.5)
[✓] Connected device (4 available)
    ! Error: Browsing on the local area network for Rick KrystianneのiPad. Ensure the device is unlocked and attached
      with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

! Doctor found issues in 1 category.

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

iPhone 12 mini

Device operating-systems(s)

iOS 26

What happened?

There are no location data sent to our server when force killing the app in iOS.

Tested the app while driving. Minimizing the app works fine.

        <key>UIBackgroundModes</key>
	<array>
		<string>fetch</string>
		<string>location</string>
	</array>

Plugin Code and/or Config

bg.Config(
          debug: DevUtils.showTrackingDebugging,
          minimumActivityRecognitionConfidence: 50,
          locationTimeout: 120,
          distanceFilter: 300.0,
          startOnBoot: false,
          stopOnTerminate: false,
          httpRootProperty: '.',
          locationsOrderDirection: 'ASC',
          logLevel: DevUtils.showTrackingDebugging
              ? bg.Config.LOG_LEVEL_DEBUG
              : bg.Config.LOG_LEVEL_OFF,
          desiredAccuracy: Platform.isIOS
              ? bg.Config.DESIRED_ACCURACY_NAVIGATION
              : bg.Config.DESIRED_ACCURACY_HIGH,
          locationTemplate:
              '{"Latitude":"<%= latitude %>", "Longitude":"<%= longitude %>", "Timestamp":"<%= timestamp %>", "BatteryLevel":"<%= battery.level %>", "IsCharging":"<%= battery.is_charging %>", "PollEvent":"<%= event %>"}',
          headers: {
            ...
            ...
          },
          activityType: bg.Config.ACTIVITY_TYPE_AUTOMOTIVE_NAVIGATION,
          logMaxDays: 3,
          maxDaysToPersist: 14,
          maxRecordsToPersist: -1,
          autoSync: true,
          url: '$baseUrl${Endpoints.tracking}',
          disableElasticity: true,
          disableLocationAuthorizationAlert: true,
          backgroundPermissionRationale: bg.PermissionRationale(
            title: Strings.permissionAndroidRationaleTitle,
            message: Strings.permissionAndroidRationaleCaption,
          ),
          // No activity sensor usage
          disableMotionActivityUpdates: true,
        ),

Relevant log output

[hramadan-si]

@christocracy

kindly need solution for this issue, also we have same issue, need solution ASAP

[christocracy]

Geofencing does not stop after terminating the app. This is easily verified in the iOS simulator with "Freeway Drive"

[rick-hl]

Geofencing does not stop after terminating the app. This is easily verified in the iOS simulator with "Freeway Drive"

@christocracy

Any idea why we're not receiving the location data in our backend when app is terminated?

[christocracy]

Ensure your app is calling BackgroundGeolocation.ready(config) each and every time your app launches, no matter what.

Test your app with debug: true and LogLevel.verbose in the iOS simulator with Freeway Drive.

See Wiki "Debugging" and learn to fetch plugin logs using .emailLog method.

[christocracy]

5.0.5

You say you're using v5 but you've not migrated your Config to the new compound-style

bg.Config(
debug: DevUtils.showTrackingDebugging,
minimumActivityRecognitionConfidence: 50,
locationTimeout: 120,
distanceFilter: 300.0,
startOnBoot: false,
stopOnTerminate: false,
httpRootProperty: '.',
locationsOrderDirection: 'ASC',
logLevel: DevUtils.showTrackingDebugging
? bg.Config.LOG_LEVEL_DEBUG
: bg.Config.LOG_LEVEL_OFF,
desiredAccuracy: Platform.isIOS
? bg.Config.DESIRED_ACCURACY_NAVIGATION
: bg.Config.DESIRED_ACCURACY_HIGH,
locationTemplate:
'{"Latitude":"<%= latitude %>", "Longitude":"<%= longitude %>", "Timestamp":"<%= timestamp %>", "BatteryLevel":"<%= battery.level %>", "IsCharging":"<%= battery.is_charging %>", "PollEvent":"<%= event %>"}',
headers: {
...
...
},
activityType: bg.Config.ACTIVITY_TYPE_AUTOMOTIVE_NAVIGATION,
logMaxDays: 3,
maxDaysToPersist: 14,
maxRecordsToPersist: -1,
autoSync: true,
url: '$baseUrl${Endpoints.tracking}',
disableElasticity: true,
disableLocationAuthorizationAlert: true,
backgroundPermissionRationale: bg.PermissionRationale(
title: Strings.permissionAndroidRationaleTitle,
message: Strings.permissionAndroidRationaleCaption,
),
// No activity sensor usage
disableMotionActivityUpdates: true,
),

[rick-hl]

@christocracy

I just tried using v5.0.5 to check if similar behavior happens.

Anyways, here's my migrated config.

bg.Config(
          app: bg.AppConfig(
            startOnBoot: false,
            stopOnTerminate: false,
            backgroundPermissionRationale: bg.PermissionRationale(
              title: Strings.permissionAndroidRationaleTitle,
              message: Strings.permissionAndroidRationaleCaption,
            ),
          ),
          activity: const bg.ActivityConfig(
            minimumActivityRecognitionConfidence: 50,
            // No activity sensor usage
            disableMotionActivityUpdates: true,
          ),
          geolocation: bg.GeoConfig(
            locationTimeout: 120,
            distanceFilter: 300.0,
            desiredAccuracy: Platform.isIOS
                ? bg.DesiredAccuracy.navigation
                : bg.DesiredAccuracy.high,
            activityType: bg.ActivityType.automotiveNavigation,
            // Makes sure distance filter triggered every xxx meters
            disableElasticity: true,
            disableLocationAuthorizationAlert: true,
          ),
          http: bg.HttpConfig(
            rootProperty: '.',
            headers: {
              Constants.keyGfSecretToken: tokenToUse,
              Constants.keyGfApiKey: apiKey,
            },
            autoSync: true,
            url: '$baseUrl${Endpoints.tracking}',
          ),
          persistence: const bg.PersistenceConfig(
            locationsOrderDirection: 'ASC',
            locationTemplate:
                '{"Latitude":"<%= latitude %>", "Longitude":"<%= longitude %>", "Timestamp":"<%= timestamp %>", "BatteryLevel":"<%= battery.level %>", "IsCharging":"<%= battery.is_charging %>", "PollEvent":"<%= event %>"}',
            maxDaysToPersist: 14,
            maxRecordsToPersist: -1,
          ),
          logger: bg.LoggerConfig(
            debug: DevUtils.showTrackingDebugging,
            logLevel: DevUtils.showTrackingDebugging
                ? bg.LogLevel.debug
                : bg.LogLevel.off,
            logMaxDays: 3,
          ),
        ),

[christocracy]

logLevel: DevUtils.showTrackingDebugging
? bg.LogLevel.debug
: bg.LogLevel.off,

When you have a problem, the first thing to do is LogLevel.verbose and fetch logs using .emailLog