Login redirect loop bug

[hingobway]

Logged in users are occasionally caught in a redirect loop due to some kind of state issue surrounding whether they are logged in or not. For some users this may lead to being shown the login page at unusual times, or it may fully crash the tab in extreme cases.

• is this a next.js bug?
• does this have to do with the invalid cookie deletion policy? was there even a good reason for doing this?
• should we disable auto redirects for already logged in users anyway? go to a static page that makes the user click through? (could even make it a non-reactive link to break state)
• is this actually more common on mobile, or does this (most likely i think) have to do with failed auth requests and therefore shoddy internet connections?

---

user report:

I am not sure why but on the phone it at times returned me to the login screen and asked me to enter email and get a link (or the passkey). My guess is that I was already logged in but I am wondering if it might make sense to add an "already logged in option" to that screen or something. With that said I can't replicate it but it did happen twice.

---

• possibly solved by Fix loginboundary error #141 ??