Bug when creating a manual backup with the "LoMaps and other vector maps" option enabled.

40° shared this problem 40 days ago
Solved

Detailed description:

App version: Locus Map Classic 3.70.19 / 3.70.20.

Device: Samsung A50 Android 11, Honor 20 Android 9.

Problem description:

Creating a manual backup with the "LoMaps and other vector maps" option enabled causes a crash. I see the message "Uuups!".

The problem is reproduced every time.

Replies (17)

photo
1

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?

This comment is in trash! Restore
photo
2

I've tried saving locally and to dropbox.

87fd21700c50ec6424bee62ea5a956a223a588470ec2f11b04bf129d9c183d83

This comment is in trash! Restore
photo
1

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

This comment is in trash! Restore
photo
1

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.

This comment is in trash! Restore
photo
2

Thanks, we managed to identify and fix the bug. Please wait for the next app version.

This comment is in trash! Restore
photo
1

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.

This comment is in trash! Restore
photo
1

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).

4d6eea5f1eba4e09a57e150294c18bd914acf8935db45579ca02f42dc275bfaf

Logcat extract:

09-12 10:31:33.645 10391 22507 22557 E q       : backupDataSync(2026-09-12_10-31-23, [E6.e@7be1046, E6.b@1067207, E6.a@ee6df34, E6.a@687115d, E6.a@9baead2, E6.a@88e27a3, E6.c@facbaa0, E6.c@5286659, E6.b@338e21e, E6.a@5519aff, E6.d@132e0cc, E6.d@cf00f15], false)
09-12 10:31:33.645 10391 22507 22557 E q       : java.util.zip.ZipException: duplicate entry: mapsVector/_themes/Elements/Elements.png
09-12 10:31:33.645 10391 22507 22557 E q       : 	at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:246)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at l9.a.b(SourceFile:232)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at l9.a.b(SourceFile:266)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at l9.a.b(SourceFile:266)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at E6.d.d(SourceFile:18)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at k9.v.c(SourceFile:291)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at k9.q.invokeSuspend(SourceFile:22)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at sj.a.resumeWith(SourceFile:9)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at Sk.L.run(SourceFile:115)
09-12 10:31:33.645 10391 22507 22557 E q       : 	at Zk.a.run(SourceFile:96)

This comment is in trash! Restore
photo
1

Right... so after just posting a new topic regarding backup issues, there is a known backup bug in LM v3.70.20?

This comment is in trash! Restore
photo
1

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 :)

This comment is in trash! Restore
photo
2

Hi all,

Locus Classic 3.70.21 has just been added to https://bit.ly/lmVersions.

This comment is in trash! Restore
photo
1

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!

This comment is in trash! Restore
photo
1

Yep, 3.70.21 works for me, too.

Thank you very much!

This comment is in trash! Restore
photo
1

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.

This comment is in trash! Restore
photo
1

> The automatic backup is still failing and filling my SD card with .temp files.

In my case I have 2 ".temp" files: one in the backup folder and another one in the auto folder. As they contains the maps they are pretty big, but there are no multiple ones.

Of course I think they shouldn't be there after the backup completes correctly (and probably neither if it fails).

C:\>adb shell ls -lhR /storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/backup
/storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/backup:
total 5.7G
-rw-rw---- 1 u0_a391 ext_data_rw  39M 2026-08-24 19:20 2020-09-16_19-05-07.zip
-rw-rw---- 1 u0_a391 ext_data_rw  40M 2026-08-24 19:20 2023-05-19_22-51-13.zip
-rw-rw---- 1 u0_a391 ext_data_rw  47M 2026-08-24 19:28 2026-08-24_19-27-54.zip
-rw-rw---- 1 u0_a391 ext_data_rw 2.6G 2026-09-16 15:22 2026-09-16_15-19-33.temp
-rw-rw---- 1 u0_a391 ext_data_rw 2.9G 2026-09-16 17:05 2026-09-16_17-02-28.zip
-rw-rw---- 1 u0_a391 ext_data_rw  31M 2026-08-24 19:20 Note9.zip
drwxrws--- 2 u0_a391 ext_data_rw 3.3K 2026-09-17 13:17 auto

/storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/backup/auto:
total 5.4G
-rw-rw---- 1 u0_a391 ext_data_rw  47M 2026-08-24 19:20 2026-08-15_13-58-17_Locus_Map_Classic.zip
-rw-rw---- 1 u0_a391 ext_data_rw 2.9G 2026-09-16 17:26 2026-09-16_17-17-11_Locus_Map_Classic.zip
-rw-rw---- 1 u0_a391 ext_data_rw 2.4G 2026-09-17 13:24 2026-09-17_13-17-32_Locus_Map_Classic.temp

This comment is in trash! Restore
photo
2

Please turn off "LoMaps and other vector maps" and "Personal maps" in the backup contents. These are only used when the migration to Locus Map 4 is done.

This comment is in trash! Restore
photo
2

Yep, apparently update v3.70.20 had automatically turned on those two options for me and, like Žilina below, I wasn't aware of them.

This comment is in trash! Restore
photo
1

Yep... I'd have to agree with virtualdj.
I've now just turned off "Personal maps" also, but as the folder was empty it wasn't an issue for me.

This comment is in trash! Restore
photo
photo
1

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...

This comment is in trash! Restore
photo
1

Please try turning off the backup of "LoMaps and other vector maps" and test the automatic backup again. Thanks.

9c5308e3ca625426dfa0150e49fd4c178a811b88b7edef04efc289ed54e973d3

This comment is in trash! Restore
photo
1

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...

This comment is in trash! Restore
photo
1

> 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).


I think I'm in the same yours situation: I checked the previous auto backups and they never had a size greater than 50 MB. So I'm pretty sure the maps have never been backed up.

This comment is in trash! Restore
photo
photo
1

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. :)

This comment is in trash! Restore
Leave a Comment
 
Attach a file