Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot open the project file when the export folder is defined by UNC path #501

Open
jpdupuy opened this issue Mar 10, 2023 · 4 comments
Open

Comments

@jpdupuy
Copy link

jpdupuy commented Mar 10, 2023

Describe the issue

On Windows 10, QField reports an error when opening a local project file which has been defined in an export folder based on a UNC path (network folder)

Reproduction steps

Steps to reproduce the behavior:

  1. Configure QFieldSync to Export your project (cable export) in a network folder instead on C:/users//QField/export/ (see screenshot)
  2. Install QField for Windows on your desktop
  3. Open QField on your desktop, and select "a local project"
  4. Select your exported project from from network folder

Expected behavior

The map should be displayed without error message

Observed behavior

A blank map and an error message (see screenshot):
Le fichier de projet "/QFieldProjet/Infrastructure/Export/GAZ_qfcloud_edu_qfield.qgs" n'existe pas

Screenshots and GIFs

image

image

[Please also attach additional files if a specific project/dataset is useful to investigate the problem.]

Desktop (please complete the following information)

  • OS: [Windows]
  • QGIS Version [3.28.4]
  • QFieldSync Version [4.4.8]

Mobile (please complete the following information)

  • Device: [Desktop]
  • OS: [Windows 10]
  • QField version: [2.7.0)]

Additional information

  • Problem started happening recently, didn't happen in an older version of QField: [No]
  • Problem can be reliably reproduced, doesn't happen randomly: [Yes]
  • Problem happens with all files and projects, not only some files or projects: [Yes]

[If the problem happened with QFieldCloud, please add your username and project name.]

@m-kuhn
Copy link
Member

m-kuhn commented Mar 12, 2023

Does it work to mount the UNC path to a drive letter (as a workaround)?

@m-kuhn
Copy link
Member

m-kuhn commented Mar 12, 2023

Likely related to
https://bugreports.qt.io/browse/QTBUG-68634

@suricactus suricactus transferred this issue from opengisch/QField Mar 12, 2023
@jpdupuy
Copy link
Author

jpdupuy commented Mar 13, 2023

I have also tired this way, but it does not work . :-(

@meyerlor
Copy link

meyerlor commented May 8, 2024

I have occured the same problem - my usual set up for Qfield is:
H:/Customer_Folder/
|____QGIS Project
|____Qfield Cable
|____Re-Import

I set up the QGZ / data in the QGIS Project folder, then i sync it with QfieldSync plugin into the Qfield Cable folder. This results into random behaviour:
Some layers (marked for offline editing for cable sync) work, some get a "../QField Cable/Trees.gpkg" as datasource (when investigating within the created .qgs file), some only have "./Trees.gpkg" as datasource - the latter are working. I can manually manipulate the .qgs before copying it on my tablet, but this is kind of a nasty work around.

This is all happening on a network drive H:/

If i select C:/temp/ for example as output folder in QfieldSync, everything just works fine - which is a better workaround, but still requires manually copying the files back into my Customer_Folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants