Unhelpful 400 error when adding MSISDN and server doesn’t delegate

[jryans]

If you try to add a MSISDN to your account in Settings, but the HS is not configured to delegate MSISDN handling, Riot does not handle the error very well and presents a 400 error.

[jryans]

This is ideally resolved by a better error code in the spec and / or some way the client to know if HS supports adding MSISDNs.

[rxl881]

In my opinion it would be good to disable or hide the input in settings if MSISDN registration / MSISDN delegation is disabled (e.g. for all Modular servers, currently).

[jryans]

Right, I think we all agree. The challenge is that at the moment the HS doesn't signal to the client whether it supports adding MSISDNs, so we may need some spec work to add that signal.

[kittykat]

Could this be caused by matrix-org/sydent/issues/410?

[babolivier]

Could this be caused by matrix-org/sydent/issues/410?

Ah no, this looks like a different issue: in this case the homeserver isn't configured to delegate MSISDN requests to an identity server (therefore doesn't support adding a phone number), whereas in matrix-org/sydent#410 the homeserver is configured to do so but Sydent (or the OM API) silently fail to send the text message.

[babolivier]

Looks like Synapse is the naughty one here, since it seems to be hiding errors from Sydent to clients: matrix-org/synapse#11016