MerginMaps / MerginMaps/mobile

Interactive warning notification timeout too short

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

Nobody has claimed this yet.

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

Description

When a synchronization error occurs the app shows a brief notification (5 sec) with the full text: "There was an issue during synchronisation, we will try again. Click to learn more". but the notification disappears too quickly for users. The result is that users cannot access the detailed error.

In case of an interactive notification - the user is expected to take some action, the notification should not disappear automatically after 5 seconds.

Application (+ app version, build, operating system)
Mobile devices / OS - windows, IOS, Android

Steps to reproduce

  1. Open the app and select project.
  2. Trigger a synchronization that will fail (e.g., force network error, edit conflict, or use a project with a known server error).
  3. Observe the sync error notification that appears in the app UI.
  4. Try to tap the "Click to learn more" (or read the full message) before the notification times out.

Actual results

The sync error notification displays briefly (5 sec) and times out automatically.
The user does not have enough time to read the full error text or tap "Click to learn more".
The detailed information is not accessible from the UI once the notification disappears, preventing users from understanding the cause or taking corrective action.

Expected results

The sync error notification should remain visible

  1. until the user clicks on it or closes it manually (e.g., via an "x" button)
  2. a longer time (e.g., 10-15 sec)

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 synchronization error notification in the mobile app UI and the code that sets its five-second timeout. Reproduce a failed synchronization on a supported device or simulator, then verify that the interactive notification remains available until dismissed or for the agreed longer duration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.