Missing Geo Points At Random Times #2141
Comments
|
PolygonGeofencingService has absolutely nothing to do with your problem. I will remove that log message so you don’t see it. |
|
Show me a screenshot of your problem with locations displayed on a map, |
|
If you’re not monitoring polygon geofences, the PokygonGeofencingService, which receives every recorded location, does nothing. Red herring |
|
this is a map of the route with all the geo points we received for that trip |
|
You're saying you experienced a loss of location-data at ~ I don't see that at all. I see a continuous stream of reported locations. I see you're not using the plugin's built-in, pure native HTTP service and you've disabled the plugin from inserting recorded locations into its SQLite database. I don't trust HTTP requests through the react-native layer. When you see this in the logs, the |
|
Btw, here's me driving all over France for 2.5 weeks this summer using the demo app (iPhone 15 Pro, Google Pixel 6.) |
|
Correct, looking closely at the logs in particular I don't see a similar log to the one that indicates the 
|
|
If the data exists in the logs, but not on your map, then you have a problem in your JavaScript / http / socket. |
|
I understand that part, but the issue is that I see no coordinates recorded in the logs for the time between from the logs I see the following Point 1 and the very next one is 
|
|
The native location api had no locations to provide during that period. This can happen in a dense downtown of a large city, where tall buildings and other large physical obstacles block GPS radio signals. |
The logs you uploaded do not have these locations that you quote. If I search the logs for Please check the logs you sent me and search for those timestamps. |
|
|
I can understand that. But the strange behaviour we are seeing on v 4.17.1 (the above logs) was not there on 4.14.4 Please try again, re-uploaded the logs (the wrong trip logs were uploaded earlier) |
You’re consistently reproducing this yourself? I’m field testing daily with my iPhone 15 Pro @ 17.5.1 — I’m not experiencing unusual behaviour on my daily walks / bike rides. |
I suggest you test with that set to |
|
My last 7 days of tracking: 
|
|
Unfortunately, we are consistently seeing the same jump in geo points every trip we've tested. Here is a another set of logs for reference Same Plugin config as mentioned above seeing the jump between and |
We can test that, will share logs once we have them |
|
There is no explanation for the delay between these two locations. The native location API is like a tap of water that drips locations according to your configured One thing to note is that the accuracy of locations that finally started coming in after the delay were relatively poor: Typical GPS accuracy is 5-10 meters. This sort of thing is indicative of the device losing access to GPS.
|
|
Yes, the logs seemingly going blank at times and picking right back up is a very strange behaviour especially that we don't see any action that suggests that a stop was detected or that the device was in a stationary state or anything that would explain why geo points weren't collected. Interesting to see the accuracy piece, I overlooked that part earlier. Again, the fact that we only see this behaviour of missing geo points at times on 4.17.1 but not 4.14.4 is why we are trying to understand what changed More trips for reference: Plugin config
BackgroundGeolocation.ready({
desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
stopOnTerminate: false,
enableHeadless: true,
logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
stationaryRadius: 1,
stopDetectionDelay: 10,
stopTimeout: 15,
preventSuspend: true,
disableElasticity: true,
desiredOdometerAccuracy: 1,
distanceFilter: 0,
heartbeatInterval: 60,
showsBackgroundLocationIndicator: true,
startOnBoot: true,
maxRecordsToPersist: 0,
backgroundPermissionRationale: {
title: "Allow Solo to access to this device's location in the background?",
message: t(TRACKING_MESSAGE),
positiveAction: 'Change to {backgroundPermissionOptionLabel}',
negativeAction: 'Cancel',
},
})
gap in geo points 
|
|
I’m out walking, as I often do, right now.
|
|
We are experiencing the same behavior in our production app with v4.16.3 on iOS. E.g.
We use Is there a test app on iOS to compare against our production app? |
No, it would make it worse. Imagine you're stopped at a red light with
Yes. It's linked in the README here |
I have read through these so many times ... I get what the library is trying to do. Noticed this user had that value set in their config and no mention of whether adjusting it would be prudent to assist with the issue they are reporting so thought I would highlight it.
Right, have to build it, was interested in if you released it to App Store. Our production users can't be expected to build it and install on a real iOS device |
Apple doesn't allow "demo apps" released publicly. You would have to release it yourself for testing and add up to 100 beta users. |
|
This issue is stale because it has been open for 30 days with no activity. |
Your Environment
Expected Behavior
an uninterrupted stream of geo points that maps the entire route step by step
Actual Behavior
After upgrading from 4.14.4 to 4.17.1, we see some gaps in geo points at random times in every trip we've tested
Steps to Reproduce
Taking any trip that includes regular traffic delays, traffic light stops, parking lot exits/parking
Context
We are trying to understand what is causing the gap in geo points at times
Debug logs
background-geolocation (3).log
Logs
The text was updated successfully, but these errors were encountered: