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
There seems to be a new problem with permissions, at least for me on a new Android 14 device:
We already knew that sine long now Qfield cannot read files that are not in its own folder, so that we have to do the "import project" thing.
Anyway until now there were applications like File Manager+ or Automate that were able (aka had permissions to) to navigate/read the Qfield imported projects folder, and that was really important especially to get photos out of there (via SFTP for example or by uploading them to a gdrive account), without needing to do the "export" thing with QField considered also that it tends to block/stop (at least for me) when the project folder has many files like photos and alike.
Now those apps have lost the ability to navigate the /Android/data folder... that makes very hard to take files/pictures out of the imported projects folder (again, the qfield "export" functionality is not an option to do it routinely on a folder that gets bigger and bigger each day spent on the field gathering data and taking pictures), leaving as only option the USB cable... which has its own downsides.
I'm missing something or getting something wrong here?
Any suggestion?
The text was updated successfully, but these errors were encountered:
I found that this https://play.google.com/store/apps/details?id=com.folderv.file can still access Android/data (after having tested at least 7/8 other file managers), but I guess for how long it will work until Google will lock the door this app is using.
Still... the number of jumps needed to get photos out of qfield folder and have them uploaded to some remote storage makes the process very painful. I understand is not qfield fault, just trying to understand what are the option for the present and next future.
This is also a problem when trying to implement use of shared datasets- Unless moving shared datasets (i.e. a imagery layer) onto the device with a physical cable, there's no way to do it because the required location is blocked/inaccessible by Android.
There seems to be a new problem with permissions, at least for me on a new Android 14 device:
We already knew that sine long now Qfield cannot read files that are not in its own folder, so that we have to do the "import project" thing.
Anyway until now there were applications like File Manager+ or Automate that were able (aka had permissions to) to navigate/read the Qfield imported projects folder, and that was really important especially to get photos out of there (via SFTP for example or by uploading them to a gdrive account), without needing to do the "export" thing with QField considered also that it tends to block/stop (at least for me) when the project folder has many files like photos and alike.
Now those apps have lost the ability to navigate the /Android/data folder... that makes very hard to take files/pictures out of the imported projects folder (again, the qfield "export" functionality is not an option to do it routinely on a folder that gets bigger and bigger each day spent on the field gathering data and taking pictures), leaving as only option the USB cable... which has its own downsides.
I'm missing something or getting something wrong here?
Any suggestion?
The text was updated successfully, but these errors were encountered: