[Bug] GPSLogger points ingested via API (v1 and v2) are not rendered on the map in v5.3.0

[Arcane64]

Describe the bug
After upgrading from Reitti 5.1.0 to 5.3.0, location data ingested from GPSLogger is no longer rendered on the timeline or map view.

• Using the new GPSLogger v2 file upload flow (configured via auto-configure), data is received without errors, but no location points or trips appear on the map.

• Ingesting points via the v1 API (/api/v1/ingest/gpslogger) that I reconfigured manually in GPSLogger accepts the data as well, yet no points are shown on the map either.

• Manually uploading the .gpx file through the web interface still works as expected and is currently my only way of importing data.

To Reproduce
Steps to reproduce the behavior:

1. Configure GPSLogger to send data via either of the two APIs (/api/v2/gpslogger/file or /api/v1/ingest/gpslogger).
2. Send tracking points from the device.
3. Navigate to the Reitti web UI timeline/map for the current date.
4. No new points are displayed and no background tasks are running/processing them.

Expected behavior
GPS points ingested via /api/v1/ingest/gpslogger or /api/v2/gpslogger/file should be processed by the background worker and displayed on the timeline/map, as was the case in version 5.1.0.

Additional context
Reitti version: 5.3.0 (upgraded from 5.1.0)
Deployment: Docker
Client App: GPSLogger for Android

Personal Note
First of all, my apologies if I missed anything obvious or if my technical explanation isn't fully accurate; I am still relatively new to Reitti's inner workings and writing GitHub issue reports.

A small piece of feedback regarding the new setup: it feels a bit limiting that we can no longer easily choose or configure our preferred ingestion method with GPSLogger. I'm not sure if the new v2 file API is intended to handle continuous real-time live tracking, as data seems to be batched at a 1-hour interval by default.

Additionally, I noticed on the GPSLogger integration setup page in the UI that the documentation mentions configuring Custom URL, but the auto-configurator only touches the HTTP File Upload settings in GPSLogger. and the HTTP body field completely empty. I'm not sure if it is intended behavior or if a default payload template was supposed to be provided there.

[dgraf-gh]

Hi @Arcane64,

maybe you are running in the same issue like #1212. I hope to find some time tomorrow to work on that. If you fo to 'Settings > Logging' are there any errors?

Sorry, I forgot to update the documentation to provide the old way. I will add this tomorrow.

The auto configure sets only the HTTP File Upload part of gpslogger. The rest is empty or uses the defaults. But you made me realise that we also could set the custom url upload but keep it deactivated. Then the user can switch between the two.

You are free to set the interval back to your preferred timing. The problem with the old way in GPSLogger is that it always sends all points created at this day. So if it is 02:00 and 50 points are tracked, it sends them one by one to reitti. Later at 03:00 and 75 points are tracked, it sends the first 50 + 25 points. Every one with its own request. The new way does the same, but sends only one file which contains these points. So basicly they do the same. Only that the new way, works much faster and saves energy by not opening hundreds or thousand connections.

[Arcane64]

Hi @dgraf-gh,

Thanks for getting in touch, i did read issue #1212 while looking for existing reports before opening this, but initially discarded it because my instance processes no GPS points besides the .gpx files I upload occasionally. Looking at it again, I can definitely see the similarity since my data appears to be ingested but simply not processed.

When tweaking the GPSLogger settings while trying to solve the issue, I did see errors in the Logging UI, but none anymore since getting the HTTP settings right.

Thank you for the upcoming documentation updates. I understand the need for the new api better now and it will hopefully be useful for saving some of our phone battery.

Having both HTTP File Upload and Custom URL could definitely be useful for switching between continuous live tracking for location sharing and periodic file uploads for gps backup.

Please let me know if i can help you investigate further by sharing any additional logs or configuration details from my instance.

[Arcane64]

Hi again,

While modifying some points imported from my .gpx in the Workbench, i ran into this error :
Cannot invoke "java.lang.Long.longValue()" because the return value of "com.dedicatedcode.reitti.service.SpatialCoverageService.getLevelCellForPoint(double, double, int)" is null
and the manual data modification is stuck in "awaiting" state in the task list.

Hope it can help you with the issue.

[dgraf-gh]

Hi @Arcane64,

at least the docs are now updated https://www.dedicatedcode.com/projects/reitti/latest/integrations/mobile-apps/#manual-setup-via-log-to-custom-url

I am still investigating the rest. 🤞

[dgraf-gh]

HI @Arcane64,

please test the v5.3.1 release. This should resolve your issue.

Thank you for the report

[Arcane64]

Hi @dgraf-gh,

I had some time to test 5.3.1 and it is working as expected ! the gpx imported from the gpslogger http file upload are getting sent at my desired rate and processed by reitti !

The workbench issue is solved as well, i think it happened because i enabled spatial coverage to test it out but disabled it when i saw that my points weren't ingested thinking it was somewhat the issue, so happy to test the edge case ahah.

Thank you as well for updating the integration UI for gpslogger. I'm excited for the future of Reitti, keep up the good work !

[dgraf-gh]

Thank you for coming back and updating me. That helps tremendously.

think it happened because i enabled spatial coverage to test it out but disabled it

Judging by the code, this would have been broken without the feature enabled in the beginning. I tested the Workbench for 5.3 but never without the spatial coverage being off.