nextcloud / nextcloud/notes-android
Bug: Data loss on new instance sync
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 168
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 31
Description
Please use GitHub reactions 👍 to show that you are affected by the same issue. Please don't comment if you have no relevant information to add!
Describe the bug
I have set up a new nc instance and logged in via the same username and domain as the old instance, thats why i only had to give access again on the android app, to the same account as before and the sync started, but the notes were partly deleted, on the nextcloud server were only 14 out of around 80 and after that all the remaining notes also dissapeared on the client
To Reproduce
Steps to reproduce the behavior:
- have a nc instance with notes on the client and on the server
- delete that instance and setup a new one with the same account name and domain as before but no notes
- go to the notes android app and click on add account
- accept the popup
- wait for the sunc to finish
- see your notes dissapearing
Expected behavior
the android app should sync the notes to the server properly without partly deleting notes
Smartphone (please complete the following information):
- Nextcloud Notes-Version (android app): 4.1.0
- F-Droid or Play Store: used both
- Android-Version: 12, Miui 13.0.16
- Device: Xiaomi Redmi Note 10 pro
Server
- Nextcloud version:
- Nextcloud Notes version (server app):
Stacktrace
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, entry points, server versions, or stack trace are provided. Start by reproducing the documented new-instance sync sequence with the listed Android and app versions, then trace the sync path; done means existing client notes remain intact and are synchronized without deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100