nextcloud / nextcloud/flow_notifications
Has this app ever worked properly?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 8
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
Description
Hello,
Over the past few years, I’ve run tests on various test suites with this app, and they’ve never been successful (or maybe they were a long time ago).
Test performed (for example): a notification is triggered when a PDF file is renamed. The setup is very simple, but I have never received a single notification (and I am certain that the instance's notification system works fine in other contexts).
Also, for years now, I’ve seen people use a workaround for this glitch by sending notifications via Talk (a message sent in a conversation, which triggers a notification).
So I’m wondering: have I simply never understood how your app works, or has it been buggy for a long time (and therefore never been fixed)?
Thank you in advance for your clarification on this matter.
I can provide more details, but in my opinion, the problem is easily reproducible in many configurations.
Thanks
P.S.: My most recent tests were conducted with version 5.0.0 (Nextcloud 34), and they failed in exactly the same way as all my previous attempts with earlier versions.
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 PDF rename notification scenario described for Nextcloud 34 and compare it with notification delivery through Talk. The issue does not name a file, test, or entry point; done would require identifying why the Flow notification is not delivered and confirming the behavior across the relevant configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100