[Help Wanted]: Offline GPS Pulses Are No Longer Being Stored in Flutter Implementation

[Macarena000]

Required Reading

• Confirmed

Plugin Version

flutter_background_geolocation: ^4.13.3

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

all

Device operating-systems(s)

all

What do you require assistance about?

Hello Transistor Software team,

We previously purchased the plug-in and successfully used the offline storage of GPS pulses feature in our Flutter application. However, we recently identified that the application is no longer storing location pulses when the device is offline.

We have not made intentional changes related to location persistence, so we would like to understand what could be causing this behavior and whether there are new configuration requirements or updates necessary.

Environment

Framework: Flutter

Platforms: Android / iOS

Plug-in version: flutter_background_geolocation: ^4.13.3

Device models: All

OS versions: All

Expected Behavior

Location pulses should be stored locally when the device is offline.

Once connectivity is restored, pulses should sync normally.

Actual Behavior

Location pulses are not being saved offline.

No pending records appear to be queued or uploaded after reconnection.

Steps to Reproduce

Run the application using the plugin with offline storage enabled.

Disable internet connectivity.

Generate GPS movement/pulses.

Re-enable connectivity.

Observe that no pulses have been stored or synced.

Additional Information

Please let us know if there were recent changes to the plug-in related to offline persistence or if additional setup is now required.
We are happy to provide logs or any other detail needed.

Thank you for your support.

[Optional] Plugin Code and/or Config

[Optional] Relevant log output

[christocracy]

You must provide your Config and logs.

See wiki "Debugging" and api docs ".emailLog". Learn to monitor your logs.

[Macarena000]

@christocracy

url: ${Constants.hostAppDrivers}/gps
headers.Authorization: Bearer
method: POST
httpRootProperty: coords
locationTemplate: {"lat":<%= latitude %>, "lng":<%= longitude %>, "dateEventGps":"<%= timestamp %>", "velocity":<%= speed %>}
autoSync: true
batchSync: true
maxBatchSize: 20
maxDaysToPersist: 1
persistMode: Config.PERSIST_MODE_LOCATION
desiredAccuracy: Config.DESIRED_ACCURACY_HIGH
logLevel: Config.LOG_LEVEL_VERBOSE
debug: false

[christocracy]

flutter_background_geolocation: ^4.13.3

You're using a version from over 2 years ago

See Wiki "Debugging" and learn to observe your logs. See API docs ".emailLog".

[Macarena000]

Hello,

That was indeed the version we had installed, but we updated to the latest one as you suggested and the issue still persists.

Could you please confirm if there are any configuration changes or new parameters introduced in the recent versions that we should be aware of? We want to ensure our setup aligns with the current requirements of the plugin.

Thank you.

[christocracy]

You must learn to observe logs from this plugin. When something unusual happens, the first thing to do is fetch and analyze the logs:

See Wiki "Debugging" and learn to observe your logs. See API docs ".emailLog".

[Macarena000]

12-05 13:45:36.489 DEBUG [LoggerFacade$a a] com.transistorsoft/flutter_background_geolocation/events/location
12-05 13:45:36.489 DEBUG [TSSQLiteAppender$c run]
ℹ️ Cleared logs older than 72 hours
12-05 13:46:28.217 DEBUG [TSConfig e] ℹ️ Persist config, dirty: [autoSync, batchSync]
12-05 13:46:49.970 DEBUG [TSConfig e] ℹ️ Persist config, dirty: [autoSync]
12-05 13:46:49.973 DEBUG [SQLiteLocationDAO destroyAll]
✅ DELETED: (0)
12-05 13:46:52.599 DEBUG [LifecycleManager onPause] ☯️ onPause
12-05 13:46:54.007 DEBUG [LifecycleManager onResume] ☯️ onResume
12-05 13:47:01.439 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 1 (146944ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0 {Bundle[{battery_level=1.0, is_charging=true, odometer=0.0}]}], time: 1764960274495

