MerginMaps / MerginMaps/qgis-plugin

QGIS crashes when downloading a project on MacOS

Open
#866 1 comment 0 reactions 1 assignee View on GitHub

@harminius is already working on this.

Since Jul 16, 2026.

bug critical Geodiff
Dominant language
Python
Stars
44
Forks
20
Avg merge
3d 12h
Merged PRs (30d)
5

Description

My setup:

  • Intel MacBookPro Late 2015
  • MacOS Monterrey 12.7.6
  • QGIS 3.44 Solothurn
  • Mergin qgis-plugin version 2026.1.1

Steps to reproduce:

  • Configure mergin plugin (custom server addr, user and pass). Test connection (returns green OK)
  • At the browser panel, expand Mergin Maps (it correctly list my projects), right click on a project, click in "Download"
  • File browser opens, select destination directory, hit Accept

Result:

  • Sync dialog briefly flashes, and QGIS silently crashes. OS reports EXC_BAD_ACCESS

What i found out:

I've been able to debug the plugin with first-aid, and found out it was something related to the geodiff package. Couldn't get to the bottom of the problem, but as I noticed it was using version 2.1.2, just tried to install the latest version of the package.

My steps:

  • Clone geodiff source code from git
  • Download dependencies (specifically sqlite-autoconf-3450000)
  • ./configure sqlite with --enable-dynamic-extensions flag, and compile it
  • follow geodiff instructions to compile it
  • replace pygeodiff directory at ~/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/Mergin/mergin/deps with the last version
  • rename libpygeodiff.dylib (result of compiling geodiff) to libpygeodiff-2.2.0-python.dylib and move it inside the newly replaced pygeodiff directory.

After all this, the mergin plugin was able to download and sync projects.

Maybe is just a matter of packaging the mergin plugin with the latest version of geodiff, but I'll let decide that to maintainers!

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.