Bitwarden doesn't work.
-
Hi,
Vivaldi on Android is looking great, I'm excited to see my favorite browser finally available. I hear lastpass sort of works but cannot see the proper URL to match with your vault. However Bitwarden (another password manager similar to lastpass except its opensource) doesn't work with Android Vivaldi at all. Long pressing on a login field does not result in a auto fill option at all only a paste option. I have both the auto fill service and the accessibility service enabled it works fine with chrome and firefox just not Vivaldi. Right now you have to go into the bitwarden app and manually copy and paste usernames and passwords
I wasn't sure if there was a better place to post about this. Would be great to see this fixed.Keep up the great work and thanks for finally bringing Vivaldi to android!
-
@Sarth69 I tried it a couple of hours ago with the Vivaldi login. I first logged in to my Bitwarden app and then I got a notification to autofill when I visited the login dialog on the Vivaldi site. Worked out fine.
-
I logged into bitwarden and then opened vivaldi and I only get "Copy to Note" or "Paste" as options.
-
@Sarth69 You have to visit the actual login site for this to work. Moreover the Bitwarden entry for Vivaldi Forum has to include the URI for the login.
-
@luetage Can you clarify what you mean by you have to visit the actual login site?
I am going to login.vivaldi.net for example and long pressing the username field and I just get "Copy to Note" and "Paste" as the options that pop up. If I do the exact same thing in chrome or firefox I get the prompt to autofill.
I've tried several other websites as well such as gmail and youtube and they all give the same options "Copy to Note" and "Paste" I never get a prompt for autofill.
-
@Sarth69 You don't have to long tap anything. Just select the password field and the android notification will appear on top (shield icon), which you only have to tap to autofill username and password. Here a screenshot, but be aware that the shield icon was hidden when I took the screenshot, for whatever reason.
pic
-
@luetage Oh, thanks it works now! Strange. On all the other browsers I've just long pressed the form and hit auto fill. After sliding my notifications down and tapping the bitwarden notification it worked! Except now I have a different problem. It thinks every website is the same password haha it just sees com.vivaldi.browser as the URL for everything.
-
@Sarth69 Oh lol, should probably be brought to the attention of bitwarden devs. Vivaldi has little reach and is only out for half a day, can't expect miracles.
-
I posted on the bitwarden forums and someone replied that Google Chrome seems to be having this issue as well. So it doesn't seem to be a Vivaldi or Bitwarden issue, it would seem it is a chrome issue but I could be wrong, I saw the lastpass one made it to the bug tracker so maybe if that gets fixed it might fix bitwarden as well?
-
Support for Vivaldi had to be added to Bitwarden and it should be available in the next release. Github issue
-
@R3gi The issue linked is closed. But it "generated" a new issue, closed too, but this new issue indicates that it's a problem on Vivaldi's side.
-
The issue has been resolved in Bitwarden beta, which works fine with Vivaldi 1.0 and Vivaldi snapshot through the old fashioned Android Accessibility service. The more recent android autofill service continues to suffer from some sort of bug in Android system or Chrome.
You can either join the Bitwarden beta programme or keep a sharp eye on the next Bitwarden release. -
@Gwen-Dragon that's correct. If one joins the Bitwarden app beta programme then you'll get the beta version that works fine using the Accessibility service.
-
@Gwen-Dragon that's downright tedious, isn't it, that they have to manually add id's for each supported browser and its variants?
I get the impression it's a requirement from android
-
@Gwen-Dragon from what I understand it is required to have some xml file listing all supported browsers in order to get the Autofill mechanism working. Doesn't make for a flexible open integration between browsers and password managers, does it?
But maybe I'm wrong here. Not my expertise. -
FYI: Enabling the Bitwarden Auto-fill Accessibility Service affects the phone "secure startup" (device encryption) negatively! Check this year old reddit post: https://www.reddit.com/r/Bitwarden/comments/c3u371/is_there_a_reason_to_use_bitwardens_accessibility/?sort=old
On my Android 9 phone, the "Use Bitwarden?" prompt says:
If you turn on Bitwarden, your device won't use your screen lock to enhance data encryption.
So in order to use Bitwarden with Vivaldi on Android, you need to turn on the Bitwarden Accessibility Service and then you lose device security. It's bonkers like one of the commenters on the reddit topic wrote.
Somebody wrote on Bitwarden GitHub that on Android 10 the "native" Auto-fill Service works, I don't know exactly on which browser he meant, Chrome or Vivaldi.
-
No real need to post twice. Let's continue with this thread.
Frankly, I've given up on Android's Autofill.
Mine is a Nokia 3.1 with Android 9.
I use Vivaldi Snapshot, Edge and DuckDuckGo as browsers.
I use Bitwarden (beta channel) and KeePassDX as password managers.
For each password manager there is the option to enable the Autofill service or to enable the Accessibility service. The Autofill service can be assigned to one single app only.Whenever there's a new release of above apps I run a series of experiments with combinations of these browsers, password managers and services.
The accessibility service makes things work, sort of. But that's not how it's supposed to be, eh?
The Autofill service I have yet to see in action for both Bitwarden and KeePassDX and I read in many places that this happens with other password manager as well.At Github I watch the makers of Bitwarden and KeePassDX struggling to make things work with different browsers and I believe the Vivaldi Team is also trying to make it work for a third password manager. Why would all these parties have to spend so much effort in trying to make things work between all these apps, each combination requiring different tweakings?
I'm not a programmer (anymore), but I have a strong suspicion that this Android Autofill API may not be functional at all.Hence me giving up and quietly waiting for a miracle to happen. (Well not so quiet now, aren't I?)
Maybe I should switch to iOS like my son keeps reminding me: "Dad, that's Android for you. Switch to iOS. Everything just works." -
@S_Paternotte Autofill isn’t a reason to ditch Android. Doesn’t work for me either, but I don’t see it as a deal breaker. At least I don’t think iOS is the answer.
-
I have a strong suspicion that this Android Autofill API may not be functional at all.
From what I've heard, the struggle that password managers and browsers are having is because of Chromium. Have you tested a non-Chromium based browser with your password managers?
-
The work efficiency of the Vivaldi dev team is too low. A bug that annoys users is so frustrating that it hasn't been solved for such a long time.
enpass
