Unable to load project after updating to 2.0.14 #2802
-
Hi all! We've been using Qfield for a project over the last few months and have recently run into an issue. I think that we hadn't been regularly updating Qfield and we were instead looking for the survey season to finish before we did so, but we accidentally updated Qfield to its newest version last week. (2.0.14) Unfortunately, when we now try to open the project on Android we're given the message: "The following layers could not be loaded, please review those and reconfigure the QGIS project." When we access the Qfield data, saved on the android, via the desktop's QGIS we get the error messages seen in the image attached. Things were okay before the update, so we're unsure what happened. Any help would be greatly appreciated! Best wishes, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@AshleyThorntonWWT , QField 2.0 had to significantly change the way it accesses storage on Android, please read this documentation: https://docs.qfield.org/get-started/storage/ That should give you a good idea as to how to import your project currently stored on your device in a location I assume QField has no right to access anymore. As for QGIS desktop error, try to copy your whole project folder off your device onto your desktop, make sure your datasets are present, and open it from there. Sometimes your device might connect via USB in a different mode than "raw" storage access which could cause trouble. |
Beta Was this translation helpful? Give feedback.
@AshleyThorntonWWT , QField 2.0 had to significantly change the way it accesses storage on Android, please read this documentation: https://docs.qfield.org/get-started/storage/
That should give you a good idea as to how to import your project currently stored on your device in a location I assume QField has no right to access anymore.
As for QGIS desktop error, try to copy your whole project folder off your device onto your desktop, make sure your datasets are present, and open it from there. Sometimes your device might connect via USB in a different mode than "raw" storage access which could cause trouble.