nextcloud / nextcloud/richdocuments
User multiplies like a rabbit when the connection of the mobile client is lost
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Describe the bug
I was working on a spreadsheet using the Nextcloud Android client on ChromeOS -- usually a better combination than using the web UI. The link was not that stable and I had to reconnect a few times. Now I have multiple mes editing at once and can't get rid of them:

To Reproduce
Steps to reproduce the behavior:
- Edit in the mobile client
- Crash the client
- Goto 1.
- Edit in the Web app.
Expected behavior
I don't exactly know but I would expect that one of me is enough.
Screenshots
See above
Client details:
- OS: Android Client 3.22.3
- Version 25
- Device: Lenovo ThinkPad C13 Yoga
Server details
Operating system: Debian 11.5
Web server: nginx
**Database:**mariadb
**PHP version:**8.1
**Nextcloud version:**25
Version of the richdocuments app 7.0.1
Version of Collabora Online 22.5.702
Logs
Nextcloud log (data/nextcloud.log)
I have no access to the logs.
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
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
Start by reproducing the listed mobile-client crash and reconnect sequence, then compare the resulting editors in the web app using the reported Nextcloud 25, richdocuments 7.0.1, and Collabora Online 22.5.702 versions. The issue is done when reconnecting after a client failure no longer leaves multiple editors for the same document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100