nextcloud / nextcloud/text

Android app text editor doesn't write changes to server filesystem

Open
#5,102 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: direct editor
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Describe the bug
Changes from the text editor in the Nextcloud Android app don't get synced on the server filesystem. But they show up in the editor on other devices.

Changing a file from the webbrowser makes it sync to the server filesystem.
Update 2024-02-14: See https://github.com/nextcloud/text/issues/5102#issuecomment-1944185020
In short: It's about timing between step 2 and 3. And it's also reproducible in a webbrowser.

Bug is probably a regression between Nextcloud > 25.0 and 26.0.9. Didn't recognized it in Nextcloud <= 25. See also: #4100

 

To Reproduce
Steps to reproduce the behavior:

  1. Create a md or txt file. (should have 0 bytes)
  2. Open the file in the Android app and add some text.
  3. Close the file in the Android app.
  4. File will still have 0 bytes. (visible via the files view in the Android app or a webbrowser, or directly on the server filesystem)
  5. Open the file on another device or in the webbrowser and you'll see the text added via the Android app.

 

Expected behavior
When closing the editor changes should be written to the server filesystem.

 

Server details:
Tested with two different servers.

  • server 1
    • Nextcloud version: 26.0.9
    • PHP Version: 8.2 (Debian-12)
    • Database: MariaDB 10.11.4 (Debian-12)
  • server 2
    • Nextcloud version: 27.1.1.0
    • PHP Version: unknown
    • Database: unkonwn

 

Client details:
Tested with two different Android devices.

  • Device: Fairphone 3+
    • Nextcloud app: 3.26.0
    • OS: /e/OS-12.3-s (LineageOS-19 based Android-12)
  • Device: Nokia 1 (TA-1060)
    • Nextcloud app: 3.26.0
    • OS: Android-10

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 reproducing the edit and close sequence with the listed Nextcloud and Android app versions, then read the linked update and comment about timing between steps 2 and 3. Trace the editor-to-server synchronization path; done means edits made in the Android app are written to the server filesystem when the file is closed.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, javascript
Domain
backend, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.