As far as I understand, this is related to a very inefficient implementation with Web Sockets (probably why you don't see an additional request). They're trying to get rid of that as soon as possible is my understanding, so things should get better.
What helped in my case: Picking another username. It's possible that somehow it handles existing username errors weirdly which leads to the infinite spinner.
What helped in my case: Picking another username. It's possible that somehow it handles existing username errors weirdly which leads to the infinite spinner.