-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BackgroundGeolocation.onHttp() and the related POST to server stops running #1448
Comments
There have been a number of reports of problems with iOS 15.2 Geofencing & Significant Location Changes APIs from all over the place. The plugin relies on both of these apis in order to determine when the device is moving so it can engage location-tracking. The problem is apparently fixed in iOS 15.4 (beta). I have a number of users of my Cordova, Capacitor, Flutter and React Native version who have confirmed that installing iOS 15.4 fixes their issues. |
I don't know if that's what you're experiencing. If there is a location recorded and the plugin has an HTTP connection, an http request will be attempted. The plugin will keep attempting to upload all recorded locations until a network connection does become available. The plugin does not "just stop uploading locations" for no reason, even while it continues to record locations. |
I suggest you fetch logs from the plugin (using the |
If I do this BackgroundGeolocation.logger.emailLog('foo@bar.com').then((success) => {
console.log('[emailLog] SUCCESS');
}).catch((error) => {
console.log('[emailLog] ERROR: ', error);
}); Is it using their email? LIke their outbox would show them the email? I ask because of the TOS and privacy whatnot, we may or may not have that email, and are not looking to data-mine people. As far as:
This seems to be half what happened this morning. Basically, a bunch of points are bulk posted. Then it stopped. Then when you turn to track back on, it looks like it then tried to post all the ones it did not, or was not. The BE went a little nuts for a few min why that happen. Basically need it so the user should not need to toggle tracking off then on for the points to resume posting to the BE. I will also take a look at 15.4... But my understanding is the Geofencing & Significant Location Changes would affect if a location was triggered not if it would trigger the HTTP post? |
Yes. You are supposed to reproduce this on your own device. |
Can I know which beta version? I tried using 15.4 Beta 3, seems like still got same problem. |
Create for me a simple RN Hello World app which reproduces the issue and share that in a public repo for me. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You may also mark this issue as a "discussion" and I will leave this open. |
Buenas noches, Presento el mismo inconveniente. React Native versión: 0.70.8 |
Your Environment
react-native -v
): "~0.63.4"Additional:
Expected Behavior
I would expect [onHttp] to keep running and the change in location to keep getting posted to the server.
Actual Behavior
After a while, I keep seeing the
console.log("[location] ", location);
when debugging in the simulator, but theconsole.log("[onHttp] ", response);
stops, and as far as I can tell nothing is being sent to the server BE anymore.Steps to Reproduce
console.log("[onHttp] ", response);
when I turned everything on then nothing. Just the locations...Context
Trying to track a phone in the background. While drivers and other people are using it for other things.
It works great for a while, then for whatever reason, the phone seems to know the location to send, but the background task locks up and stops posting it to the server which defeats the whole point.
Toggling tracking on and off fixes this, but again the point is to track during a whole shift or run of things.
Debug logs
Logs
Overall am glad to have bought this, but really need a way to keep the phone sleep what not from ending the background reporting position until the user resets it
The text was updated successfully, but these errors were encountered: