Messages

Another bug that appears to be back is that, when editing a route, the time is not updated correctly. If you want a new estimate of the time, you have to recalculate the entire route.

Have you tried the latest version I've just published?

I checked with version 4.33.0.8 build 1211. The problem appears to be fixed, i.e. I can edit the route I linked earlier again.

Have you tried the latest version I've just published?

Given the number of problems reported here with the latest beta, I'll hold off for now.

However, there are now multiple reports in the helpdesk about the inability to edit routes. I answer them with a video of the workaround via the web planner.

I made a s reen capture of the problem with certain routes: https://drive.google.com/file/d/1hBbUPK2HMt9LgnBQUrV8TfbWYN_fRXpB/view?usp=drivesdk

I also noted the problem is reported as a bug in the helpdesk twice (not by me)

[@Blihi]

@Blihi
share a problematic route with me over "Share by link". Thank you.

Sure. Here's one that cannot be opened in the app: https://link.locusmap.app/t/1s9v2t

This one does not open in the online planner either.

This link is working for me, both in app (latest beta) and in Web planner.

Interesting. I can open it now in the Web planner on my Windows computer. It did not want to open in the Android version of Firefox on my tablet yesterday.

In the app (latest release 4.33) it does not open, but when I choose "edit route" the app opens the empty planner.

The latest beta is 1207, while the release is 1210. I cannot downgrade to 1207 to test, unfortunately. But it seems to be related to this, i.e. any route made after January 2026 has this problem for me.

[@Blihi]

@Blihi
share a problematic route with me over "Share by link". Thank you.

Sure. Here's one that cannot be opened in the app: https://link.locusmap.app/t/1s9v2t

This one does not open in the online planner either.

Routes can be restored in the following way: open them in the web planner, recalculate with the correct profile, store as new. Then you can edit them in the app again.

Or, sometimes on a tablet: open the route in the webplanner, select edit, open in planner. Then refresh the page, now the Locusmap app will open with the route in the routeplanner. Here you can save it directly to the app.

For me it's the entire holiday planning for this year, unfortunately 

Well, I'll just hope it will be fixed soon.

After reading the entire thread, it seems the problem is the same as mentioned here:

I think there ist a nasty bug in Beta 4.33.0.1

Routes created using the route planner cannot be edited. Selecting 'Reroute' displays a brief 'Initialising' message, hides the route to be modified, and brings up the screen where I can create a completely new route. It's as if I were starting the route planner from scratch.

Routes created using the web planner can still be edited (once).

See screenshots.

Though, it does not seem to be limited to routes made in a specific small time window. Older routes, i.e. more than a year old, open well, but routes that are from 2026 do not seem to open.

I can confirm that this is the exact error message that shows up in the log every time I try to open one of the routes that won't open.

The logs are showing a message suggesting that there is a cancellation:


20:40:30.910   E   a   setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@2dc2482

20:40:36.898   E   a   setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@4e95969

20:40:44.398   E   a   setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@5b4f7ab

20:40:49.673   E   a   setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@cccd273


In this example, I tried to open four existing routes in the planner. None of them opened.

You respond to me, but I'm not talking about downloaded tracks. I'm talking about routes made in the locus planner, which suddenly cannot be opened anymore in the planner in the app.

I do not see any error messages, the planner just shows an empty screen as if you open it the regular way, while it no longer shows the route on the map.

Restarting the app makes no difference and the problem exists on multiple devices and I checked the logs, no exceptions are logged.

In the latest version, 1210, most of my routes cannot be opened in the planner anymore. When I open them in the planner, the planner just shows an empty planner. No waypoints whatsoever.

In the online planner, I can see that the waypoints are still there, so the problem is really in the app, allthough I also have routes that show waypoints in the app, but not in the planner.

Routes are all made on offline lomaps with offline locus planner.

[@Blihi]

@Blihi
Thanks for the "ID". Unfortunately, I do not see any automatically reported issues. The current version seems to be more stable than I expected. So there are no unusual memory problems reported. This happens to you even when you start with an empty route planner and just add a few points? Does it make a difference what map you use? (online require a lot less memory, so give it a try).

The problem occurs randomly in the routeplanner. It does not really matter if I start from an empty route or open an existing route for editing. I'm typically using offline LoMaps, not the online maps. It's unclear when the crashes exactly happen, but the way they appear is always the same: the screen freezes and the app reboots.

I'll try to debug a bit, but it's a hard problem to reproduce. I'll try to see if it also happens when I'm offline. Maybe the cloud synchronization in the background is interfering with the planner in some way.

I include a log file of today. Crashes happened a few times, no clear indication why, but there are a lot of exceptions in the log.

[@Blihi]

@Blihi
may you please write to me your "User ID"? Thanks (in the about app screen > 9 characters)

Sure, it's a3cb44c74

It appears to be a memory issue. The app works for a while, then slows, typically when showing the magnifier glass. At that point it becomes unresponsive and reboots. Android by now also suggests to put the app in deep sleep because of frequent crashes.

The issue appears both on the phone (Samsung S22) and the tablet (Samsung Tab9FE). I turned logging off, but that did not make a difference.