Hi,
Since updating to Locus Map Classic v3.70.20 automatic backups always fail and I'm left with a number of .temp files.
I can manually backup without a problem.
I checked my usual backup folder (Set custom sub-directories) on my SD card and LM wasn't complaining about it.
However I did to reselect the same backup folder location and it popped up something about not allowing a nested folder.
It would only allow me to select a custom backup location as the root of my SD card and in no subdirectory.
In the end I set the backup folder the default LM location (/storage/xxxx-xxxx/Android/data/menion.android.locus.pro/files/locus/backup) on my SD card to stop the nested folder error.
The automatic backup still fails leaving .temp files in the default LM backup directory.
It was working fine until I updated which makes me thing it's a bug in the latest release.
All the best...
The same problem
Hi,
how do you trigger the manual backup of "LoMaps and other vector maps"? Where do you store the backup? What storage do you select?
Hi,
how do you trigger the manual backup of "LoMaps and other vector maps"? Where do you store the backup? What storage do you select?
I've tried saving locally and to dropbox.
I've tried saving locally and to dropbox.
Hi,
could you please create a bug report after the app crash and send the report file? Thanks. More info: https://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
Hi,
could you please create a bug report after the app crash and send the report file? Thanks. More info: https://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
Error Details (from logcat)
On Honor 20:
E/q (26484): backupDataSync(2026-08-12_08-07-32, [...], false)
E/q (26484): java.util.zip.ZipException: duplicate entry: mapsVector/_themes/AdventureV4.zip
On Samsung A40:
E/q (14962): backupDataSync(2026-08-12_08-09-00, [...], false)
E/q (14962): java.util.zip.ZipException: duplicate entry: mapsVector/_themes/Tiramisu.zip
Suggested Cause
The backup routine appears to scan the mapsVector/_themes/ directory and add files to the ZIP archive, but the same file (or entry) is being added twice. This could be due to:
Duplicate entries in the file list (e.g., symbolic links, or the same file referenced via different paths).
A logic error in the directory traversal that processes the same file more than once.
An issue with how the backup manager handles theme files that may be stored in multiple locations.
Error Details (from logcat)
On Honor 20:
E/q (26484): backupDataSync(2026-08-12_08-07-32, [...], false)
E/q (26484): java.util.zip.ZipException: duplicate entry: mapsVector/_themes/AdventureV4.zip
On Samsung A40:
E/q (14962): backupDataSync(2026-08-12_08-09-00, [...], false)
E/q (14962): java.util.zip.ZipException: duplicate entry: mapsVector/_themes/Tiramisu.zip
Suggested Cause
The backup routine appears to scan the mapsVector/_themes/ directory and add files to the ZIP archive, but the same file (or entry) is being added twice. This could be due to:
Duplicate entries in the file list (e.g., symbolic links, or the same file referenced via different paths).
A logic error in the directory traversal that processes the same file more than once.
An issue with how the backup manager handles theme files that may be stored in multiple locations.
Thanks, we managed to identify and fix the bug. Please wait for the next app version.
Thanks, we managed to identify and fix the bug. Please wait for the next app version.
I have the same issue with Android 13 after updating to 3.70.20 to use the Wear OS remote control app (previously I was using 3.70.17 from the Play Store). Please post here when you'll release the fix.
I have the same issue with Android 13 after updating to 3.70.20 to use the Wear OS remote control app (previously I was using 3.70.17 from the Play Store). Please post here when you'll release the fix.
Hi guys, are there any news about the fix for v3.70.20?
I'm experiencing the same with both manual backup and automatic backup (the latter leaves a notification about the failure).
Logcat extract:
Hi guys, are there any news about the fix for v3.70.20?
I'm experiencing the same with both manual backup and automatic backup (the latter leaves a notification about the failure).
Logcat extract:
Right... so after just posting a new topic regarding backup issues, there is a known backup bug in LM v3.70.20?
Right... so after just posting a new topic regarding backup issues, there is a known backup bug in LM v3.70.20?
Okay, my post about the issue has been merged with this one so I'm guessing it's the same known bug.
I use LMC a lot, so knowing my tracks & points etc are not being backed up automatically is a bit worrying.
I see it's been over a month since this bug was identified... any time-scale when a fixed version of LMC be released?
Thanks :)
Okay, my post about the issue has been merged with this one so I'm guessing it's the same known bug.
I use LMC a lot, so knowing my tracks & points etc are not being backed up automatically is a bit worrying.
I see it's been over a month since this bug was identified... any time-scale when a fixed version of LMC be released?
Thanks :)
Hi all,
Locus Classic 3.70.21 has just been added to https://bit.ly/lmVersions.
Hi all,
Locus Classic 3.70.21 has just been added to https://bit.ly/lmVersions.
Just updated and so far so good...
Locus happily accepted my custom backup folder location and moved my backups back to where I originally stored them.
Fingers crossed by tomorrow morning I should have a gleaming new automatic backup waiting for me. :)
Many thanks!
Just updated and so far so good...
Locus happily accepted my custom backup folder location and moved my backups back to where I originally stored them.
Fingers crossed by tomorrow morning I should have a gleaming new automatic backup waiting for me. :)
Many thanks!
Yep, 3.70.21 works for me, too.
Thank you very much!
Yep, 3.70.21 works for me, too.
Thank you very much!
Not good news I'm sorry to say.
The automatic backup is still failing and filling my SD card with .temp files.
Since updating yesterday afternoon I already have 2 failed automatic backups.
Manual backups are still working.
Not good news I'm sorry to say.
The automatic backup is still failing and filling my SD card with .temp files.
Since updating yesterday afternoon I already have 2 failed automatic backups.
Manual backups are still working.
Update...
About every 5 hours or so LMC is trying to create an automatic backup and is filling my auto folder with .temp files of various sizes.
When does the automatic backup run as it appears to be attempting to create them whilst I'm using my phone?
My phone is an old Samsung Galaxy S8 which hasn't received any OS updates for years (and never will).
I'm going to have to turn off automatic backup until sorted as it's eating up the spare space on my SD card and slowing my phone down whilst it tries to backup.
Fingers crossed a fix is released soon.
All the best...
Update...
About every 5 hours or so LMC is trying to create an automatic backup and is filling my auto folder with .temp files of various sizes.
When does the automatic backup run as it appears to be attempting to create them whilst I'm using my phone?
My phone is an old Samsung Galaxy S8 which hasn't received any OS updates for years (and never will).
I'm going to have to turn off automatic backup until sorted as it's eating up the spare space on my SD card and slowing my phone down whilst it tries to backup.
Fingers crossed a fix is released soon.
All the best...
Please try turning off the backup of "LoMaps and other vector maps" and test the automatic backup again. Thanks.
Please try turning off the backup of "LoMaps and other vector maps" and test the automatic backup again. Thanks.
Hi...
Thanks for coming back so quickly.
Okay I've switched the option off... which should've been off anyway.
My collection of maps is large at nearly 56GB so I've never backed them up using the auto backup.
Did/could the buggy update have switch the option back on again?
All the best...
Hi...
Thanks for coming back so quickly.
Okay I've switched the option off... which should've been off anyway.
My collection of maps is large at nearly 56GB so I've never backed them up using the auto backup.
Did/could the buggy update have switch the option back on again?
All the best...
Bingo... the automated backup is working again!
I've never backed up the maps, so I'm guessing the buggy update must've turned the option back on (but I hadn't noticed).
Just for fun I did a dump of the Android jobscheduler and it was having a right hissy fit as the LM backup kept failing!
Thanks for your patience and help. :)
Bingo... the automated backup is working again!
I've never backed up the maps, so I'm guessing the buggy update must've turned the option back on (but I hadn't noticed).
Just for fun I did a dump of the Android jobscheduler and it was having a right hissy fit as the LM backup kept failing!
Thanks for your patience and help. :)
Replies have been locked on this page!