You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
Please describe your issue in as much detail as possible:
When selecting "import destinations" from the menu, the menu closes and map returns with no apparent actions. What I supposed to happen?
The manual (http://info.zanavi.cc/manual/) should document the "import destinations" feature, especially if a hard-coded filename is being read (as opposed to asking the user to select a file to import).
It's the same problem for "export destinations". Nothing appears to happen. Intuitively, one might expect to find a file in /mnt/sdcard/zanavi/, but that directory doesn't exist and there is no evidently no file in the whole filesystem (unless perhaps it's well hidden).
Steps for reproducing this issue:
menu >> "import destinations"
Screenshots (if possible):
The text was updated successfully, but these errors were encountered:
ghost
changed the title
The "import destinations" feature does nothing. The online manual omits the feature.
The "import destinations" feature does nothing. Bug 2: The online manual neglects to cover the feature.
May 22, 2017
The code shows that the "import destinations" feature tries to read from: /data/data/com.zoffcc.applications.zanavi/share/. This filespace is unreachable to users, which means it will only work on rooted devices.
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
Your system information:
ZANavi Version: 2.0.56
App from Google-Play / F-Droid / other: f-droid
Android OS Version: 2.3
Device:
Please describe your issue in as much detail as possible:
When selecting "import destinations" from the menu, the menu closes and map returns with no apparent actions. What I supposed to happen?
The manual (http://info.zanavi.cc/manual/) should document the "import destinations" feature, especially if a hard-coded filename is being read (as opposed to asking the user to select a file to import).
It's the same problem for "export destinations". Nothing appears to happen. Intuitively, one might expect to find a file in /mnt/sdcard/zanavi/, but that directory doesn't exist and there is no evidently no file in the whole filesystem (unless perhaps it's well hidden).
Steps for reproducing this issue:
menu >> "import destinations"
Screenshots (if possible):
The text was updated successfully, but these errors were encountered: