MerginMaps / MerginMaps/mobile

Add button not visible for editor/writer access rights in mobile app – cannot add new record

Open
#4,015 0 comments 0 reactions 1 assignee View on GitHub

@tomasMizera is already working on this.

Since Nov 4, 2025.

bug
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

Description
User with reader access to workspace cannot add new record in mobile app, which is expected. However, if the user is granted editor or writer access rights, they are still unable to add a record because the add button is not visible in the mobile app. The only workaround is to close the current project, open another project, close it, and then reopen the original project where data collection is needed. Issue occurs on both iOS and Android platforms.

Environment
Staging

Application (+ app version, build, operating system)

  • Android: Android 14 (actual version: 2025.4.1)
  • iOS: iOS 18.5 (actual version: 2025.4.0)

Steps to reproduce

  1. Open Mergin Maps mobile app
  2. Log in with a user who has reader access to a workspace (add button not visible, cannot add record)
  3. Change user access rights to editor or writer for the workspace
  4. Open the same project in the mobile app
  5. Observe that the add button is still not visible, and user cannot add a new record
  6. Workaround: Close the current project, open another project, close it, and reopen the original project – add button becomes visible

Actual results

  • Add button is not visible for users with editor or writer access rights after changing permissions
  • User cannot add new records in the mobile app
  • Only workaround is to switch between projects to refresh the UI

Expected results

  • Add button should be visible for users with editor or writer access rights
  • User should be able to add new records immediately after access rights are updated
  • No need to switch between projects to refresh the UI

Screenshots or logs

Conclusion
Created by GitHub Copilot 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.