MerginMaps / MerginMaps/mobile

App crashes when syncing a project with a virtual layer after .qgz file is updated

Open
#4,573 1 comment 0 reactions 1 assignee View on GitHub

@uclaros is already working on this.

Since Aug 25, 2026.

android 🤖 bug data corruption - sync failure - crash - anr iOS 🍎 sync
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

Description

When a project containing a QGIS virtual layer is open in the mobile app, syncing a change that includes an updated .qgz project file causes the app to crash. Syncing data-only changes (no .qgz update) works correctly.

Environment
[ ] Staging [x] PROD

Application (+ app version, build, operating system)

  • Mergin Maps mobile 2026.2.0, Android 9 (Samsung Galaxy Tab S3), Android 16 (Pixel)
  • Mergin Maps mobile 2026.2.0, iOS 26.0

Steps to reproduce

  1. Open a project containing a QGIS virtual layer in the mobile app (e.g. tester-ws-1/test_virtual_layer)
  2. In QGIS, open the same project, make a change to the .qgz file (e.g. layer visibility or project settings), save and sync to the server
  3. In the mobile app, trigger sync
  4. The app applies the incoming .qgz update

Actual results

  • The app crashes immediately when applying the synced .qgz project file update
  • After reopening the app, the synced changes are present (data was written successfully before the crash)

Expected results

The app should reload the updated project without crashing.

Notes

  • If the sync contains only data changes (no .qgz update), sync completes successfully
  • Issue is specific to projects containing a QGIS virtual layer
  • Reproducible across all tested devices and platforms

Screenshots or logs

Conclusion
Created by Claude and supervised by a human test analyst.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.