Re: [APP] - version 4.32.+ ( 12/2025 )

[Menion]

Ah, this is exactly the kind of possible errors ... thanks, will fix it asap.

[freischneider]

4.32.03
When I click on the Locus Store, the app closes.

[Erelen]

4.32.03

1) Crash when I open MapItems list (Map-screen content - button in right of Active items).

Earlier bugs:

2) Two "Presets" screens do not take into account the height of android navigation bar:
- Presets - Edit (last item under "Pencil" button)
- Presets - Edit - Pencil (last item under navigarion bar)

3) Dashboards. Sorry.

Everithig ok in edit mode (ok == "like in 4.31 and earlier").

But in view mode:
- bottom row is under navigation bar
- top row is under notification bar (hm. top row in view mode was ok in 4.32.0.1 - https://forum.locusmap.eu/index.php?msg=80029)

[Andrew Heard]

4.32.03 When I click on the Locus Store, the app closes.

confirmed - crash - nasty ;-(

1) Crash when I open MapItems list (Map-screen content - button in right of Active items).

confirmed crash

- top row is under notification bar (hm. top row in view mode was ok

confirmed - as a quick fix I simply added a new row above each of my existing dashboard rows to compensate for "immersive mode" - figured that was simpler to fix this way

2) Two "Presets" screens do not take into account the height of android navigation bar:
- Presets - Edit (last item under "Pencil" button)

tried to reproduce, but unsure how; sounds related to "immersive mode"
 

[Erelen]

4.32.03

Crash on open "Online map downloader" (tiles downloader).

And after downgrading to 4.32.0-1198 (to use MapItems and offline LoRouter with my own profile) - it crashes in 1-2 seconds after start. So, I'm really looking forward to the next build :)

[Menion]

Thanks for the tests ... 4.32.0.4 published!

@Erelen
Presets UI > indeed there is something wrong when returning back from "Select settings" page. Hmm, can't find the real reason of this ...

Dashboard problem > in the "Dashboard over full screen" mode, this is starting to be more complicated . What to do with it here? Offset it by the status bar? But what if you want to draw dashboard panel also below the status bar? 

[Andrew Heard]

What to do with it here?

leave it "as is"

4.32.0.4 - all good now
 

[slarti76]

Merry Christmas everyone!

Sorry for bug reporting in the holidays, but this one's severe:
I edited a track, did the following:

• Insert/edit trackpoint
• Remove section
• Insert/edit trackpoint

The last operation instead deleted like half of the track, I'm not 100%, but it was probably same as "Remove all after".

Track and screen recording of what I did can be found here: https://web.tresorit.com/l/UwA4T#NoxPRGDwfym3Key277zm1A (that video contains a "Remove all before" as first operation, but I tried it without again and could reproduce - the first "Insert/edit" however is necessary to reproduce)

I used latest beta, so not urgent, but definitely disconcerting...

[Ulrich Kiermayr]

Merry Christmas from me as well:

I hit a serious bug in 4.32.0.4

1. app crash in navigation
When in navigation or guidance when the screen goes off, the app crashes/closes/disappears.
This is regardless of the settings of screen control or run as a service. (Problem is: this makes this version quite unusable).

I checked the log and it seems, the app dies, when the screen goes back on. This is the error message:

Code Select Expand

16:57:03.820 E a uncaughtException(Thread[main,5,main])
java.lang.RuntimeException: Unable to resume activity {menion.android.locus/com.asamm.locus.basic.features.mainActivity.MainActivityMap}: java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:6269)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:6342)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:73)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:63)
at android.app.servertransaction.TransactionExecutor.executeLifecycleItem(TransactionExecutor.java:169)
at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:101)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:3150)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loopOnce(Looper.java:273)
at android.os.Looper.loop(Looper.java:363)
at android.app.ActivityThread.main(ActivityThread.java:10060)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
Caused by: java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet
at d5.n.e(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:45)
at bx.c.invoke(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:354)
at com.asamm.locus.basic.settings.dialogs.PrefDashboardSelection.q(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:108)
at mt.c.onResume(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:110)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1720)
at android.app.Activity.performResume(Activity.java:9691)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:6239)
... 14 more


2. Nav Bar draw over (inconvenient):
The nav Bar draws over the sensors manager, which makes the connect button of the last sensor (almost) unreachable.
(Fun fact: also the screenshot ends above the nav Bar, therefore i had to take a photo 😉)

You cannot view this attachment.

Greetings Ulrich
And as always, if I can help debugging, just tell me, what I should do 👍🙂

[Tapio]

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

[Ulrich Kiermayr]

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

I did a quick check and the issue seems to be related to my dashboard. Have to do some more checking

LG uk

[T-mo]

LM 4.32.0.4
the bug once mentioned in the german post you answered shortly is still existent.
With GPS location on but crossed moved out of current position and center the icon still keeps its white center and does not switch to empty/non-white. This is only with lock on, with lock off the center of the icon immediately switches.
See pic, center not on current position (far away) but icon filled white, obviously wrong and easy to doublecheck.

btw i use the dual centering button (expert setting > maps).
There's also sth. wrong with north direction and center on current location and map-rotation, you definitely have to move center-cross out of location to enable northing, otherwise it switches always back to map-rotation when centered. I know this move but might be irritating to others.

Guess all that is supersimple to solve.

[Ulrich Kiermayr]

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

So I did some testing: crash only happens when a dashboard is Active. It does not matter what is in the dashboard - even a completely empty one triggers the crash. If I disable the dashboard, crash is gone.

Can someone confirm this?

Greetings, Ulrich

[Ulrich Kiermayr]

Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.

So I did some testing: crash only happens when a dashboard is Active. It does not matter what is in the dashboard - even a completely empty one triggers the crash. If I disable the dashboard, crash is gone.

Can someone confirm this?

Greetings, Ulrich

This workaround is only valid for guidance mode. Navigation always crashes, regardless of the dashboard (or anything else navigation draws on the screen).

Maybe also related to the Android version (S23, Android 16).

Greetings, Ulrich

[Tapio]

Not crashing even with Dashboard on. Android 10