Using an outdated login link shows no clear error message

[PapeThePope]

Describe the bug
When using an outdated login link "Logging in" is showing with a loading spinner:

After some seconds an error message pops up, that the login has failed, with no clear message stating why:

In the network tab we can see, that it tried to authenticate against the api for 4 times before giving a response:

To Reproduce
Steps to reproduce the behavior:

1. Create a login link
2. Wait for it to expire
3. Try to use the login link

Expected behavior
I expect to get a faster reaction for this case. The Token is clearly invalid and shouldnt become valid even after 4 tries.
A better error message would be good aswell, for example that the token is invalid. It kinda feels like a connection problem at the moment.

Desktop:

• OS: MacOS
• Browser Zen
• Version 31.12

[github-actions]

Hi @PapeThePope, thanks for opening this issue. It hasn't been approved by a maintainer yet — we'll get back to you shortly to either milestone it (approval) or close it.

— Automated. See CONTRIBUTING.md.

[PapeThePope]

Can you assign me to this one? Would like to try to fix it myself 👍