It´s not possible to set user defined track colors (android release AND nightlies), followed by a crash

[Rowin63]

Description

I have a set of imported tracks. I want to change their color. Two different devices, two dofferent Osmand releases.

This is what happens in the ~4.9.0#3200m (but also before):

Though set to "red":

They look like this (blue, red, green):

Back in the editing mode I see this color selected at all tracks:

I change the color to green and apply:

After closing the app and starting Osmand again, I´m back to the beginning:

And this is what happens in the Android Playstore release +4.9.0:

The same set of tracks, all set to "red":

I change one of them to "green":

Close Osmand and start it again, I´m back where I started:

And going back to the editing mode, again I see this color selected (what I never did):

While writing this text here, the +4.9.0 crashed: exception.log

[edit] the yellow color-picker perhaps is caused because of selecting tracks with different colors?

Steps to reproduce

see above.

Actual result

see above.

Expected result

see above.

Your Environment (required)

2x Galaxy S20+ Android 13 Osmand +4.9.0 Osmand ~4.9.0#3200m

[Rowin63]

All this, both described issues, don´t happen in the +4.8.6 There changes remain as done!

[yuriiurshuliak]

The bug has been reproduced. To reproduce it, add three tracks to a folder and changing their appearance, specifically their color. After changing the color and confirming that the tracks reflect the changes, close the app entirely. Upon reopening the app, you will notice that the previously set colors are lost, and the tracks revert to the default red color.

OsmAnd~ 4.9.0#3203m, released: 2024-09-17

https://github.com/user-attachments/assets/234ac517-da03-4127-8574-b86e68540dc8

[arncor]

Same problem here on 4.9.0 (android9). Osmand also doesn't remember track width and direction arrows, or even the list of tracks that are shown on the map.