Android: Note stuck in synchronization loop after editing until note is deleted from server

オープン
  • 何か問題がありますか？
#3,442 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
android, java
領域
mobile

調査の方向性

The failure is raised from pushLocalChanges in NotesServerSyncTask.java (around line 150), which run() calls at line 99; the logged exception comes from the SSO InputStreamBinder. Start by reading how pushLocalChanges picks and retries an edited note, and why a failed push is never marked as done. Done means a note that fails to push stops looping and either syncs or surfaces a conflict, confirmed by a sync test. The reporter has no reproduction steps, so reproducing the loop first is the main hurdle.

索引モデルが issue の本文から書いたものです。

説明

0. Needs triage bug
This issue respects the following points:
Describe the bug

Environment:

  • Nextcloud Notes Android app
  • Nextcloud server:35.0.3
  • Android: 12
  • Notes app version: 35.0.0

Issue:

Sometimes after editing a note on the Android app, the note fails to synchronize correctly.

The application then appears to enter an endless synchronization loop. The note remains unsynchronized and the issue persists even after:

  • forcing synchronization
  • restarting the application
  • rebooting the phone

The only workaround I found is:

  1. Open Notes from the web interface or desktop.
  2. Delete the problematic note.
  3. The Android app starts synchronizing normally again.
  4. The deleted note unexpectedly reappears on the server, apparently pushed back from the mobile application.

Expected behavior:

  • The note should synchronize normally after editing.
  • A synchronization conflict should be detected and handled gracefully if necessary.
  • The application should not enter an endless sync loop.

Actual behavior:

  • One note becomes stuck.
  • Synchronization keeps failing repeatedly.
  • Restarting the device does not solve the issue.
  • Deleting the note on the server temporarily restores synchronization.
  • The deleted note is recreated from the mobile client during the next synchronization.

Additional information:

I am attaching the error log generated by the mobile application.

Expected behavior
Notes Android version

35.0.0

Notes server version

6.1.0

Nextcloud Android version

35.0.2

Nextcloud version

35.0.3

Device

redmi note 10

Android Version

12

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

App Version: 35.0.0
App Version Code: 350000090
App Flavor: play

Files App Version Code: 350000290 (PROD)

OS Version: 4.14.186-perf-g0d9078479a02(V13.0.3.0.SKSEUXM)
OS API Level: 31
Device: camellian
Manufacturer: Xiaomi
Model (and Product): M2103K19G (camellian_eea)

java.lang.Exception: {"errorType":"Exception"}
[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:112), android.os.Binder.execTransactInternal(Binder.java:1179), android.os.Binder.execTransact(Binder.java:1143)]
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:520)
at java.util.concurrent.FutureTask.run(FutureTask.java:328)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1100)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:1571)

主要言語
Java
スター
1.1k
フォーク
177
平均マージ
12時間 24分
マージ済み PR（30日）
26

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextcloud/notes-android のほかの issue

nextcloud/notes-android の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。