Optimization for Auto-fill on Android Mobile Screens

[Nail1684]

@mting1117

① 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.

According to this comment by a Bitwarden developer, ports are an Android limitation. (see the comment for more details)

@mting1117

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.

Okay, two things:

1. 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)

2. I don’t think the mobile app can “blacklist” specific browsers - but you could already

   1. deactivate autofill in the mobile app (Settings → Autofill),

   2. 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

   3. 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)