Hello, after update to [Nextcloud Hub 10]((31.0.1) Talk app is not working on ios device please help.
I assume you enabled E2EE?
Where I can check it? Was working fine before the update to hub 10
Can you check the talk admin settings? There should be a section about E2EE.
Also it’s really hard to help since you omitted the template, do you have a HPB setup?
Mobile clients do not support end-to-end encrypted calls at the moment.
Yes I have HPB active
Exactly, that’s the point. So E2EE is disabled, correct?
Can you try turning E2EE on and the back off and see if it works then?
I have check that option but when I refresh the page is uncheck again. Possible to activate from the terminal ?
Can you please first run
occ config:app:get spreed call_end_to_end_encryption
and post the output here?
After that try to reset it with
occ config:app:set --value=0 spreed call_end_to_end_encryption
1 Like
Now is working, thank you so much for your help! 
Cool! Could you still let me know what the output of the first command was please? 
1)the output of the first command was 1
2)second comand result → Config value ‘call_end_to_end_encryption’ for app ‘spreed’ is now set to ‘0’, stored as mixed in fast cache
2 Likes
Thank you for confirming!
Btw, I am able to reproduce the issue on latest main and created E2EE toggle in admin settings not working · Issue #14672 · nextcloud/spreed · GitHub
2 Likes
Thank you so much! I see the latest talk version is Version 21.0.1 but on the appstore is still Version 21.0.0.
The latest talk-ios is still 21.0.0 Releases · nextcloud/talk-ios · GitHub, only the server part of talk is on 21.0.1 and that is released correctly: Talk - Apps - App Store - Nextcloud. The development cycles for minor versions are independent of each other, so 21.0.0 Talk iOS works fine with 21.0.1 Talk Server.
Okay, thank you for your help! I love nextcloud. I have my own home server I use to talk with my wife and store all the pictures with our children.
2 Likes
Hi again, after I have been fixed this error, last night was apper again. Solved with the same command on the terminal …
Hmm… Without you changing anything? That sounds very weird. When it happens again, can you check the output again? Was it again set to 1?
Yes, without change anything… and yes the output was 1 again
To be honest, I have no idea, how this can happen. I don’t see any code-path leading to this…
@ochiverzi A colleague suggested to check the access logs for a call to /apps/provisioning_api/api/v1/config/apps/spreed/call_end_to_end_encryption. Could you check if there was a request?
Thank you for this! Very much appreciated!