Android: Note stuck in synchronization loop after editing until note is deleted from server
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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)
- Lenguaje dominante
- Java
- Estrellas
- 1.1k
- Forks
- 177
- Merge medio
- 12 h 24 min
- PR fusionados (30 d)
- 26
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nextcloud/notes-android
-
App crashes when I connect powerAbierto0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nextcloud/notes-android#3439 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
nextcloud/notes-android#3367 ·
Los mantenedores suelen responder en 1 día
-
0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
nextcloud/notes-android#3353 · 2 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
0. Needs triage bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
nextcloud/notes-android#3436 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
0. Needs triage bug
Dificultad 4/5 3-5 días Aptitud para principiantes 43/100
nextcloud/notes-android#3431 · 1 comentario · 2 reacciones ·
Los mantenedores suelen responder en 1 día
Todos los issues de nextcloud/notes-android
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Backblaze/b2-sdk-java#248 ·
Los mantenedores suelen responder en 3 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
IETF-Hackathon/pqc-certificates#351 ·
Los mantenedores suelen responder en 2 días