nextcloud / notes-android

✎ Android client for Nextcloud Notes app.
https://play.google.com/store/apps/details?id=it.niedermann.owncloud.notes
GNU General Public License v3.0
933 stars 134 forks source link

Android notes app does not sync notes with server #2393

Open ratermir opened 2 weeks ago

ratermir commented 2 weeks ago

This issue respects the following points:

Describe the bug

  1. change existing note or add new note then save it (exit note by the arrow at the left top corner) or refresh list of notes
  2. after approx. 5 sec I get the error message "Syncronization failed" (my language is Czec, this is my translation of the message so it can be inaccurate)
  3. note is not saved on the server

Expected behavior

Note is saved on the server

Notes Android version

4.3.1

Notes server version

4.11.0

Nextcloud Android version

3.29.2

Nextcloud version

29.0

Device

Honor 9X

Android Version

10

App Store

Stacktrace

App Version: 4.3.1
App Version Code: 40030192
App Flavor: play

Files App Version Code: 30290290 (PROD)

---

OS Version: 4.14.116(10.0.0.224C432)
OS API Level: 29
Device: HWJSN-H
Manufacturer: HUAWEI
Model (and Product): JSN-L21 (JSN-L21)

---

java.lang.Exception: {"errorType":"RuntimeException"}

    at it.niedermann.owncloud.notes.persistence.NotesServerSyncTask.pushLocalChanges(NotesServerSyncTask.java:164)
    at it.niedermann.owncloud.notes.persistence.NotesServerSyncTask.run(NotesServerSyncTask.java:100)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:929)
ratermir commented 2 weeks ago

I removed account in the Notes app and added it again; notes were downloaded from the server (probably - because they apeared in the notes list as they are on the server; but they could be cached - i can't decide it), but then behaviour was as described in the bug.