I try to setting my project on QFieldCluod, and for each layer that I created on myself, I get this kind of error “Exported layer ‘layer_name’ is not valid: ‘invalid_dataprovider’”. Can someone help me?
Open question by RubenSadei migrated from Error: Invalid_dataprovider · opengisch/qfieldcloud-beta · Discussion #8 · GitHub
Imported from GitHub discussion by @m-kuhn on 2021-06-18T05:05:55Z
Hey, RubenSadei. Thanks for testing QFieldCloud. Can you give more details about your layers? I guess they are some kind of online provider (PostGIS, WFC etc) that require login credentials OR point to a host that is not available from QFieldCloud (localhost, 0.0.0.0, etc). Ideally you can share your project with us.
Imported from GitHub comment by @suricactus on 2021-06-18T09:46:01Z
I think I am having the same issue - I posted about it here: https://github.com/opengisch/qfieldcloud-beta/discussions/1#discussioncomment-803842. From your reply about, I think I misunderstood that the Postgres database needs to be hosted publicly.
Imported from GitHub comment by @niall-quinlan on 2021-06-20T15:55:56Z
Hi, niall-quinlan . Sorry I missed your comment there. Yes, Postgres database should be publicly available in order to prepare package your layers on QFieldCloud and make you project available on any device.
Imported from GitHub comment by @suricactus on 2021-06-20T20:50:02Z
suricactus Thanks, how can I share my project? In my project I’ve online provider, but these don’t give me troubles!
Imported from GitHub comment by @RubenSadei on 2021-06-22T11:37:39Z
I fixed the problem, but not in the best way. If I move all shapefiles to the same folder as the project then it no longer gives me this error and everything works. But from a practical point of view, in keeping the files in order, it is quite problematic.
I’ve tried loading an online layer, for example the one from google sattelite, it partially loads the image. I think this is also a bug.
Imported from GitHub comment by @RubenSadei on 2021-06-22T12:31:17Z
Hi, RubenSadei.
Yes, QFieldCloud assumes all your files are in the same directory. There is an upcomming functionality for QFieldSync to collect all your files in the same folder, so you don’t need to do this manually.
On the Google Satellite problem, can you elaborate more? What do you mean by “partially loads the image”? What is the image - a local raster file, WMS, XYZ layer? Did you mark it also as base layer? BTW, feel free to open a new question in discussion to resolve your Google Satellite problem.
Imported from GitHub comment by @suricactus on 2021-06-22T12:59:36Z
In order to provide a clearer and more manageable discussion forum and to have all discussions about QField and related products (i.e. QFieldCloud and QFieldSync) in a single place, we transferred all the discussions from the QFieldCloud to the QField repository.
Imported from GitHub comment by @marioba on 2022-02-01T13:22:11Z
Imported from GitHub comment by @Nioigte on 2022-03-10T17:41:23Z
Opening a new issue/discussion, describing your project and data (data providers and files you have), pasting the QFieldCloud feedback text and screenshot, uploading an example project (if possible) and using less capital letters will drastically increase the chances someone helps you. 
Imported from GitHub comment by @suricactus on 2022-03-10T18:13:40Z
I also had this problem with my Shapefiles (local files, no database involved) . The trick is to choose the layer that has the issue and edit it in QGIS. By editing I mean, simply add some attributes to one of the features or digitize a feature. After you finished the editing, try Uploading it to QFieldCloud or Synchronize it. It should work without issue now . You can delete the edits you made earlier via QGIS or Qfield app if you want.
Imported from GitHub comment by @shafibaj07 on 2024-11-06T09:16:10Z