Update 4.33.0 BUG: Edit tracks

Hi Ralf,

could you please describe the problem in more detail, or add screenshots or a video? We can't simulate the problem, see: https://drive.google.com/file/d/10bu-slXpSzBb25B0ttXUPSYcPPFtV9iY/view?usp=sharing.

Hi Michal!

No, I can't add a screenshot anymore - I just installed the last working version - and lost all my settings, maps, and icons! :-(

Now I have to set everything up from scratch... Thanks a lot... Aren't the settings backed up during synchronization? If not, why not? Why isn't there a way to cancel an update and revert to the previous version?

Who does the bug checking for a new version? Hopefully not the programmers - they're "blind to their own mistakes" and can't find them! This isn't meant to be offensive, it's just how it is.

To reproduce the bug, take any old track consisting of DOZENS or HUNDREDS of waypoints and try to edit it.

Try changing a section from "walking" to "cycling," try to see the waypoint list... none of it works anymore...

It simply doesn't work the way it's shown in your example video. Do you have access to my tracks in the cloud?

regards,

Ralf Sundell

------ Originalnachricht ------

Von "Locus Map" <locus.map@asamm.com>

An "Ralf Sundell" <ralf.sundell@web.de>

Datum 02.04.2026 14:50:16

Betreff New Comment in "Update 4.33.0 BUG: Edit tracks"

Hi Ralf,

settings are not backed up during synchronization. Only tracks, routes and points. The settings are dedicated to the particular Locus Map installation on your device. The settings are saved in a backup - do you have automatic backup set up? If yes, nothing is lost. (more info: https://docs.locusmap.app/doku.php/manual:user_guide:settings:backup_fsys#backup_manager).

"Why isn't there a way to cancel an update and revert to the previous version?"

- you can cancel automatic updates in your Google Play app:

- you can uninstall the app and install an older version from our public repo at https://bit.ly/lmVersions. BUT we strongly recommend creating a complete (migration) backup before that (more info: https://docs.locusmap.app/doku.php/manual:user_guide:settings:backup_fsys#app_migration_backup)

"Who does the bug checking for a new version?"

- the developers, our team, and a community of power users and beta testers around forum.locusmap.eu

"To reproduce the bug, take any old track consisting of DOZENS or HUNDREDS of waypoints and try to edit it..."

- as you can see on the video, I can't reproduce the issue. Could you please send a GPX of any routes of yours that can't be edited? Thanks

"Do you have access to my tracks in the cloud?"

- no, your data is kept private

This problem is also discussed in the forum. The issue is with all routes made after January 2026. New routes and older routes work as expected.

A workaround is to open the route in the web planner, open for editing and then save a copy. The copy can then be edited in the app again.

Video of the problem here: https://drive.google.com/file/d/1hBbUPK2HMt9LgnBQUrV8TfbWYN_fRXpB/view?usp=drivesdk

The track in the video https://link.locusmap.app/t/1s9v2t

A more elaborate video, including the workaround can be found here: https://drive.google.com/file/d/17XafHQZFnU3mL64cuPHXXNRYn8g-mSqK/view?usp=drivesdk

Hi Michal!

The current version was reinstalled overnight after all – I thought I had prevented that…

Now the problem is back.

I even installed a screen recorder and enabled the touchpoint in the Android developer options so you could see what I was doing.

The recording is attached to this email, as is the corresponding GPX track.

You have my permission to log in to Locus Map under my name to search for the error. I am logged in with the email account I am writing from; the password is "Pavel2022#".

The test example you cited as a video is a typical example from a software developer. Real-world testing looks different and is NOT performed by the developers themselves – as I said, you get tunnel vision, it's only human. I know what I'm talking about.

I once discovered a serious bug in a CAD/CAM program written in C++ that caused a system crash. It involved drawing a polygon that closed automatically. The developers had only ever tested the function with a polygon of just a few points, always drawing just clockwise. For testing purposes, I also drew counterclockwise. The result: an immediate crash due to a simple error with the plus and minus signs while closing the polygon. All the developers involved in this function had overlooked this tiny but fatal bug.

Even when using the same beta testers repeatedly, this kind of tunnel vision can develop.

Furthermore, testing requires a certain mindset: you have to aim to crash the software. Only when all attempts to break it fail the version can be considered as stable. A benevolent attitude is just as unhelpful as the routine procedure of a few repetitive processing steps – beta testers tend to do exactly that...

Kind regards

Ralf Sundell

------ Originalnachricht ------

Von "Locus Map" <locus.map@asamm.com>

An "Ralf Sundell" <ralf.sundell@web.de>

Datum 02.04.2026 16:00:05

Betreff New Comment in "Update 4.33.0 BUG: Edit tracks"

Hi Ralf, please test it with the latest Beta version: https://drive.google.com/file/d/1jSBflgMt30BsHdIiQZ80n2_TrytrT91p/view?usp=sharing. The issue has been fixed.

Hi Michal!

I installed the Beta version and tested all tracks that made problems before: Everything works fine!

I also imported some GPX files, no problems editing those.

Thanks for helping and for fixing the bug.

Kind regards,

Ralf Sundell

------ Originalnachricht ------

Von "Locus Map" <locus.map@asamm.com>

An "Ralf Sundell" <ralf.sundell@web.de>

Datum 07.04.2026 15:20:05

Betreff New Comment in "Update 4.33.0 BUG: Edit tracks"