Delete confirmation input retains previously entered name after cancelling

Open Beginner friendly

#4,665 opened on Aug 25, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 72/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: android, cpp, ios
Domain: mobile

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.

Description

bug Good first issue ui/ux

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

Open account settings
Tap Close account
Type the account name in the confirmation input
Tap Cancel (do not confirm deletion)
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.

Dominant language: C++
Stars: 388
Forks: 87
Avg merge: 4d 4h
Merged PRs (30d): 21

Contributor guide

Open the contributing 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.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues