Infinite Loading Loop

prometheus-22 commented

2025-12-15 00:41:28 -06:00

(Migrated from github.com)

When logging in to multiple accounts using a password (no passkeys in use) I get stuck on loading with the register passkey prompt in the background. It seems like VoidAuth is possibly waiting for interaction with this prompt before proceeding. No amount of waiting will get past this loading loop, nor can I interact with the register passkey prompt. If I refresh the page at this point it will log in normally. I am seeing this behavior on two separate VoidAuth instances across three different browsers. I am also getting this register passkey prompt on accounts where a passkey has already been registered.

It is somehow related to the Bitwarden browser extension because when I disable this extension the register passkey prompt is able to be interacted with and login flows normally. It also continues to work after re-enabling the Bitwarden extension following a successful login with it disabled, but the flow breaks again if I clear all my browser data with Bitwarden still enabled.

When logging in to multiple accounts using a password (no passkeys in use) I get stuck on loading with the register passkey prompt in the background. It seems like VoidAuth is possibly waiting for interaction with this prompt before proceeding. No amount of waiting will get past this loading loop, nor can I interact with the register passkey prompt. If I refresh the page at this point it will log in normally. I am seeing this behavior on two separate VoidAuth instances across three different browsers. I am also getting this register passkey prompt on accounts where a passkey has already been registered. It is somehow related to the Bitwarden browser extension because when I disable this extension the register passkey prompt is able to be interacted with and login flows normally. It also continues to work after re-enabling the Bitwarden extension following a successful login with it disabled, but the flow breaks again if I clear all my browser data with Bitwarden still enabled. <img width="473" height="408" alt="Image" src="https://github.com/user-attachments/assets/c3f68981-b3de-4a1e-a558-d324ad55df9a" />

notquitenothing commented

2025-12-15 07:24:28 -06:00

(Migrated from github.com)

Thanks for opening an issue! Let me see if I can reproduce the issue, I also have the BitWarden browser extension installed but I already have a passkey so that may be why it is not asking to create one

prometheus-22 commented

2025-12-15 12:16:15 -06:00

(Migrated from github.com)

Appreciate you looking into it. For some reason I have this issue even with accounts that have a passkey associated already, so I'm not sure why I'm even getting the prompt when I login to those accounts with a password.

notquitenothing commented

2025-12-16 07:43:58 -06:00

(Migrated from github.com)

The app will ask a user to register a passkey if the login is on a new device/browser (it keeps track with localStorage) but it should not get stuck behind a loading spinner.

When you get the chance, can you test a potential fix for this issue? You can do this by backing up your existing database, then changing your VoidAuth image tag to :edge from :latest and see if the problem is gone.

The app will ask a user to register a passkey if the login is on a new device/browser (it keeps track with localStorage) but it should not get stuck behind a loading spinner. When you get the chance, can you test a potential fix for this issue? You can do this by backing up your existing database, then changing your VoidAuth image tag to `:edge` from `:latest` and see if the problem is gone.

prometheus-22 commented

2025-12-16 17:52:13 -06:00

(Migrated from github.com)

Thanks for the explanation about using localStorage. Makes perfect sense, I'm just used to most services not asking to register a new passkey when one is already registered to the account. I'm admittedly not an expert when it comes to passkeys, so I'm curious what the theory is behind using localStorage to track that?

This change on edge is definitely better. After a moment with the spinner, it disappears and allows me to interact with the passkey prompt as I'd expect. I'm able to login normally now.

Thanks for the explanation about using localStorage. Makes perfect sense, I'm just used to most services not asking to register a new passkey when one is already registered to the account. I'm admittedly not an expert when it comes to passkeys, so I'm curious what the theory is behind using localStorage to track that? This change on edge is definitely better. After a moment with the spinner, it disappears and allows me to interact with the passkey prompt as I'd expect. I'm able to login normally now.

notquitenothing commented

2025-12-16 18:47:46 -06:00

(Migrated from github.com)

Nice! Glad the patch fixes the main issue, I will include it in the next release.

My original thinking is that passkeys are usually tied to device/platform, and if you had access to your passkey from device #2, you would have used it to sign in. But I will think some more about implementation and how to prevent annoying popups, like if you were using a privacy focused browser that didn't store localStorage between sessions it would ask you every time.

Nice! Glad the patch fixes the main issue, I will include it in the next release. My original thinking is that passkeys are usually tied to device/platform, and if you had access to your passkey from device #2, you would have used it to sign in. But I will think some more about implementation and how to prevent annoying popups, like if you were using a privacy focused browser that didn't store localStorage between sessions it would ask you every time.

prometheus-22 commented

2025-12-16 20:26:51 -06:00

(Migrated from github.com)

Gotcha. I use bitwarden to store my passkeys so I'm not tied to one device, but you're right that if I was using passkeys most of the time I'd just use it to sign in and that wouldn't even be an issue. Good point on the privacy focused browser as well, as that's probably the reason I keep getting annoyed by Amazon to set up a passkey even though I've done that.

I've been using a passkey-only auth solution for most of my services until now, but it's a little cumbersome with some of the things I'm doing. I find myself using bypass codes way too often. I've been evaluating VoidAuth to replace that because it handles my workflow better. This and #198 were pretty much the only things holding me back. Really appreciate you jumping on this so quickly!

Gotcha. I use bitwarden to store my passkeys so I'm not tied to one device, but you're right that if I was using passkeys most of the time I'd just use it to sign in and that wouldn't even be an issue. Good point on the privacy focused browser as well, as that's probably the reason I keep getting annoyed by Amazon to set up a passkey even though I've done that. I've been using a passkey-only auth solution for most of my services until now, but it's a little cumbersome with some of the things I'm doing. I find myself using bypass codes way too often. I've been evaluating VoidAuth to replace that because it handles my workflow better. This and #198 were pretty much the only things holding me back. Really appreciate you jumping on this so quickly!

❤️ 1

notquitenothing commented

2025-12-16 20:58:58 -06:00

(Migrated from github.com)

No problem! Thanks for opening an issue 😊 feedback is great, and I really do rely on people finding things that need fixing