nextcloud / nextcloud/notes-ios

Error Message for Failed Sync Covers Notes Area

Open
#172 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Swift
Stars
73
Forks
22
PR merge metrics
No merged PRs in 30d

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Context: I was in a basement today playing board games and taking notes on my phone for points, and had very little signal. An error message popped up that the changes I was making could not be synced to the server (which is expected behavior), but the bug was that:

  1. The error message covered the part of the editor where I was taking notes, and
  2. When I swiped the error message up to dismiss it, it would keep coming back, and cover the editor again.
Steps to reproduce
  1. Have server be unreachable or have spotty internet.
  2. Make changes to a note.
  3. Have error message appear.
Actual Behavior

The error message covers a substantial amount of the editor. And since the error keeps reoccurring because of a spotty connection in the basement, the error message keeps coming back and covering the editor again.

Image
Suggested Behavior

Just a suggestion to improve the usability, but you could have a sync status icon in the top bar that shows whether the changes were synced successfully (and maybe even only show it if there was an error), and show the details when the icon is tapped, eg show the popup that is already shown now, but only if the error icon is tapped, so that the errors don't interfere with taking notes.

Image

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

No file or test is named. Start by reproducing the sync failure in the iOS note editor with an unreachable server, then trace where the error message is presented. Done means repeated sync failures no longer obscure note-taking, while error details remain accessible.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.