Switching Note - Failed to push (empty) steps
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 738
- Forks
- 162
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 35
Description
Steps to reproduce
- Open a note
- Change to another note
- See 403 error in JS console
Expected behaviour
Switching between notes should not generate an error.
Actual behaviour
Switching between notes triggers an 403 pushing step error.
Requests/Logs
Excerpt from the log console:
[ERROR] text: Failed to push the steps to the server ...
[ERROR] text: failed to write to document - not allowed Object { app: "text", uid: "xxx", level: 3 }
[ERROR] text: Unexpected Error "Failed to apply steps. Retry!" Object { app: "text", uid: "xxx", level: 3, error: Error }
Actual request body that fails:
XHRPOST
https://cloud.xxx.xxx/index.php/apps/text/session/542243/push
[HTTP/2 403 106ms]
awareness "xxx"
baseVersionEtag "6800baba35a17"
documentId 542243
filePath ""
sessionId 3620
sessionToken "xxx"
steps []
token null
version 71331
I notice that filePath and steps are empty.
Die documentId in body and URL also equals the current open note before switching to new note.
Server
- Notes app version:
4.12.0 - Nextcloud version:
31.0.2 - OS:
Linux xxx 6.13.8-arch1-1 nextcloud/notes#1 SMP PREEMPT_DYNAMIC Sun, 23 Mar 2025 17:17:30 +0000 x86_64 GNU/Linux - Web server (from outside to nextcloud):
- 1st:
nginx/1.27.4(latest docker image) as reverse proxy - 2nd: Docker
apache2/now 2.4.62-1~deb12u2 amd64of nextcloud container
- 1st:
- PHP version:
PHP 8.3.19 (cli) - Database:
11.7.2-MariaDB-ubu2404-log
Nextcloud configuration:
Client
Please complete the following information.
- Browser (incl. version): Firefox 137.0 (64bit)
- OS:
Linux xxx 6.14.2-arch1-1 nextcloud/notes#1 SMP PREEMPT_DYNAMIC Thu, 10 Apr 2025 18:43:59 +0000 x86_64 GNU/Linux
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 tracing the note-switching flow around the /apps/text/session/{documentId}/push request and compare the session, documentId, filePath, and steps values before and after switching notes. Reproduce the sequence from the issue and verify that switching no longer sends an empty push for the previous document or produces a 403 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100