I've reported a few bugs to support over some months -- my first involved Gaia constantly snapping back to the last search result and losing the most recent pan, another involved offline routing being broken. But I've rather lost my will to do so, and it's very laborious...well, in general...but especially for bugs that reproduce frequently, but not always.
Since then, I've noticed other weird stuff, such as route vertices being rendered as numerous waypoints in "saved," multiple cursors being rendered when clicking, occasional exceptionally long delays in being able to use the cursor to interact with the map, crashes when trying to use guidance mode (whose detail page is the only way to see how I sit on the elevation gain/decline).
All of these can be resolved by swiping out of GaiaGPS (force-close) and opening back up. I wind up doing this far, far more with GaiaGPS than any other application. It's practically obligatory knowledge to use the application. When I recommend Gaia, I always add on: "but it's very buggy, you have to force-close it whenever doing something slightly advanced after it is backgrounded."
I also had a case of incorrect track data being recorded (warping me momentarily to a previous point) when I swiped out once, to resolve some of these issues.
That said, if I continuously use GaiaGPS, that is, I am not switching apps or letting the phone sleep while recording in the field, it's fairly polished. So it seems like these bugs have a nexus that is getting very distracting, and could use some significant software engineering time to consider what is going wrong to cause so many bugs when Gaia loses focus.
Please sign in to leave a comment.