nextcloud / nextcloud/notes-android

synchronization error / different content rich mode <-> text mode.

Open
#3,120 3 comments 5 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

When loading the app most of the times an error message appears (see below).

Sometimes also the error appears that rich editing mode could not be loaded.

Also I found I have different content in text mode and rich mode on my shopping list, so now some things I am thinking my bag ;)

Thank you for the App!

Expected behavior

No synchronization error.

Notes Android version

33.0.0

Notes server version

4.13.1

Nextcloud Android version

33.0.1

Nextcloud version

32.0.5

Device

Google Pixel 5

Android Version

13

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

App Version: 33.0.0
App Version Code: 330000090
App Flavor: fdroid

Files App Version Code: 30290290 (PROD)


OS Version: 4.19.269-gdb4810fe97f0(eng.root.20260312.135224)
OS API Level: 33
Device: redfin
Manufacturer: Google
Model (and Product): Pixel 5 (redfin)


java.lang.Exception: {"errorType":"OCP\Lock\ManuallyLockedException"}
[com.nextcloud.android.sso.InputStreamBinder.processRequestV2(InputStreamBinder.java:440), com.nextcloud.android.sso.InputStreamBinder.performNextcloudRequestAndBodyStreamV2(InputStreamBinder.java:113), com.nextcloud.android.sso.InputStreamBinder.performNextcloudRequestV2(InputStreamBinder.java:96), com.nextcloud.android.sso.aidl.IInputStreamService$Stub.onTransact(IInputStreamService.java:110), android.os.Binder.execTransactInternal(Binder.java:1280), android.os.Binder.execTransact(Binder.java:1244)]
at it.niedermann.owncloud.notes.persistence.NotesServerSyncTask.pushLocalChanges(NotesServerSyncTask.java:150)
at it.niedermann.owncloud.notes.persistence.NotesServerSyncTask.run(NotesServerSyncTask.java:99)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:463)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)

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 with NotesServerSyncTask.java, especially run() at line 99 and pushLocalChanges() at line 150, then reproduce the synchronization error and compare the shopping list in rich and text modes. Done means synchronization completes without the reported lock error and both modes show the same content.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.