[Bug]:

[harryandroiddev]

Required Reading

• Confirmed

Plugin Version

^5.1.1

Flutter Doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.41.6, on macOS 26.3 25D125 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 26.2)
[✓] Chrome - develop for the web
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

iphone 15

Device operating-systems(s)

26.3.1 (a)

What happened?

While tracking location in terminate state the onmotionchange event is not fired when stop the trip .

• Opened the app start the tracking .
• Motion changed event fire for the stationary location and also fetched the location updates .
• Started moving the motion change event fires again with is moving true and start getting location updates while travelling .
• Reached the destination after 1 hour of travelling , the stop timeout notification shown up with 300 s which is default timeout but event after 10 min of time passed the motion update event is not fired in the app .
• Also there is no location turn off notification shown up . just gets the event as onlocation even with moving as true .

Summary : We are syncing the data manually and storing too , so when the tracking start saving location data locally on device, when motion event is fired we sync the remaining data at once . But the event never fires so our data remains in the local storage only .

Plugin Code and/or Config

static Future<void> init() async {
    // 1. Listen for Heartbeats while app is open

    if (Platform.isAndroid) {
      bg.BackgroundGeolocation.onHeartbeat(_handleHearBeat);
    }

    bg.BackgroundGeolocation.onMotionChange(_handleMotionChange);

    bg.BackgroundGeolocation.onLocation(
      _handleLocationChange,
      _handleLocationError,
    );

    // 2. Configure the plugin
    await bg.BackgroundGeolocation.ready(
      bg.Config(
        app: bg.AppConfig(
          backgroundPermissionRationale: bg.PermissionRationale(
            message:
                "Allow background location access so we can track your attendance while the app runs in the background.",
          ),
          stopOnTerminate: false, // Keep service running after swipe-up
          startOnBoot: true, // Start service on phone reboot
          enableHeadless: true, // Enable the HeadlessTask above
          heartbeatInterval: 60, // 1 Minute Heartbeat]
          preventSuspend: false, // For ios only
          notification: bg.Notification(
            title: "Nebero ERP Tracking",
            text: "Location tracking is active",
            color: "#2196F3",
          ),
        ),

        geolocation: bg.GeoConfig(
          locationUpdateInterval: Duration(
            minutes: 10,
          ).inMilliseconds, //Update location on interval Android
          disableElasticity: Platform.isAndroid ? true : false,
          showsBackgroundLocationIndicator: false,
          desiredAccuracy: bg.DesiredAccuracy.high,
          distanceFilter: Platform.isAndroid ? 0 : 50,
        ),
        persistence: bg.PersistenceConfig(persistMode: bg.PersistMode.none),
        activity: bg.ActivityConfig(),
        logger: bg.LoggerConfig(
          debug:
              true, // Plays sound/vibrates on events (turn off for production)
          logLevel: bg.LogLevel.debug,
        ),

        // ─── TIMING ───
      ),
    ).then((bg.State state) {
      debugPrint('[BgLocation] Plugin Ready. Enabled: ${state.enabled}');
    });
  }

Relevant log output

[christocracy]

logger: bg.LoggerConfig(
debug:
true, // Plays sound/vibrates on events (turn off for production)
logLevel: bg.LogLevel.debug,
),

Provide LogLevel.verbose logs.

[harryandroiddev]

bg_logs (1).txt

The location tracking switched off after i opened the app from terminated state again not by itself .

[christocracy]

logger =     {
        debug = 1;
        logLevel = 4;
        logMaxDays = 3;
    };

Provide LogLevel.verbose logs (logLevel: 5)

[christocracy]

I see later in the logs you set LogLevel.verbose.

Why did you terminate the app while the stopTimeout timer was engaged?

2026-04-28 10:25:15.305 🔵 -[TSTrackingService beginStopDetection] Stop-timeout engaged: 300 s...

2026-04-28 10:25:15.305 🟢 -[TSTimerService startWithInterval:repeating:callback:] ⏰ [stopTimeout] Starting timer: 300.00s repeating: 0

2026-04-28 10:25:15.452 📌 🔒 -[TSLocationAuthorization applicationDidBecomeActive] Application became active - refreshing authorization state

2026-04-28 10:25:21.461 🔵 -[TSAppState onEnterBackground] 

2026-04-28 10:25:21.506 🔵 -[TSTrackingService onAppTerminate] stopOnTerminate? 0

If you want to test the stopTimeout, configure stopTimeout: 1 (so you don't have to wait very long).

1. call changePace(true) (to manually place the SDK into the isMoving: true state.)
2. Wait. It doesn't matter if app in foreground or background but DO NOT TERMINATE IT.

[harryandroiddev]

The app was already terminated when the timeout starts but never ends or called the onmotion changed event once reached the destination. So that's why i opened the app to check at that time the stoptimeout started .

Tested again next day , but the issue still persisted .

1. Started the app and also starts the tracking .
2. Terminated the app , Continue stationary notification shows .
3. Started my trip in real environment with real device on my vehicle.
4. Location services turned on after exit the stationary geofence , at 8:47 am (local time india) .
5. Plugin fires location updates till 9:12 . After that there is no tracking records .
6. Reached the destination at 9:27 .
7. No Motion changed event call or stop timeout engaged .
8. I had to open the app inorder to check the logs manually , just got records for the last destination location .
9. Missing the location update records .

Please check the updated logs for more info .

bg_logs (2).txt

At 9:12 i was stopped at traffic light for 1 min approx , but after that i start moving again but location tracking after that was never started .
After 9:13 location tracking stops but i was still on my trip then never tracks the location .
`

2026-04-29 09:13:06.627
╔═══════════════════════════════════════════════════════════
║ -[TSTrackingService onMotionActivityChange:] | still/33 | isMoving: 0
╚═══════════════════════════════════════════════════════════

2026-04-29 09:13:06.627 🔵 -[TSTrackingService onMotionActivityChange:] [StopDetection] Ignored — low confidence: 33 < 70

2026-04-29 09:13:11.746
╔═══════════════════════════════════════════════════════════
║ -[TSTrackingService onMotionActivityChange:] | still/100 | isMoving: 0

`

[christocracy]

I suggest you check your app for crashes (from your own code).

In XCode, Window -> Organizer.

Also, install the /example app in this repo and compare its performance vs your own app.

[harryandroiddev]

OnMotionchanged method is calling when the app is in background or foreground but not in terminate state .

There is no crash detected in the app .

[christocracy]

I think you have a misunderstanding of the iOS app life-cycle.

When you terminate an iOS app, your app and all running code is completely removed from memory.

The only thing that will reawaken it is to move at least 200 meters.

This is fundamentally different from the Android lifecycle which is able to run foreground-services and operate "headless" after app terminate.

[harryandroiddev]

(For terminate state only)
But once we exit the 200 m the app wakes and re run in background , so the tracking starts and location updates coming , but after we reached the destination user stops , stop timeout engaged for 300s . Then the onmotion change event needs to be fire
right ? And has to show the location service off notification .

[christocracy]

As long as the app remains alive after stopTimeout timer expires, onMotionChange is 100% guaranteed to fire.