Background Location Storage

Hello,

i always get the same error when trying to call getLocations().

Retrieving locations failed code: 21: message: library routine called out of sequence

Here my config

this.backgroundGeolocation.configure(callbackFn, failureFn, {
                desiredAccuracy: 10,
                stationaryRadius:5,
                distanceFilter: 5,
                activityType: 'Other',
                debug: true, 
                stopOnTerminate: false 
            });
            this.backgroundGeolocation.start();

[mauron85]

After some thinking I came to this. Hopefully you will agree on this.

If option.url is not defined, all locations updates are recorded in local db. When App is in foreground or background in addition to storing location in local db, location callback function is triggered. Number of location stored in db is limited by option.maxLocations a never exceeds this number. Instead old locations are replaced by new ones.

When option.url is defined. Location updates are also stored in local db. In addition, each location is also immediately posted to url defined by option.url. If post is successful, the location is marked as deleted in local db. All failed to post locations will be coalesced and send in some time later in one single batch. <TO_BE_DEFINED>Batch sync takes place only as per interval defined in IntervalForBatchSync config option.</TO_BE_DEFINED>.

Is almost same as your suggestion. The difference is that location is stored into db at all times and also when url is set it is also immediately posted to server. Failed to post locations are coalesced and posted as single batch sync.

[mauron85]

Currently no. Sorry. But I will probably release update soon.

If Url option is not defined, all locations updates when App is killed/Background/Foreground are recorded in local db. When App is in foreground or background in addition to storing location in local db, location callback function is triggered.

ok, it will be possible as soon I implement row limit on location table, so old location records will be replaced by newer ones. Without this db can grow very large, because people might tend to forget clean up db with deleteAllLocations…