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

Started by Menion, December 05, 2025, 08:08:32

0 Members and 1 Guest are viewing this topic.

Menion

Ah, this is exactly the kind of possible errors ... thanks, will fix it asap.
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 Release download
  •  

freischneider

4.32.03
When I click on the Locus Store, the app closes.
Poco F5, Android 15 / Xiaomi Redmi Note 10 Pro, Android 13
Locus Map 4 Gold (always latest version or Beta)
LM4 User-ID: 11cec7cb5  (Devices-ID poco F5)
  •  

Erelen

#32
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

#33
Quote from: freischneider on December 20, 2025, 21:16:584.32.03 When I click on the Locus Store, the app closes.
confirmed - crash - nasty ;-(

Quote from: Erelen on December 21, 2025, 02:38:241) Crash when I open MapItems list (Map-screen content - button in right of Active items).
confirmed crash

Quote from: Erelen on December 21, 2025, 02:38:24- 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

Quote from: Erelen on December 21, 2025, 02:38:242) 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"
 
4.32.0.4 1198 GOLD user ID:c7d47597a
  •  

Erelen

#34
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

#35
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?  ::)
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 Release download

Andrew Heard

#36
Quote from: Menion on December 22, 2025, 15:28:29What to do with it here?
leave it "as is"

4.32.0.4 - all good now
 
4.32.0.4 1198 GOLD user ID:c7d47597a
  •  
    The following users thanked this post: Menion

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

#38
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:

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 👍🙂