"Limit starting a call" cannot be saved - POST responds with Error 400

[Eric-Benesch]

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. Fresh nextcloud installation v32 -> upgrade to v33
2. Install Talk App
3. Change "Limit starting a call" to anything

Expected behaviour

Setting should be saved

Actual behaviour

AJAX POST responds with error 400 - setting is not saved
(All other settings can be saved without problems)

Talk app

Talk app version: 23.0.1

Custom Signaling server configured: no

Custom TURN server configured: no

Custom STUN server configured: no

Browser

Microphone available: yes

Camera available: yes

Operating system: Mac

Browser name: Firefox

Browser version: 148

Browser log

Details

``` Insert your browser log here, this could for example include: a) The javascript console log b) The network log c) ... ```

Server configuration

Operating system: Ubuntu

Web server: Apache

Database: Maria

PHP version: 8.4

Nextcloud Version: 33.0.0

List of activated apps:

Details

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder

Nextcloud configuration:

Details

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

Server log (data/nextcloud.log)

Details

Insert your server log here

[Eric-Benesch]

@Antreesy Thank you for your attention! But I dont think the issue will be resolved by the pull request you have linked.

I will clarify:

The issue I am reffering to does NOT happen in nextcloud v32 talk v22.0.9 - the setting can be saved fine there

When I set start_calls in oc_appconfig directly within the db the setting is working fine

The problem I am reffering to is only, the setting cannot be saved using the settings page - and only in nextcloud v33 talk v23.0.1

[Antreesy]

When I set start_calls in oc_appconfig directly within the db the setting is working fine

Does it store as an int or as a string? I suspect some OCP API was changed in the meantime between the version, and we simply miss that. Endpoint now expects a string value to be passed, and I can also reproduce it in NC 33+. So still should be this fix.

[Eric-Benesch]

In the db it is stored as int.

spreed|start_calls|3|2|0

I am new to nextcloud, just wanted to setup a quick talk server. Didnt have time to look into the API - but yes, I guess the bug sits there - or in the frontend sending the wrong data.