12-05 13:47:01.568 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:47:01.569 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:47:01.572 INFO [SQLiteLocationDAO persist]
✅ INSERT: c21532c6-1d6b-49e7-a555-4fd12b696180
12-05 13:47:04.329 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 2 (149835ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:47:04.356 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:47:04.356 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:47:04.359 INFO [SQLiteLocationDAO persist]
✅ INSERT: 24c3cd12-75e9-41ab-80ef-e6408f440b29
12-05 13:47:05.087 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 3 (150593ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:47:05.114 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:47:05.114 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:47:05.118 INFO [SQLiteLocationDAO persist]
✅ INSERT: 61ddae4f-89fa-4a91-869f-6e0b43a99574
12-05 13:47:05.503 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 4 (151008ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:47:05.504 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:47:05.504 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:47:05.508 INFO [SQLiteLocationDAO persist]
✅ INSERT: 1bd76e21-f6b3-4970-b8ac-ea55327ca16b
12-05 13:47:05.973 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 5 (151479ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:47:05.974 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:47:05.974 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:47:05.978 INFO [SQLiteLocationDAO persist]
✅ INSERT: b63f81a1-ffce-4096-b86b-36ccdd4b0569
12-05 13:47:07.050 DEBUG [TSConfig e] ℹ️ Persist config, dirty: [autoSync]
12-05 13:47:32.154 DEBUG [LifecycleManager onPause] ☯️ onPause
12-05 13:47:32.154 DEBUG [LifecycleManager onStop] ☯️ onStop
12-05 13:47:34.253 DEBUG [LifecycleManager onStart] ☯️ onStart
12-05 13:47:34.259 DEBUG [LifecycleManager onResume] ☯️ onResume
12-05 13:47:49.812 DEBUG [LifecycleManager onPause] ☯️ onPause
12-05 13:47:53.821 DEBUG [LifecycleManager onStop] ☯️ onStop
12-05 13:51:58.343 DEBUG [LifecycleManager onStart] ☯️ onStart
12-05 13:51:58.346 DEBUG [LifecycleManager onResume] ☯️ onResume
12-05 13:52:44.818 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 6 (490324ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:52:44.850 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:52:44.850 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:52:44.857 INFO [SQLiteLocationDAO persist]
✅ INSERT: 7cb4560a-eb4e-4e19-9d8c-5b66d4d12cd1
12-05 13:52:45.644 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 7 (491150ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:52:45.672 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:52:45.672 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:52:45.677 INFO [SQLiteLocationDAO persist]
✅ INSERT: 25b5b176-2d35-42ea-9734-20d2ef7d8863
12-05 13:52:45.871 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 8 (491376ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:52:45.872 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:52:45.872 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:52:45.876 INFO [SQLiteLocationDAO persist]
✅ INSERT: b179b02b-ccd7-4a53-8cb6-615057d9719a
12-05 13:52:46.078 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 9 (491584ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:52:46.079 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:52:46.079 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:52:46.082 INFO [SQLiteLocationDAO persist]
✅ INSERT: ca192211-5830-4d55-a363-e8c7fe5b0881
12-05 13:52:46.286 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 10 (491792ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:52:46.287 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:52:46.288 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:52:46.291 INFO [SQLiteLocationDAO persist]
✅ INSERT: 672328ee-781e-46b8-9502-8d6403304138
12-05 13:52:46.786 INFO [TSLocationManager a]
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 11 (492291ms old)
╠═════════════════════════════════════════════
╟─ 📍 Location[fused 6.145878,-75.627372 hAcc=23.776 et=+3m8s949ms alt=1669.9000244140625 vAcc=10.850224 vel=0.12534046 sAcc=1.5 bear=110.921074 bAcc=45.0], time: 1764960274495

12-05 13:52:46.787 INFO [TSLocationManager onSingleLocationResult]
🔵 Acquired current position
12-05 13:52:46.787 DEBUG [TSLocationManager a] Median accuracy: 23.776
12-05 13:52:46.791 INFO [SQLiteLocationDAO persist]
✅ INSERT: b8ec860f-11fb-434d-bf29-cb2a5ed1043f
12-05 13:52:48.375 DEBUG [TSConfig e] ℹ️ Persist config, dirty: [autoSync]
12-05 13:52:48.380 DEBUG [SQLiteLocationDAO destroyAll]
✅ DELETED: (11)

[christocracy]

That's only 7 minutes worth of logs, repeatedly calling .getCurrentPosition.

Learn to use the .emailLog method (see API docs). the plugin holds up to 3 days worth of logs. You should be going outside to do field-testing, gathering logs.

[Macarena000]

Hello,

We have already performed proper field testing as suggested, including real outdoor movement with the device offline, and collected logs using the .emailLog() method. Despite this, GPS pulses are still not being captured or stored while the device is offline.

At this point, we would like to ask if there is any additional configuration, recommended option, or alternative approach we should be using to ensure offline location persistence works as expected in the current versions of the plugin.

If there is a more effective way to receive support for this specific issue, please let us know how to proceed.

Thank you for your assistance.

[christocracy]

I do all my Android testing on devices with no SIM card (ie offline). When my test devices arrive back at the office, they sync their queued locations once a wifi connection is established.

There are no special Config options to do this (other than autoSync: true).

For Android devices, see https://dontkillmyapp.com.

Also, you have not yet provided a significant amount of logs (eg 3 days worth, with multiple field tests).