Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Layers list search clear (✕) requires two back-arrow taps to return to map

Open
#4,655 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the issue in the Mergin Maps mobile app by opening Layers, searching, clearing the search, and tapping the back arrow. Trace the Layers list search-clear handling and back-navigation state, then verify that clearing the search followed by one back tap returns directly to the map canvas on Android and iOS.

Written by the indexing model from the issue text.

Description

bug ui/ux

Description

When a user searches for a layer in the Layers list (opened from the bottom menu) and then clears the search by tapping ✕, an extra navigation state is pushed onto the stack. As a result, tapping the back arrow once returns to the search state instead of the map canvas, requiring a second tap to fully exit the Layers list.

Environment
[x] PROD

Application (+ app version, build, operating system)
Mergin Maps Mobile App

  • Android: 2026.3.2 / Android 9
  • iOS: 2026.3.2 / iOS 26.0

Steps to reproduce

  1. Open a project in Mergin Maps mobile app
  2. Tap the Layers icon in the bottom menu to open the Layers list
  3. Type any text in the search field to filter layers
  4. Tap ✕ (clear/reset) to clear the search
  5. Tap the back arrow to return to the map canvas

Actual results
The first back-arrow tap does not return to the map — it appears to dismiss the search state but stays in the Layers list. A second back-arrow tap is required to fully close the Layers list and return to the map canvas.

Expected results
A single back-arrow tap after clearing the search should return the user directly to the map canvas.

Screenshots or logs

https://github.com/user-attachments/assets/a30c993a-3137-4df7-9f9c-e7e06da93c0f

Conclusion
Created by Claude and supervised by a human test analyst.

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

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.

More from MerginMaps/mobile

All issues in MerginMaps/mobile

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.