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

40° shared this problem 20 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 (6)

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
Leave a Comment
 
Attach a file
You can't vote. Please authorize!