bitwarden v2.2.6 support vivaldi Android

bigbighill

prking

@bigbighill Well that's a surprise, it does work in Vivaldi on Android!

S_Paternotte

On my Nokia 3.1 Android 9 (Pie) Vivaldi does not work with Bitwarden. DuckDuckGo browser does work with BW.
Could you elaborate on your experiences?

how does autofill work for you?
which of the autofill services have you enabled in your Android settings?

prking

@S_Paternotte It depends how you've setup Autofill in Bitwarden settings, it can work in one of three ways. I've got it set so that if I tap on a username or password it offers to fill it. (After I put in my master password or fingerprint)

troypulk · SolydX 13, 6.6.15 / Debian 6.6.15-2 / Xfce 4.18.1 (64-bit)

@prking

Thanks for suggesting auto-fill settings.

I'm using Enpass and it was not working in snapshot for android until now.

In Enpass's auto-fill settings there is an option to use the enpass keyboard so after checking that box Vivaldi snapshot now shows options to fill password/auto-fill fields.

I think it's a work around for Enpass because Vivaldi snapshot will not work otherwise where other browsers don't need the keyboard function enabled to work.

Edit: also I needed to enable Accessibility in auto fill.

S_Paternotte

@prking I'm interested to hear which settings you used to get things working.

the Bitwarden Auto-fill service doesn't do it for Vivaldi on my phone. For DuckDuckGo this does work.
the Bitwarden Accessibility service sort of half works. When Vivaldi opens a webpage containing login fields, Bitwarden generates a Notification. But when I open this, I have to perform a manual search to find the relevant credentials. If next I select the option Autofill and Save, then my vault item is given an extra URI androidapp:vivaldi... Do this a couple of times more for other websites and each time you open a login page you are presented with a long list of possible credentials to choose from. To me this is not how it is supposed to be working.
Bitwarden does not offer a Keyboard service

So, tell us more about your settings and how it works for you.

prking

@S_Paternotte I have Autofill and Accessibility Service on. URI match is set to Base Domain. Accessibility service is set to auto-scan.

I haven't tested Enpass.

S_Paternotte

@prking Peculiar. I've got the same settings on my phone.
The BW Autofill service is doing nothing with/receiving nothing from Vivaldi.
I find the BW Accessibility service (a fallback solution for older phones) 'unworkable'.

If I may ask, what happens if you disable the BW Accessibility service?

bigbighill

only support vivaldi android beta
not support vivaldi android snapshot

S_Paternotte

@bigbighill Being a Translator I'm on the Vivaldi Android Sopranos pre-release version
Your little message triggered me to install Vivaldi Android Bèta alongside.

Vivaldi Android Bèta works with Bitwarden as it should (confirmed)
Vivaldi Android Sopranos does not work with Bitwarden. This version passes on the url 'com.vivaldi.browser.sopranos'

Hmm, could THIS be the issue?

S_Paternotte

@S_Paternotte Yeah found it!
Bitwarden's browser support is looking for another browser ID-string to catch and filter out
See https://github.com/bitwarden/mobile/commit/f657edf195d4770c610cf2cd03b88a5f00d5d033

I guess Vivaldi Android Sopranos cannot identify itself as com.vivaldi.browser (as well).
So, this means that if I want BW to cooperate with Vivaldi, I need to switch to the regular Vivaldi Bèta and I'm in business.

S_Paternotte

Further details on this.
Bitwarden offers two methods for fetching browser URL's and entry fields for lookup in its database and provide autofill.

Autofill service
This is the standard Android Autofill service (since Android 8?)
Accessibility service
This is a fall back method meant to work on older Android versions

With both enabled, Vivaldi Android Bèta manages to trigger Bitwarden resulting in a notification. Tapping the notification opens Bitwarden and I can select the correct entry for autofill.
With just the (standard) Autofill service enabled, Bitwarden remains ignorant of any messages from Vivaldi Android Bèta.

So, the standard Android Autofill Service is NOT working with Vivaldi Bèta or Vivaldi Sopranos.
What's working with Vivaldi Bèta only is the fall back method for older Android versions.

S_Paternotte

Further info
Note that there now exist three different versions of Vivaldi Android: Beta, Snapshot and Soprano's. The latter being pre-snapshot build for translators and Vivaldi team members.

Each of these three versions has its own android app ID.
Now, Bitwarden provides support for Vivaldi, at least from its own code. But this is ONLY for the regular Vivaldi Beta App ID: com.vivaldi.browser.

Bitwarden has no knowledge of or co-op with the Snapshot or Soprano's releases of Vivaldi with respective id's com.vivaldi.browser.snapshot and com.vivaldi.browser.sopranos.

So, even when the team enhances its support for password managers in Vivaldi, one will only be able to experience this in the regular Vivaldi Beta release, not in the snapshot or Soprano's releases, simply because Bitwarden is not prepared for these other app ID's.

Now, do we need to ask Bitwarden (and other password managers) to also add support for com.vivaldi.browser.snapshot and com.vivaldi.browser.sopranos, or is there a solution to this on Vivaldi side?

mmazur

Now, do we need to ask Bitwarden (and other password managers) to also add support for com.vivaldi.browser.snapshot and com.vivaldi.browser.sopranos, or is there a solution to this on Vivaldi side?

Vivaldi could pretty much fix the problem if they update the app to fully support Oreo+ autofill service.

https://developer.android.com/guide/topics/text/autofill-optimize#java

MannixMD

This post is deleted!

S_Paternotte

For the record, I've filed a request at Bitwarden to also listen to com.vivaldi.browser.snapshot and com.vivaldi.browser.sopranos (pending)

Looking further at Bitwarden@Github I discovered this long discussion thread that mentions more autofill issues with several browsers and even suggest that there may be an issue inside Chrome Android.

S_Paternotte

I was pointed to Myki Password Manager, which is free for personal use on iOS, Android, Linux, MacOS, Windows.

It uses Android's Accessibility Service and works just fine with Vivaldi.

Myki is always available in the top drawer, next to the time. Open a login page in Vivaldi. Draw down the Myki icon. Click it, enter your pin and select the applicable login credentials for autofill.

I might switch to this password manager

Edit: Myki also supports the Android 8 Autofill Service, but this does not work with Vivaldi.

Tealing

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.