-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Synchornizing from Qfield is not working #528
Comments
@Ipickedausername , that is super odd. Have you tried to use the 'Send compressed folder to...' action when clicking on the DCIM folder's 3-dot menu in QField? |
@Ipickedausername , could you try the APKs here with a project of yours: opengisch/QField#4402 -- photos should be visible there. |
Hello,
This option works to extract pictures from the phone and send them to another app in order to open them on my computer.
With these APKs, if I open my project, it is empty. Is there something we are supposed to do before synchronizing data ? Copy the folder somewhere, synchronizing inside the phone... I didn't find such options and I wasn't doing it before. |
@Ipickedausername , right, it'd be empty because the APK has a different app name (i.e. ch.opengis.qfield_beta instead of ch.opengis.qfield). Can you take a few dummy photos and check if you see them when connecting with your USB cable? When you confirm the test photos are visible, we can push an official QField 2.8.4 on the playstore, you'll be able to then see the photos in your main project. |
I took 3 pictures. I can see them in the folder of the project: But empty on windows. Is there something I'm missing ? Before the modifications related to google's policy changes, it was quite simple to get pictures from the phone. But maybe something has changed ? It is like pictures are saved somewhere in Qfield, but without path. I check the whole phone to find these pictures. Nothing.. ^^' |
@Ipickedausername , are you sure you are looking in the right directory? From the last windows explorer screenshot, it doesn't look like you are looking inside your Galaxy S9+, i.e.: Your original explorer screenshot showed a Galaxy S9+ in the path here: Are you using the all access APK or the play store version? If it's the latter, the photos should be somewhere in /Android/data/ch.opengis.qfield/files/Imported projects/Project_MSI/DCIM. Also, do you have other folders in your project folder alongside DCIM? Can you check if photos are located somewhere else? |
@Ipickedausername , and you're 100% sure you are looking into ch.opengis.qfield_beta? sorry, just want to make sure our wires aren't crossing :) |
I looked into : ch.opengis.qfield_beta There is a bug with windows/my phone. I checked twice, and I did it again because of your message. And now I can find all the projects from Qfield master-dev. |
But I still cannot synchronize it with my original project using QfieldSync. |
@Ipickedausername , by "now I can find all the projects from Qfield master-dev", you mean you can see the photos of your projects you took with QField master-dev? |
Yes I can see them. Can copy them from windows. |
Hello,
After collecting data with Qfield, when I try to synchronize these data to my original project, I simply cannot.
I receive this message : QFieldSync: Opened original project (with the project path).
Since Qfieldsync is not working well since the beginning (or I cannot make it work), I used to manually extract data from the Qfield project and add it to my data.
But now, I can't see my data in the Qfield project (but it does exist in my phone).
Same issue with pictures. Before I could see them in the DCIM folder, but now this folder is empty (but the pictures are visible in my phone).
Is there something wrong I do ?
The picture can be taken and displayed on my phone:
Pictures are well saved in the DCIM folder, on my phone (with a correct name):
But doesn't exist in my phone's directories when opened on windows:
The project is found in my phone from Qfield, but not when I'm searching for it on my phone.
thank you for your attention
The text was updated successfully, but these errors were encountered: