Android: Note stuck in synchronization loop after editing until note is deleted from server
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 22/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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)
- Lingua principale
- Java
- Stelle
- 1.1k
- Fork
- 177
- Merge medio
- 12h 24m
- PR unite (30g)
- 26
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nextcloud/notes-android
-
0. Needs triage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
nextcloud/notes-android#3439 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
nextcloud/notes-android#3367 ·
I maintainer di solito rispondono entro 1 giorno
-
0. Needs triage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
nextcloud/notes-android#3353 · 2 commenti · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
0. Needs triage bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
nextcloud/notes-android#3436 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
0. Needs triage bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 43/100
nextcloud/notes-android#3431 · 1 commento · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di nextcloud/notes-android
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Backblaze/b2-sdk-java#248 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
IETF-Hackathon/pqc-certificates#351 ·
I maintainer di solito rispondono entro 2 giorni