Display name is case sensitivity, registration fails

[akallabeth]

Linked issues:
element-hq/element-ios#5664

When building out this screen in FTUE we should ensure that the keyboard defaults to lower case letters, and has field level error message for real-time updates.

---

Steps to reproduce

I´ve helped a friend register a new account which failed with a strange error.

1. Where are you starting? What can you see?
   Registration of new user. Phone autocorrect did capitalize the first letter

2. What do you click?
   Register new user

After correcting the capital first letter the registration succeeded.

Outcome

What did you expect?

Registration complete

What happened instead?

Strange looking error code

Your phone model

Samsung, not sure which exact model

Operating system version

No response

Application version and app store

Latest from play store as of last saturday (28.01.2022)

Homeserver

matrix.org

Will you send logs?

No

[bmarty]

I quickly tested the user story with Element 1.3.17:

• create an account on matrix.org using displayname Benoit010101. Note that on my phone, there is no capitalization of first letter for this field, and this is the expected behavior.
• the account @benoit010101:matrix.org is created. Note that the B has become b

So I have not reproduced the issue.

Can you provide more details or a screenshot about the strange error you have seen?

[akallabeth]

@bmarty sorry, no. As mentioned, did help a friend who could not register and was astonished about this too.
will not be able to get that particular phone in my hands for quite some time and don´t have any phone with google tools installed myself.

[daniellekirkwood]

We saw users run into this issue on UserTesting.com too. I will provide more info.

[daniellekirkwood]

Reproduced on UserTesting video Doctor1Who at 3:48

[daniellekirkwood]

Investigating this issue with the team yesterday and found that the issue is with the username, not display name and also that in the case of SSO there's unlikely anything that we can do.

Due to those things I'm going to close this issue and we'll track the keyboard info as a part of the deliverable for this issue here which is actively being worked on.