MerginMaps / MerginMaps/mobile
Interactive warning notification timeout too short
Nobody has claimed this yet.
- 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
- Open the app and select project.
- Trigger a synchronization that will fail (e.g., force network error, edit conflict, or use a project with a known server error).
- Observe the sync error notification that appears in the app UI.
- 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
- until the user clicks on it or closes it manually (e.g., via an "x" button)
- a longer time (e.g., 10-15 sec)
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 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