QFieldSync Feature Requests

If I upload a test project with a single empty layer, I will be able to successfully upload it using QField Sync. However, when I download it in QField, I will get a packaging error. The projects's problem is that I have no features in my layer, so no extent is defined for the project. Easy to fix. Once I found the problem, I added a point and now everything is ok. However, the response is really confusing. From QField I get nothing but "packaging error, download failed." And if I go to the Admin site, the log is mysterious. (I do have a private installation of QFieldCloud which is getting a bit stale, so it is possible that QFieldCloud in its current version gives a better error..) The real error is classified as ENTRYPOINT INFO. So it looks not fatal. And if I dont know where to look in the Jobs logs, I wont find the message. My proposal is, that QField Sync shouldn't let the project sync in the first place if it doesnt have an extent. It would be nice if checks for this project error, and other validity errors like it, were pushed into the QFIeld Sync plugin so that the upload of such a project is blocked. Here might also be a good place to check that layers have primary keys, for instance. 07:32:39.307 ENTRYPNT INFO Preparing QGIS project for packaging… 07:32:39.307 root INFO Loading QGIS project "/tmp/tmp241m8jrc/files/test_foto_sync.qgz"… 07:32:39.307 root INFO Skip loading QGIS project "/tmp/tmp241m8jrc/files/test_foto_sync.qgz", it is already loaded 07:32:39.307 ENTRYPNT INFO Getting project area of interest… 07:32:39.307 ENTRYPNT INFO Failed to obtain the project extent from project layers. 07:32:39.312 QGSSTDERR WARNING Logged warning: Loading a file that was saved with a newer version of qgis (saved in 3.42.2-Münster, loaded in 3.36.3-Maidenhead). Problems may occur. ::>>>::6bc6a767-f7d9-416e-a05c-594493f2442f 1 07:32:39.484 root INFO Stopping QGIS app… 07:32:39.591 root INFO Deleted QGIS app!

Currently the 'Local Directory' path seems to be stored in the user QGIS profile, and is not shared among users. As we have multiple people intersted in viewing the local version, this can result in confusion as to where to sync it to and erors made in this process. It would be better if this directory paths i ssved to a shared location (project properties? QfieldCLoud?) so everyone is able to use that path if someone defines it. In additon it is possible to accidently put the wrong path in and sync the wrong data to the wrong location (if the projects ar setup with the same structure). Ideally some checks are made that prevent this happening.

As a user I am able to create image stamping template, but isnt possible to add the features values in the stamp from the same layer different field. For example I need to take borehole pictures and it would be nice if borehole number would appear as stamp automatically on the picture (with some additional information).

With multiple Qfield users collecting photos stored in the attachment directory (i.e. 'DCIM') and synchronizing to the cloud, synchronizations of the project by other users gets slower and slower as they are forced to download all other users photos/attachments. In some cases, these large data aren't needed on each device involved in a project so it would be great to choose a synchronization method for the attachment directory: 1) (current method)- Attachments from Qfield are synchronised to the cloud and available on other devices 2) Attachments from Qfield are synchronised to the cloud but not available on other devices 3) Attachments are not synchronised 1) and 2) would still allow the owner of the project to download the attachments to the project folder using QField sync toolbar/plugin. 3) would require manual retrieval from the device or some other method.