'Shared local dataset' workflow appears 'broken' due to Android security settings? #5643
timbo-barnes
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've recently got shared local datasets working on Qfield thanks to some help from Lorenz Meyer on the QField ideas page (https://ideas.qfield.org/qfieldcloud-feature-requests/p/qfieldcloud-and-large-data-on-device)*
However, doing so has highlighted some problems (at least for me) with the current expected workflow: Moving the local data to the required folder is fine if you have the device physically connected to your computer via USB, but as far as I can tell, it's impossible to move the file to that location using the file-manager tools on the device itself on Android.
Why is this important? Because if it's not possible to move data to that location, it makes managing (or getting users to 'self-manage') a fleet of devices which I don't have access to, impossible.
I believe the restriction is due to this:
This is a 'protected' area of a device, meaning that if you download the shared local dataset on the device (either via Teams or from a shared QField 'Basedata' project), you can't actually move it into the required folder to make it work:
This is after testing on a few Android devices, none of them rooted or anything- Just a 'standard' device, as a typical QField user might experience it
So, idea:
Either allow qfield to access it's own directory (it can already access the projects directory to see those files?) to allow saving to the localised 'basemaps' director' or allow some method of getting a localised dataset working from the devices root:\basemaps directory (i.e. a non-protected area)
Beta Was this translation helpful? Give feedback.
All reactions