nextcloud / nextcloud/talk-desktop
Notify Push not consistently triggering Talk notifications (icon appears randomly)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 525
- Forks
- 85
- Avg merge
- 8h 5m
- Merged PRs (30d)
- 35
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Enable and configure notify_push with Redis and proper proxy.
- Confirm setup with php occ notify_push:setup https:///push shows all
- Open the Talk desktop or web client and wait for a new message.
Expected behaviour
Talk notifications should arrive instantly and reliably, and the message indicator (black dot or red count) should always appear when a new message is received.
Actual behaviour
Sometimes the black dot indicating a new message appears.
Other times, no indicator shows up, even though a new message is received.
Other times, no indicator is shown and the user is not alerted at all, even though a new message has arrived.
System-level notifications do arrive instantly, indicating that notify_push is working correctly — the issue seems to be with how the Talk app handles or displays the incoming notifications.
Diagnosis and logs
Diagnosis report
php occ notify_push:setup https://xxxxxxxxxxxxxxxxx/push ✓ redis is configured ✓ push server is receiving redis messages ✓ push server can load mount info from database ✓ push server can connect to the Nextcloud server ✓ push server is a trusted proxy ✓ push server is running the same version as the app configuration saved Insert a diagnosis report here.It can be found in the About window (open from the menu or via F1 and click on "Copy report" button).
Client logs
Press:
- 🪟 Windows: Ctrl+Shift+I
- 🍎 macOS: Cmd+Option+C
- 🐧Linux: Ctrl+Shift+I
Or use the context menu to open the developer tools, then go to the Console tab.
Insert error logs here.
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 issue with notify_push configured through the documented php occ notify_push:setup command, then inspect the Talk desktop client's developer-console logs while receiving messages. Compare cases where the black dot, red count, or no alert appears with the system-level notification. Done means Talk notifications and message indicators appear reliably for incoming messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100