MerginMaps / MerginMaps/mobile
Registration with an already existing email succeeds without error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Description
When a user attempts to register in the mobile app using an email address that is already registered, the registration flow completes successfully without any error. The user can proceed through the full onboarding: register → create workspace → create project. Only when attempting to upload a project does the user see an error: "Failed to push changes. Ask the workspace owner to log in to their Mergin Maps dashboard for more information. (TrialExpired)".
The root cause is likely that duplicate email registration is not validated in the mobile app (or the server error is not surfaced), leaving the user in a broken account state.
Environment
[x] Staging [ ] PROD
Application (+ app version, build, operating system)
Mergin Maps iOS — 2026.4.0
iOS: 26.0
Steps to reproduce
- Take an email address that already has a registered Mergin Maps account
- Open the mobile app and tap Sign up
- Fill in the registration form using the existing email
- Complete the full onboarding flow (create workspace, create project)
- Attempt to upload/sync the project
Actual results
Registration succeeds with no error. The user completes onboarding and creates a project.
Expected results
Registration with an already existing email should fail immediately with a clear error message (e.g. "An account with this email already exists"), preventing the user from entering a broken state.
Screenshots or logs
Conclusion
Created by Claude and supervised by a human test analyst.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the mobile app's Sign up registration flow and reproduce the duplicate-email case on staging, then trace whether the server response is validated or surfaced. Done means an existing email stops registration immediately with a clear error, without allowing onboarding or project creation to continue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, ios
- Domain
- authentication, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100