Android: Note stuck in synchronization loop after editing until note is deleted from server
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
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 內容生成。
描述
This issue respects the following points:
- I have read the FAQ
- I have searched for existing issues
- The issue affects the Notes Android app, neither the Notes server app nor the Nextcloud Android app.
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:
- Open Notes from the web interface or desktop.
- Delete the problematic note.
- The Android app starts synchronizing normally again.
- 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 分鐘
- 30 天內合併 PR
- 26
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
nextcloud/notes-android 的其他 Issue
-
0. Needs triage bug
難度 2/5 1-3 小時 新手友好度 72/100
nextcloud/notes-android#3439 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 65/100
nextcloud/notes-android#3367 ·
維護者通常 1 天內回覆
-
0. Needs triage bug
難度 2/5 1-3 小時 新手友好度 74/100
nextcloud/notes-android#3353 · 2 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
-
0. Needs triage bug
難度 4/5 3-5 天 新手友好度 48/100
nextcloud/notes-android#3436 · 1 個 reaction ·
維護者通常 1 天內回覆
-
0. Needs triage bug
難度 4/5 3-5 天 新手友好度 43/100
nextcloud/notes-android#3431 · 1 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
查看 nextcloud/notes-android 的全部 Issue
相似的 Issue
-
brain bug mod
難度 2/5 1-3 小時 新手友好度 75/100
PetitPotam/kindred-spirit#230 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 62/100
humblemuzzu/dumbtv#207 ·
維護者通常 2 天內回覆
-
0. Needs triage bug
難度 2/5 1-3 小時 新手友好度 64/100
維護者通常 1 天內回覆
-
document volunteer wanted
難度 2/5 1-3 小時 新手友好度 82/100
apache/shardingsphere-elasticjob#2569 · 1 則留言 ·
-
bug
難度 2/5 1-3 小時 新手友好度 65/100
維護者通常 1 天內回覆