You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logs are after running a Force Reload. Issue still occurs.
(I don't think the logs help in this case)
index.js:2 Using locale "" for language "en"
JitsiStreamBackgroundEffect.worker.js?v=fa1b69e42302a02d7a71:1 [WASM] Loading model of size: 249792
JitsiStreamBackgroundEffect.worker.js?v=fa1b69e42302a02d7a71:1 INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
printChar @ JitsiStreamBackgroundEffect.worker.js?v=fa1b69e42302a02d7a71:1
nextcloud.domain.example/ocs/v2.php/apps/user_status/api/v1/statuses/_sim2kid:1
Failed to load resource: the server responded with a status of 404 ()
nextcloud.domain.example/ocs/v2.php/apps/user_status/api/v1/statuses/_sim2kid:1
Failed to load resource: the server responded with a status of 404 ()
index.js:2 Not connected to signaling server yet, defer joining room kgbswmoy
index.js:1 Session has been marked as inactive
The text was updated successfully, but these errors were encountered:
Avatar image has this in response headers, so it's cached for 1 day and won't be updated until it expires (which is a common practice for most of image previews / assets in Nextcloud):
Cache-Control: private, max-age=86400, immutable
If you disable cache, it should be promptly updated after force reload.
We'll take a look how it is invalidated in web and see, if that would be possible to implement in the Desktop client.
How to use GitHub
Steps to reproduce
Expected behaviour
The profile should update on the talk client if it changes.
Actual behaviour
The profile picture remains the same for extended periods of time. This includes past app reboots and force reloads.
Diagnosis and logs
Diagnosis report
Diagnosis report
notifications
app enablednotify_push
app enabledApplication config
Client logs
Logs are after running a Force Reload. Issue still occurs.
(I don't think the logs help in this case)
The text was updated successfully, but these errors were encountered: