Cannot sync QFieldCloud project to Android: permission_denied_plan_insufficient

[max-mapper]

I am only using 5MB of my free 100MB. I get the error message: permission denied becasue the useraccount's plan is insufficient

[nealmaker]

I'm getting the same error, and only using 3.2 of my 100MB.

[Oisin-JK]

Me too - see #4409

[christabone]

I had the same error with my app -- it started after clearing the data & cache of the app in an attempt to force a refresh of an update from QFieldCloud.

Unfortunately, the only way I was able to resolve this error was by making a copy of the project, deleting it from QFieldCloud, and remaking it again.

[L10ns]

Anybody knows if the problem was solved?
I have the same problem now.
The problem was occured about one month ago. Nothing change since before: no postgis files, no basemap layer added. I just added one light geopackage file. One day problem came out and started to report "network error...". Today I understood was for "permission_denied_plan_insufficient".
I collected some data now and I need to export to cloud and then to the pc.
I have a Community account and I'm not exceeding the 100 mb.
As I told already, nothing change before the error came.
Here my versions:
Qfield app: v. 3.4.4
Qfield Sync: v. 4.11.0

[nirvn]

@L10ns , can you type your cloud user name and project name here? If you feel uneasy doing that here, send over to [email protected] -- do not send a password. Thanks.

[BoswachterMarc]

No problem with our community/volunteer project of 75MB...
(QGis 3.40 on Ubuntu 22.04.05 LTS, plugin QFieldSync 4.11.0 and QField 3.4.3 Ebo)

[nordewal]

I have the same issue. It is a 33 MB project and does not use PostGIS, only local files. I tried removing the project and re-installing the app. Neither helped.

@nirvn the user is galegge and the project name Galegge. Any help would be appreciated!

[nirvn]

@nordewal , I'll have a look within the next 48 hours.

[SeqLaz]

Hi @nordewal ,

After investigating the job logs of your project, I found that the package synchronization failed because the project contains virtual layers, which are not allowed in the Community plan.

As recommendation is to exporting your virtual layers as a GeoPackage or duplicating the layers used to create the virtual layer. Then, directly filter your query in the Layer Properties > Source and use the "Provider Feature Filter" for querying.

[nordewal]

Thanks for investigating and for the recommendation on how to work around this issue. Given that most of our edits are in that base layer, it would be quite some work to always update/export that layer instead of using virtual ones.

I wasn't aware that virtual layers are not supported for community projects. Should this be added to the detailed comparison on the pricing page? Or even better, allow community projects to use virtual layers? 😄

[SeqLaz]

@nordewal This feature is not currently supported by the community plan. However, it is in our backlog, and we plan to make it available for community plans in the future.

[nordewal]

That's awesome to know! Do you have something (FR, mailing list,...) I can follow along for when it's available?