OAM mapsVector files remain after removal
Solved
despite deleting offline maps all *.db and *.poi files are still in Android\data\menion.android.locus.pro\files\Locus\mapsVector and taking > 10GB of space
Files:
Screenshot 2024...
The same problem 
Hi,
how exactly did you delete the maps? Could you please describe the process step by step? Thanks.
Hi,
how exactly did you delete the maps? Could you please describe the process step by step? Thanks.
Just by clicking delete button.
Map manager -> Offline -> three dots delete. Nothing fancy.
Just by clicking delete button.
Map manager -> Offline -> three dots delete. Nothing fancy.
I've noticed that deleted map is still visible for a while (few app restarts),
I've noticed that deleted map is still visible for a while (few app restarts),
Thanks, the issue has been forwarded to the devs.
Thanks, the issue has been forwarded to the devs.
Oh and by visible I mean actual map is visible not listed in my maps.
Oh and by visible I mean actual map is visible not listed in my maps.
Locus is doing caching; maybe this is the reason.
Have you tried deleting the Locus cache (search (upper right) for cache in settings)
Locus is doing caching; maybe this is the reason.
Have you tried deleting the Locus cache (search (upper right) for cache in settings)
I've deleted it manually but that's not the reason. I've bicycled through Europe with 2 friends, downloaded the same maps and they don't have this problem. It's not a problem for me, as I've mention, I've deleted it. But that's something for developers to take into consideration because most of users will not be aware if bug exists in their configuration.
I've deleted it manually but that's not the reason. I've bicycled through Europe with 2 friends, downloaded the same maps and they don't have this problem. It's not a problem for me, as I've mention, I've deleted it. But that's something for developers to take into consideration because most of users will not be aware if bug exists in their configuration.
The issue has been fixed. Please wait for the next app version.
The issue has been fixed. Please wait for the next app version.
Replies have been locked on this page!