Question 5216 in Facebook API Question posted in
The official documentation for the Facebook APIs can be found here.

Send Location Updates to Server in Background

What is the best way to keep user’s location in sync with server,even after the app is terminated?
here is what I found this far

  1. using a foreground service. I already tested that but it’s battery consuming, and sometimes it’s killed when you lock the phone or turn off the screen.
  2. using work manager. I also tested it, it sends the location every 15 mins,but so unreliable, and it stopped sending after a while.
  3. Geofencing. I read that Geofencing api gets location updates more often, every couple of minutes or so, but I haven’t tested it.
  4. LocationListener. There is a method called onLocationChanged, but I don’t know how would it work in background.

is there something like a broadcast receiver that will be fired only when location changed by a margin? I think this would be an optimized solution.
I am building an app that uses a feature similar to facebook nearby friends (which is stopped working long time ago) or something like tinder to display nearby people.
Currently I need this for android, but I will need it for IOS as well, I am developing a flutter app.

Tags:

2

Answers


  1. 0

    As discussed in the comments above, I don’t really think Android allows for you to get location updates in the background even when the application is not active.

    I recommend you instead try to query for location as soon as the app starts, and quickly follow up with whatever actions you need to make with it. As an option, you can also keep track of location history by caching their location as they interact with the app, in case you want to keep the database as fresh as possible.

    Here’s some pseudo code as a simple example:

    class MainActivity : AppCompatActivity() {

override fun onCreate(..) {
   queryForLocation(..)?.let {
      doSomething(it)
      cacheLocation(it)
   } ?: Log.d(TAG, "Location = null")
}

override fun onDestroy() {
   queryForLocation(..)?.let {
      cacheLocation(it)
   } ?: Log.d(TAG, "Location = null")
}
    Login or Signup to reply.
  2. 0

    I already used a similar method in my app which is working:

    I used foreground service to record the location, the battery consumptions are related to the frequency of location request not really the foreground service itself. indeed using LocationListener is a good option

    then I am checking the foreground service regularly using workmanager and restart it when needed.

    best

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search