-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validating MSISDN with vector.im does not work right now #19317
Comments
It doesn't work for users using that IS, it could work for users of different ISes, hardcoding |
@t3chguy is there a way to check what IS is being used? |
The URL yes, but we can't ask it if its using the OpenMarket API or not |
Can the check only be done when the phone number is submitted or when the settings panel is loaded? As far as we know, it only doesn't work with Sydent as far as we know right now. |
We know the URL of the IS at any point. |
This wouldn't cover the case of a user signed up to a homeserver which delegates its msisdn verification to an identity server (which afaik clients can't know about), however it looks like Element automatically configures new users with vector.im as their IS (@t3chguy feel free to correct me if I'm wrong), which means the number of users in this case would probably be fairly minimal. |
upstream issue matrix-org/sydent#411 |
@kittykat can you re-test this please |
I can add a phone number now. I don't get any useful error messages for invalid (wrong number of digits) or numbers which don't exist (e.g. +441234567890) and the error message for an invalid verification code isn't passed on correctly (matrix-org/synapse/issues/11016) I'm going to close this issue as it is now possible to add a phone number. |
Steps to reproduce
-> SMS message is not received but UI implies that it succeeded
Expected result
Verification SMS is received.
Critical because it fails silently and there is no workaround, and occasional because it fails for everyone but it doesn't feel like we have many users trying to use it.
Proposed solution
The text was updated successfully, but these errors were encountered: