Bug: Constant location access while app is running in background

[dillburt]

Grid 1.0.4 on Android 15

Repro steps:

1. Launch app, note that location icon appears in system status bar at top of screen
2. Navigate to home without closing app (i.e. tap home button, or swipe up if using gestures)
3. Note that location icon remains in status bar constantly. This seems like a bug, and results in high battery usage. Other map-based apps generally request location when opened, then stop requesting if app is put into the background.

For now, the workaround seem to be to remember to exit the app (i.e. back all the way out) when leaving it. This allows the location request to stop.

[chandlergach]

Got it -- It's a bit different/nuance the way Android versus iOS handle background. I thought this would be desired behavior, since you want the app to continue sharing while the phone isn't open, etc.

Do you mind detailing your expected behavior, and what you mean by background (versus terminated)? thanks!

[dillburt]

Background is what I described in step 2, i.e. leave the Grid app without closing it.

My expectation is that when the app is not in the foreground, location requests would be periodic rather than continuous, to reduce battery usage.

[rpicciotti]

I agree that my expectation would be somewhat frequent but periodic access as constant access is a significant battery drain. Though, if possible, I'd also think that if someone else actively opens the app to check my location that that should trigger my phone to update its location. And possibly even constantly keep location up to date for the whole time they're looking at my location.

[chandlergach]

@rpicciotti Absolutely, once we get APN and FCN (push notifs) setup, we plan to implement that functionality.

@dillburt Hmm, if you terminate the app -- it should do exactly that, periodic notifications based off movement. Which is why we have this headless task: https://github.com/Rezivure/Grid-Mobile/blob/main/lib/services/android_background_task.dart

If the app is swiped away (not in foreground but not terminated) it should be movement triggered also. I will look into this - location is fickle especially cross-platform. The goal is to move away from our current location plugin.