MerginMaps / MerginMaps/mobile

Delete confirmation input retains previously entered name after cancelling

Open Beginner friendly
#4,665 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Good first issue ui/ux
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

**Description**

When deleting a workspace or account, the user is required to type the account name to confirm deletion. If the user cancels the dialog and reopens it later, the confirmation input field still contains the previously typed name instead of being empty.

**Environment**
Staging

**Application (+ app version, build, operating system)**
Mergin Maps Mobile App
- Android: 2026.3.2 / Samsung Galaxy A53 5G, Android 16
- iOS: 2026.3.2 / iOS 26.0

**Steps to reproduce**
1. Open account settings
2. Tap **Close account**
3. Type the account name in the confirmation input
4. Tap **Cancel** (do not confirm deletion)
5. Reopen the delete dialog

**Actual results**
The confirmation input field still contains the name entered in step 3.

**Expected results**
The confirmation input field should be empty each time the delete dialog is opened.

*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.

Research direction

Start by locating the close-account or delete-confirmation dialog in the mobile app and reproduce the cancel-and-reopen sequence on the affected platforms. Trace where the confirmation input value is retained, then verify that reopening the dialog shows an empty field after cancellation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp, ios
Domain
mobile
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.