Visits don't get created if a track ends and starts at the same location anymore
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 10.4k
- Forks
- 376
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 151
Description
BEFORE OPENING AN ISSUE, MAKE SURE YOU READ THIS: https://github.com/Freika/dawarich/issues/1382
OS & Hardware
debian 13
Version
1.10.1
Describe the bug
I noticed that after updating to I think 1.10.x, visits don't get created anymore if the track ends and then starts a few hours / minutes later at the same location
I have set up a automation (in iOS shortcuts app) for my gym for example. When I arrive at my gym, my phone detects it and stops tracking automatically. When I leave the gym later again, the automation starts tracking. The automation just executes the build in "start tracking" shortcut from dawarich ios app.
In earlier versions dawarich always created visits for exactly this. I didn't track the entire time but visits still appeared. Now I only get visits if tracking in dawarich is always enabled. It doesn't create visits for the described situations where tracking stops and then starts at the same location later again
To Reproduce
Steps to reproduce the behavior:
- Drive to a location & stop tracking
- Leave the location later again and start tracking
- Upload the track
- Check in dawarich -> no visit is created
Expected behavior
Just like in the versions before, I get a visit even if I don't have tracking enabled the entire time
Screenshots
How it worked in older dawarich versions:
How it is in dawarich 1.10.1:
Additional context
As you can see in the screenshots above I did everything like I always do. Visits just stopped appearing for some reason. Points are exactly the same. It's not just for this day or this location. Last time it was working correctly was 10.07.2026. After that I left for vacation and since then it's not working like it did before so I think this began with version 1.10.0
If you need more examples or something lmk
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the upload flow with a track that ends and later resumes at the same location, then trace how visits are created from uploaded tracks and compare behavior with the reported 1.10.0 change. Done means a visit is created for the stopped-and-restarted tracking scenario without breaking continuous tracking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100