Import from OneDrive mostly not working
Hi,
I deleted the app and re-installed fresh.
I am using /media as a folder.
I "imported" the balkans.map (1.6 GB) from a OneDrive folder. It worked (although not on the first attempt), i.e. the map shows in the Locus Map app. Checking with Total Commander, the file is in my /MapsVector folder.
I try to do the same with other maps, e.g. Germany North (2 GB) or Czech (780 MB). This fails after a long (5+ minutes) screen showing "Loading...." and then "Whoops - Code 0".
The OneDrive folder is "Make available offline".
What does "Import" in Locus Map actually attempt to do?
During the long "Loading...." screens, is it failing after a timeout to contact OneDrive, or is it actually importing the file and failing during import? Not sure what I will do with the answer though.
Best,
Armin
The same problem 
As I am evaluating Nextcloud as a OneDrive replacement anyway, I found a way to make it work with Nextcloud. This will work with any other sync program, e.g., Dropbox that allows local Android access to the filesystem (which OneDrive prohibits).
1. Sync *.map file with Nextcloud, Dropbox, etc. between Laptop and Android.
2. Copy the *.map file from .../Android/media/com.nextcloud.client/nextcould/SOMEDIR to .../Android/media/menion.android.locus/mapsVector using an Andoid file management tool. I use Total Commander.
3. Restart LocusMap and select the newly transferred map in Map Manager.
Note: I am not using the LocusMap Map Manager "Import" function, which I criticize in my previous post. It is enough to just copy the *.map file into the mapsVector folder.
Hope this helps anyone coming with the OneDrive problem.
As I am evaluating Nextcloud as a OneDrive replacement anyway, I found a way to make it work with Nextcloud. This will work with any other sync program, e.g., Dropbox that allows local Android access to the filesystem (which OneDrive prohibits).
1. Sync *.map file with Nextcloud, Dropbox, etc. between Laptop and Android.
2. Copy the *.map file from .../Android/media/com.nextcloud.client/nextcould/SOMEDIR to .../Android/media/menion.android.locus/mapsVector using an Andoid file management tool. I use Total Commander.
3. Restart LocusMap and select the newly transferred map in Map Manager.
Note: I am not using the LocusMap Map Manager "Import" function, which I criticize in my previous post. It is enough to just copy the *.map file into the mapsVector folder.
Hope this helps anyone coming with the OneDrive problem.
Hi ,
do you have enough space in your phone storage?
Hi ,
do you have enough space in your phone storage?
Please repeat the action leading to the error again and create a bug report via the in-app reporting system. More info: https://docs.locusmap.app/doku.php/manual:faq:issue_reporting. Thank you.
Please repeat the action leading to the error again and create a bug report via the in-app reporting system. More info: https://docs.locusmap.app/doku.php/manual:faq:issue_reporting. Thank you.
Hi,
Thank you for the logs; they showed us exactly what was going on. Two things were wrong. First, the download from OneDrive really was failing part-way through — your logs show the connection to OneDrive being dropped several times. Second, and this is why the message was so useless, the app was discarding the actual error and just showing "Whoops!" with code 0. In the next version, you will see the real reason instead: a failed download will no longer leave a damaged map file behind, and you will get a progress indicator plus the option to cancel. One extra note: the file Germany-North_oam.osm.map currently in your MapsVector folder is incomplete from one of the failed attempts, so it is worth deleting it manually. We are also working separately on making large downloads survive an unstable connection, which is the real cause of the failures — your workaround of syncing with Nextcloud and copying the file in is a perfectly good approach until that lands.
Hi,
Thank you for the logs; they showed us exactly what was going on. Two things were wrong. First, the download from OneDrive really was failing part-way through — your logs show the connection to OneDrive being dropped several times. Second, and this is why the message was so useless, the app was discarding the actual error and just showing "Whoops!" with code 0. In the next version, you will see the real reason instead: a failed download will no longer leave a damaged map file behind, and you will get a progress indicator plus the option to cancel. One extra note: the file Germany-North_oam.osm.map currently in your MapsVector folder is incomplete from one of the failed attempts, so it is worth deleting it manually. We are also working separately on making large downloads survive an unstable connection, which is the real cause of the failures — your workaround of syncing with Nextcloud and copying the file in is a perfectly good approach until that lands.
Replies have been locked on this page!