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
In the latest version of DSA built for Android, I am seeing that tilecache pngs are put in that files folder, which show up when browsing for operational data (I think we had purposely made the Add Data tool look both in OperationalData and the base directly. One way to get around this would probably be to create a DSA folder under files, which then had the DsaAppConfig.json and data folders in it. But again, it is still frustrating to have to use Android Studio to manage that folder.
Note, this will become moot once we are able to store the DSA data files in a different location than the internal app sandbox area (see #372).
The text was updated successfully, but these errors were encountered:
@kerryrobinson
Try allowing the App to run once and create the sandbox folders along with the default config file.
Should be here: /data/data/com.esri.arcgisruntime.opensourceapps.DSA_Handheld_Qt/files/ArcGIS/Runtime/Data/DSA
Then place your config and data, etc in this relative location.
kerryrobinson
changed the title
Tile cache files stored in same location as DSA data
Android: Tile cache files stored in same location as DSA data
Nov 6, 2024
In the latest version of DSA built for Android, I am seeing that tilecache pngs are put in that
files
folder, which show up when browsing for operational data (I think we had purposely made the Add Data tool look both inOperationalData
and the base directly. One way to get around this would probably be to create aDSA
folder under files, which then had theDsaAppConfig.json
and data folders in it. But again, it is still frustrating to have to use Android Studio to manage that folder.Note, this will become moot once we are able to store the DSA data files in a different location than the internal app sandbox area (see #372).
The text was updated successfully, but these errors were encountered: