Please note: We are not responsible for issues in the F-Droid build.
Kindly try using our official version from Google Play or the latest nightly build and see if the issue persists there.
and
We have tested the described steps but were unable to reproduce the issue.
So I report it here – is it an issue specific to the F-Droid build?
If not, what might be the issue, and how could I at least manually once export the settings so that I can re-import in a fresh re-installation?
(I have moved the stored assets from “internal app storage” to external SD card (“Multiuser Storage 2”) before. I don’t know if this affects it.)
The issue is:
When exporting settings, no file is created. Progress shows NaN% 0/ 0 MB, saving the file fails with Error: java.io.IOException: read failed: ENOENT (No such file or directors)
Description
When exporting settings to a file, during export dialogue says “0/0Mb” and no file is created.
I have created a screen record that shows the behavious. In the end, when trying to safe the file it errors with Error: java.io.IOException: read failed: ENOENT (No such file or directors).
(Note that the wait times are times where the system stays unresponsive because most probably it does calculations.)
Video:
Steps to reproduce
Go to “Settings” → “Import/export” → “Export to file”.
Select from “Settings” all, and from “Resources” “Rendering Style”, “Routing” and “Online routing engines”.
Wait for the export to be generated, and while doing so see a progress window showing NaN% and 0/ 0 Mb.
When finished, try to save the file, which errors with Error: java.io.IOException: read failed: ENOENT (No such file or directors).
Have also tried it to share to my email programme, same issue. Sharing other export files from other Apps works.
Actual result
Error: java.io.IOException: read failed: ENOENT (No such file or directors).
Sorry, I did not see your point of already having raised with OSM&. I have updated my comments.
Someone here will surely help, but raising in parallel at gitlab under f-droid will help is it is a bug/prod issue.
I have not raised it with OSM and still do not understand why this is a mapping issue to be raised with OpenStreetMap. Only with OsmAnd I did report it, and that I did link in my initial post. Hm.
Anyway, since you seem happy, maybe we delete all our little side-discussion to keep this here clean?
(menu structure is a bit different for me, probably due to different Android version/ flavour)
Is already allowed.
I explicitly do not want and can store downloaded maps there because of size, that’s why I am on the vfat partition (“external”, not-adopted storage) of the dedicated SD card.
I am OK with playing around again with the settings when I find a way to (manually) backup them first, maybe by manually copying files from the file system. (I have root access.)