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

Offen
  • Stimmt etwas nicht?
#3,442 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
android, java
Bereich
mobile

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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)

Vorherrschende Sprache
Java
Sterne
1.1k
Forks
177
Ø Merge
12 Std. 24 Min.
Gemergte PRs (30 T.)
26

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nextcloud/notes-android

Alle Issues in nextcloud/notes-android

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.