Mi!

Now that QfieldCloud is offered as a paid service (which I am 💯 supportive of) bugs like this should be ironed out!! I see hundreds of changes from today which...

All that was changed in-between the working versions was the styling in the project file.

Mostly 2.7.1 is used in the field by the different teams, but not by all teams in the field. I suspect it is a problem with the project. The matching...

See for example these features: * Only the diamond shaped features should have been modified: Move feature, update attributes * (probably due to bad `sourcePk` another feature was moved and...

I uploaded the GeoPackage from the beginning of the working day, re-applied all changes from the day (~500 deltas), and reproduced the same bad state. See job `b6e81eef`. Something is...

After more investigation, I am pretty confident that the `localPk` and `sourcePk` are referring to the same `fid_1`, where instead `sourcePk` should point to `fid`. Subsequently the wrong feature pointing...

Great, thank you! I got all the deltas from the API and will use the day to apply changes locally. If needed I can share the scripts.

Thanks for the heads up. What exotic configuration did we use for our project?

I downloaded the uploaded deltas through the QFieldCloud API (https://app.qfield.cloud/api/v1/projects/) and manually corrected all deltas. Then I applied QFieldCloud's `apply_deltas.py` script on the local project. I had to bugfix `apply_deltas.py`,...

Check for differing fids. QField maintains a local and a remote fid, for our case there was a mismatch, so that the wrong feature was modified by QFieldCloud.