-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Labels
bugdata corruption - sync failure - crash - anrThe most critical classificationThe most critical classification
Description
Description
A .gpkg file is removed from the project in QGIS plugin (and synced to the server), and the next sync on mobile should remove the file from mobile device as well. Instead, a subsequent mobile sync re-uploads the deleted .gpkg back to the server, and it reappears again in QGIS plugin after the next pull/sync.
This looks like mobile treating the missing file as something to upload (no deletion/tombstone applied), causing the file to be “brought back”.
Environment
Staging/PROD
Application (+ app version, build, operating system)
- QGIS version: 3.44.7-Solothurn
- MM plugin version: 2026.1.2
- iOS version: iOS 26.0
- iOS app build: 26.2.860811
Steps to reproduce
- Have a project containing a
to_delete.gpkgfile. There are no pending changes in the project on plugin side. - In Mergin Maps mobile app, add/edit some records to
to_delete.gpkgand sync changes to server. - In Mergin Maps plugin in QGIS, pull/sync the project to get the mobile changes.
- Remove the
to_delete.gpkgfile from the project directory on disk (file system). - Sync in QGIS plugin (known behavior: sync fails; user restarts QGIS, reopens the project, removes unavailable layers, then syncs again - bug).
- After the successful plugin sync, confirm the
to_delete.gpkgfile is removed on server (project no longer contains theto_delete.gpkg) -> see screenshot A - On mobile app, run sync (expected:
.gpkgshould be removed locally too). - Run sync again on mobile app.
Actual results
- After the
.gpkgis removed from server, mobile sync does not persist the deletion locally as expected. - A later mobile sync re-uploads the deleted
.gpkgback to the server -> screenshot B - After the next QGIS plugin sync/pull, the
.gpkgreappears in the plugin too.
Expected results
- Once the
.gpkgis removed from server, the mobile client should remove it locally on next sync (or clearly report why it cannot). - Mobile should not re-upload a file that was deleted remotely (unless user explicitly restores it / resolves a conflict).
Screenshots or logs
A
**B**
Conclusion
Created by GitHub Copilot and supervised by a human test analyst.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugdata corruption - sync failure - crash - anrThe most critical classificationThe most critical classification