nextcloud / nextcloud/notes-android

Rich editor timeout notification remains after the editor successfully loads

Open
#3,245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
Java
Stars
1.1k
Forks
168
Avg merge
1d 17h
Merged PRs (30d)
31

Description

This issue respects the following points:
Describe the bug
Describe the bug

When opening a note in rich editing mode over a slow connection, Notes shows a message saying that loading takes longer than expected and offers switching to plain editing.

If I wait, the rich editor eventually loads successfully, but the warning remains visible for the entire editing session.

Steps to reproduce
  1. Use a slow or unstable mobile connection.
  2. Open a note in rich editing mode.
  3. Wait until the loading warning appears.
  4. Continue waiting without switching to plain editing.
  5. The rich editor loads, but the warning is not dismissed.
Expected behavior

The warning should be dismissed automatically when the rich editor reports that loading has completed.

Environment
  • Nextcloud Server: 34.0.0
  • Notes server app: 6.0.1
  • Text app: 8.0.0
  • Android: 16
  • Device: Xiaomi 15T

Related: #1798, #1843

Expected behavior

No response

Notes Android version

34.0.0

Notes server version

6.0.1

Nextcloud Android version

34.0.1

Nextcloud version

34.0.0

Device

Xiaomi 15T

Android Version

16

App Store
  • Google Play Store
  • F-Droid
  • Huawei App Gallery
Stacktrace

No response

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 tracing the rich editor loading flow and the timeout warning shown during slow connections. Reproduce the issue with a delayed load, then verify that the warning disappears when the rich editor reports successful completion and remains available if the user switches to plain editing.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.