Deck error in logs - Notification was not parsed by any notifier [app: deck, subject: card_user_assign]
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Using Deck - receiving this error
{"reqId":"REMOVED","level":1,"time":"2025-12-15T17:50:02+00:00","remoteAddr":"REMOVED","user":"REMOVED","app":"no app in context","method":"GET","url":"/ocs/v2.php/apps/notifications/api/v2/notifications?format=json","message":"Notification was not parsed by any notifier [app: deck, subject: card_user_assign]","userAgent":"Mozilla/5.0 (Windows) mirall/3.13.23.12-Win64 (build 20240708) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)","version":"32.0.2.2","clientReqId":"REMOVED,"data":[],"id":"REMOVED"}
[Nextcloud Hub 25 Autumn] (32.0.2)
Nextcloud AIO
Deck
Version 1.16.2, AGPL-licensed
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 notification request at /ocs/v2.php/apps/notifications/api/v2/notifications?format=json and trace the Deck handling for the card_user_assign subject. Done means that this notification is parsed by a notifier and the "Notification was not parsed by any notifier" log no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100