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

Aberta
  • Algo errado?
#3,442 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
22/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
android, java
Domínio
mobile

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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)

Linguagem predominante
Java
Estrelas
1.1k
Forks
177
Merge médio
12h 24min
PRs com merge (30d)
26

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nextcloud/notes-android

Todas as issues de nextcloud/notes-android

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.