First of all, the Bitwarden app cannot fully recognize the exact URLs within the browser, so I opted to use the Bitwarden extension in the browser. Coincidentally, my mobile browser supports installing the Bitwarden browser extension. However, when using both the app and the extension simultaneously, the two auto-fill features conflict with each other in the UI. I attempted to block this by adding URLs in the format of androidapp://package-name, but this action doesn’t work for the browser. I hope this option can be optimized.
@mting1117 Welcome to the forum!
Do you mean the match detection setting “exact” doesn’t work on the Android app? Do you have an example where it doesn’t work?
Yeah, that is possible – but not supported by Bitwarden. (and to clarify: the BW browser extensions obviously are supported – but not for use on mobile browsers)
(–> Password Manager FAQs | Bitwarden)
Yeah, this can lead to conflicts, as Bitwarden stated in the quote above. And that’s why I closed this feature request now.
Well, URIs (and their individual match detection setting if set) takes effect for all BW apps that are logged in to the same account. So in your case, those settings should be active in the mobile app and browser extensions at the same time – and I’m not sure, if that could help at all…
As written above, you seem to be requesting something, Bitwarden doesn’t even support (1. using the browser extension on mobile browsers and 2. using both the mobile app and browser extensions on mobile) and and already made clear it could lead to conflicts and non-working-functions. (again, see the screenshot above)
Thank you for your response. Regarding your reply, I need to provide some clarification, but my English is not very good, and I’m using translation software, so there might be some inaccuracies in the translation.
① The issue with “exact match not working” only applies to URLs within the browser. In my scenario, my Docker containers all share the same IP but have different ports. For example, https://192.168.31.101:8082 will only be recognized as https://192.168.31.101 in the Bitwarden app under exact match mode.
② The Android mobile browser I’m using is Rain Browser（雨见浏览器）: https://play.google.com/store/apps/details?id=com.yjllq.internet. It has excellent support for extensions, almost indistinguishable from using them on a desktop browser.
④ Both the browser extension and the app take effect simultaneously. The conflict I mentioned is only at the UI level—for example, overlapping pop-ups appearing under the input box.
In summary, as I mentioned earlier, due to the first point, the Bitwarden app cannot achieve perfect injection on browser-based websites. I still believe that browser websites should use the Bitwarden extension, as browsers provide additional support for extensions. Bitwarden is better suited for assisting with app logins and similar tasks. Using both together is the ultimate solution, which is why I hope the Bitwarden app can support an app blacklist feature to exclude browser access.
According to this comment by a Bitwarden developer, ports are an Android limitation. (see the comment for more details)
Okay, two things:
-
Before making a request for optimization of something that is not even supported, I would recommend to request for support of the “thing” first
: Support for browser extensions on mobile browsers (Android) -
I don’t think the mobile app can “blacklist” specific browsers - but you could already
-
deactivate autofill in the mobile app (Settings → Autofill),
-
with the new Autofill integration settings for Chrome and Brave turned off, you maybe could deactivate autofill by the mobile app in Chrome and Brave (see here for more info about those new settings) and
-
you already can block autofill for specific URIs/URLs in the mobile app (Settings → Autofill → Block autofill (it’s in the “additional options”, at the bottom of the list))
-
If none of those suggestions helps, you can still open a new feature request specific for such a “blacklist feature to exclude browser access” for the mobile app. (but as always, search for possible existing feature requests first)
As the title suggests, the autofill feature on the Android mobile end targets URLs within the browser for identification. However, due to Android’s limitations, it cannot recognize ports. Therefore, I prefer using Bitwarden’s browser extension within the browser. Consequently, a browser blacklist feature is needed to prevent the simultaneous activation of Bitwarden’s Android mobile app and browser extension, which would otherwise result in duplicate and overlapping identification pop-ups.
The title is actually confusing to me … the term “browser blacklist” seems to suggest either that your browser is prohibited from opening certain URLs, or that your Android is prohibited from running certain browsers.
I think that what you are actually requesting is for the Bitwarden mobile app to be disabled (at least as an autofill option) while you are using a web browser on your phone. Is this accurate?
Also, in case you were note aware, you should know that the use of in-browser browser extensions on Android is not officially supported.
Finally, if you have not read the following announcement, it may be a good idea to do so:
I found the root cause of my problem, because the browser I was using was adapted to the default populator of the calling system, which caused both the app and the plugin to take effect on a web page at the same time
OK, I’m glad that you’ve solved your problem. Unless you object, I will move the above discussion/comments into your other thread, and close this feature request.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.