OK, so, weird thing. I tried to use Bitwarden autocomplete to insert a password into an app and it prompted me “Bitwarden is locked”. Ok. I tap, Bitwarden opens, I use the thumbprint and I am greeted by a spinning circle. Apparently an endless one.
Fine. I kill the app, start Bitwarden, fingerprint, loading. After like 5 seconds, the thing loads, UI is very different now. I don’t know why, not the biggest fan, old one was more readable, this looks thin, fonts are smallest available. What is to be gained by smaller text in an app where reading precision matters? Oh well. Strong dislike of the fact it loads it on demand, I thought, since it looks HTML-y. But at least it’s loaded now. I assumed it’s cached now, I tapped around, seems responsive. Must be a first run thing.
Days pass, I am in the middle of a transaction, try to call BW autocomplete, it loads, thumb, spin of death. Nothing is shown but a dark blue bg and a spinning circle. I had to kill the app, which, by the way, if done while invoked by an app, means that you have to kill the calling app. It doesn’t show separately.
Kill the app, transaction failed, swearing going on. Launch BW separately, loads without issues (the spinny thing is there but takes like a second).
So. Is it the UI being loaded? Is the vault not loading? Is it a bug when being called as completion?
Whatever it is, it started with the new UI (for me). It seems (so far) to be manifesting when called by completion and vault is locked. Pre-unlocking it seems to work. I had internet both cases, but at least one was under wifi/fiberoptics. It’s not that.
Android, Samsung S22U.
P.S. I can’t ***** believe the UI got redone and credit card number is still not grouped. Same sausage-string of numbers, but smaller.