How to get point+track visibility state from before migration to new My Library?

I don't think that will work anymore. You could use a second phone and install the old version. And then load an old backup. The rest is just manual work.

I doubt (pure hope?😉) that's the way to go 🙂 The v4.28 announcement tells Before this process, the application will automatically perform a backup to eliminate the risk of data loss which would be mostly useless if no restore was possible on that device. Moreover, knowingly deleting hundreds of data points and requiring to manually re-create them using a 2nd phone (where to get it from?) is so much user un-friendly, I doubt Locus team would do so without asking for consent before.

Hi Georg,

sorry for the inconvenience and thank you for reporting it. We somehow ignored the data visibility status during the data migration. The bug has been fixed and will come into effect in the next app version so other users will be able to maintain their data visibility status also after the migration.

Hi Michal,
thank you for quick anaysis, fix of migration and reply 🙂

That's good news for all users doing migration in the future!

How can I trigger that Locus does again migrate based on the back up? Simply call restore from backup in settings? BTW, I am aware that this will lose all stuff that I changed since the backup, so to keep that, some steps are required, see https://help.locusmap.eu/topic/36964-new-library-quick-new-point-created-in-wrong-folder#comment-148451

I did this step on my 2nd phone. Made a backup to be on the safe side. Uninstalled Locus. Installed old Locus version 4.27. Backup installed before the backup. And then installed the new one. Then backup and restore the backup on the 1st phone. Since I export all recorded tracks. I added them again.

@freischneider: Thank you for sharing your experience & way.

@Michal: Is there also a way on one phone? Hopefully without uninstallation & reinstallation? 🙂

FYI, as reported in this topic, another migration resulted in a My Library where some points were visible – some but not all of the points where I expected it, and some points I definitely had hidden in v3. Maybe you want to check your fix is also handling this variation.

Hi Michael,

I re-tested MyLibrary migration from v4.23.1 (top and by intention massively reduced data set so it becomes overseeable) to v4.30.1.7beta (bottom): Visibility of tracks is preserved, visibility of some point folders is preserved while lost for others, and sorting order is lost (assuming lexical order is default), I did not have filters active:

=> The existing fix helped but is not complete. In order to allow you to reproduce, here's the backup of v4.23.1

Hello Georg,

thanks for detailed description, screenshots etc.

Before I dig deeper into this, I have to ask > does it worth fixing it? You are still using older version and waits for the fix to start using the new version?

I believe, most of users are already on the new migrated version. So fix will have benefit for minority of users.

Hi Menion,

• Worth fixing? Hard to tell for me because I cannot estimate what other users experience and do, and I do not know your priorities.
• IMHO it's not worth if pareto principle (AKA 80:20 proportion) is your decision base.
• I agree, a fix 5 months ago – so soon after I reported the current fix is not fixing the issue – would have beneficial for much more users than a fix now. Now, light users will already have manually corrected the visibility state and won't use the fix. Different for the veteran heavy users: Mainly those have big amounts of POIs+tracks, hence, manually re-creating visibility status is quite an effort, so it's not unlikely they postponed it and are happy to export all library content newer than migration, restore old backup with correct visibility state, then re-import the newer data. They are certainly a minority, but I've no idea how important they are to Locus team (subscribers? providing ideas & feedback in forum & helpdesk? etc.).
• Yes, I use old version because of several issues – if all other except for this issue would be solved, I'd not be happy about the manual work but I'd update to current version.

Last point more detailed for those who are interested: Since I discovered 4-5 months that v4.23.1 works reliably, I'm mainly using that version and sometimes v3. Why? Because of several open issues in v4.24+ that are important for me:

• Stability issues. Locus v4.24.3 and newer crashes in average maybe every 4th use. During few days of v4.30 test, crashes did also happen, and additionally, Locus did several times not start (Android's "repeatedly crashing app" dialog popped up) and it did several times not get sat fix – I did not create tickets because I don't yet see a pattern/cause. None of these issues happen in v4.23
• Loss of visibility information during v4.28+ My Library migration
• New MyLibrary is currently still less useful for me than old one, due to a combination of many smaller issues like e.g. only 50% of information visible is a considerable usability decrease for me, or that last scroll position is only partly remembered now.

Fixing only this issue (My Library migration data loss) won't make me use up-to-date versions because of other issues. The named ones, but also further bugs + limitations newly introduced in last 14 months. For several of these, Locus team tells only few users report them as issues – and I just have the bad luck to run into multiple of them, making newer v4 releases less useful for me than older v4 releases. If in fact few users experience them, it's reasonable that you don't fix them and that I will stick with old version which ages more and more (e.g. sat maps don't work any more), so for the long run, I must look for another app except issues are solved co-incientally (e.g. when I replace my mobile). I'm hoping for the latter, because I like Locus and it was a partner for so many activities during over a decade.

Hello Georg,

thanks for detailed feedback!

1. restoring of item visibility > I've just restored your backup in the Locus Classic and Locus Map apps and in both, I've got identical result. 3 points visible in the "_FR Umland" directory and per one track visible in every track directory. So I do not see any problem here.

2. crashes > I have to note somewhere "user ID" values for you and other users. Sorry to ask (probably again), may you write to me your "user ID" value visible in the "About app" screen? Thanks

3. My library > size in the UI + scroll positions - I'll answer in appropriate topics.

Hi Menion,

for such tests it would be great to have a possibility to select main dir without moving all my stuff (mapitems, router data, geoNames,...) but instead or copy data to new dir and/or just select/set an already existing dir (similar to "without move" button for custom Vector Maps dir): In all the back and forth between v3, v4.23 and v4.30 including installing/uninstalling v4.23 and v4.30 several times, at one point I overlooked that data was moved from shared folder to v4 private (to avoid shared folder mutually influencing v3 + v4) and I did not copy it back to the shared folder, so I lost the main data (mapitems, router data, raster offline maps,...) during v4 uninstall – I will need to look for the data in my backups.

When finally, after all the crashes, restore of the small export attached to my comment of 2025-08-02 and opening MyLibrary worked in v4.30, it had same state as you described and counting was correct (topic), visibility also correct after restore in v3 and v4.23 – but that state differs from the screenshot (further points were visible)...it's not impossible but unlikely that I did the v4.23 screenshot, then did hide some points before doing the backup + migration, because exactly the missing visibility of points was the core of my comment. Anyway, at the moment, also I myself cannot reproduce the issue with that backup 🤷‍♂

Moreover, I restored all my points from v3 into v4.30 and at first short glance everything looks OK, visibility, computations, no dupes, etc 😍🤷‍♂ I will go with it for some days and observe.

I am really puzzled why now MyLibrary looks fine while it did not in all the tries during last 5 months. Only difference that comes to my mind is that today, I lost my main directory, so it might be a caching issue or interaction/side-effect with some other data/setting. BTW, the crashes are not gone.

@2. 5a6872e3a6