Call audio and popup notification have 30 seconds delay

[stratoss]

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

1. Using Nextcloud Hub 10 (31.0.4) with Talk 21.0.4, desktop client v1.1.8 with Built-in Talk version v21.0.4, Release channel: stable
2. User A (using web browser) calls user B (using the desktop version)

Expected behaviour

Having visual and audio notification in the desktop client, also the tray icon color to change somehow

Actual behaviour

User B immediately see that there is an incoming call, button to join is there, but NO notification (visual and audible).
After ~ 30 seconds both visual and audio notifications arrives.

Diagnosis and logs

Diagnosis report

Diagnosis report

Nextcloud Talk Desktop
Version	v1.1.8
Built-in Talk version	v21.0.4
Release channel	stable
Operating system	Linux 5.10.0-20-amd64 (#1 SMP Debian 5.10.158-2 (2022-12-13))
Executable Path	/home/stratoss/Downloads/talk/Nextcloud Talk-linux-x64/talk
Using Wayland	❌ no
Connected to	-
Nextcloud server version	31.0.4
Nextcloud Talk version	21.0.4
notifications app enabled	✅ yes
notify_push app enabled	❌ no

Application config

{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": true,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

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.

Using locale "en_US" for language "en"
JitsiStreamBackgroundEffect.worker.js?v=52bb1692bf4c36d249c9:1 [WASM] Loading model of size: 249792
JitsiStreamBackgroundEffect.worker.js?v=52bb1692bf4c36d249c9:1 INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
printChar @ JitsiStreamBackgroundEffect.worker.js?v=52bb1692bf4c36d249c9:1
6133.js?v=0a8b511b240d8201dd7a:1 Not connected to signaling server yet, defer joining room hibe9tbd
JitsiStreamBackgroundEffect.worker.js?v=52bb1692bf4c36d249c9:1 [WASM] Loading model of size: 249792
JitsiStreamBackgroundEffect.worker.js?v=52bb1692bf4c36d249c9:1 INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
printChar @ JitsiStreamBackgroundEffect.worker.js?v=52bb1692bf4c36d249c9:1
6133.js?v=0a8b511b240d8201dd7a:1 Session has been marked as inactive
6133.js?v=0a8b511b240d8201dd7a:1 Session has been marked as active
6133.js?v=0a8b511b240d8201dd7a:1 Session has been marked as inactive
6133.js?v=0a8b511b240d8201dd7a:1 Session has been marked as active
6133.js?v=0a8b511b240d8201dd7a:1 Session has been marked as inactive
6133.js?v=0a8b511b240d8201dd7a:1 Session has been marked as active```

</details>

[Antreesy]

notify_push app enabled => ❌ no

App is responsible for immediate notifications, without it client is falling back to 30 seconds interval

Also if chat is open for user B, and session is considered active there, this shouldn't trigger a notification at all

[stratoss]

Hi @Antreesy. The app is actually enabled, but it's not recognized by the client:

root@nextcloud:/home/stanimir# sudo -u www-data php /var/www/nextcloud/occ app:enable notify_push
notify_push 1.1.0 enabled
root@nextcloud:/home/stanimir# ps aux | grep notify_push
www-data  309606  0.0  0.0  25948 11996 ?        Ssl  05:20   0:00 /nextcloud/apps/notify_push/bin/x86_64/notify_push     /nextcloud/config/config.php
root      315241  0.0  0.0   6336  2292 pts/2    S+   09:22   0:00 grep notify_push
root@nextcloud:/home/stanimir# sudo -u www-data php /var/www/nextcloud/occ app:list | grep notify_push
  - notify_push: 1.1.0
root@nextcloud:/home/stanimir# grep push_server /var/www/nextcloud/config/config.php
  'push_server' => 'https://.../push/',


root@nextcloud:/home/stanimir# sudo -u www-data php /nextcloud/occ notify_push:setup
This setup wizard is intended for use on single server instances
where the nextcloud server, web server/reverse proxy and push daemon all run on the same machine.
If your setup is more complex or involves any kind of load balancing
you should follow the manual setup instruction on the README instead
https://github.com/nextcloud/notify_push
Press enter to continue or ESC to cancel...

Push binary seems to be running already
✓ push server seems to be functioning correctly.
Reverse proxy seems to be configured already
✓ reverse proxy seems to be setup correctly.
  configuration saved
root@nextcloud:/home/stanimir# 

This is the apache config under the VirtualHost block:

ProxyPass /push/ws ws://127.0.0.1:7867/ws
ProxyPass /push/ http://127.0.0.1:7867/
ProxyPassReverse /push/ http://127.0.0.1:7867/

[stratoss]

@Antreesy It does report it now as enabled in the client as well, but the behavior is even worse. The 'incoming call' state is updated after ~ 15 seconds instead of instantly, also even after 30 seconds no audio/notification is being shown in the desktop client.

Diagnosis report

Nextcloud Talk Desktop
Version	v1.1.9
Built-in Talk version	v21.0.4
Release channel	stable
Operating system	Linux 6.12.12-amd64 (#1 SMP PREEMPT_DYNAMIC Debian 6.12.12-1 (2025-02-02))
Executable Path	/home/stratoss/Downloads/talk/Nextcloud Talk-linux-x64/Nextcloud Talk
Using Wayland	❌ no
Connected to	-
Nextcloud server version	31.0.4
Nextcloud Talk version	21.0.4
notifications app enabled	✅ yes
notify_push app enabled	✅ yes

Application config

{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": true,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

[nickvergessen]

In your first report the app was not recognized. It could be that wrong information is still cached somewhere, and the cache is ignored when generating the report.
@ShGKme is clearing the "app data" cache the way to go? We should add a button to refresh capabilities 🙈

[ShGKme]

@stratoss Could you check that the problem is (not) resolved after logout and login?