[Short Guide / Tips] Autofill on Android

[Nail1684]

Short Guide / Tips – Autofill on Android

(Notice: All mentioned paths, screenshots etc. are based on the current BW Android app 2025.8.1 and stem from Android 15. The paths and optics etc. may change in the future, with updates, and may also be different for older Android versions.)

 

(Possible) Current Limitations, bugs and recommendations

(I try to update this list from time to time – but I neither can guarantee that it is “current” nor “comprehensive” at all times)

• New current bug (November 2025): Some browser are not recognized for autofill correctly at the moment – Chrome, Brave and Firefox are unaffected. Corresponding GitHub issue: [PM-27708] Autofill regression in multiple browsers: Bitwarden 2025.10.1 stops matching by website domain and falls back to package name (e.g. com.sec.android.app.sbrowser) · Issue #6107 · bitwarden/android · GitHub – and latest update from a BW developer:
  

  
  
  (direct link to that comment: [PM-27708] Autofill regression in multiple browsers: Bitwarden 2025.10.1 stops matching by website domain and falls back to package name (e.g. com.sec.android.app.sbrowser) · Issue #6107 · bitwarden/android · GitHub)

  • Update: It seems, with Android app version 2025.11.0 there comes a fix for this: a new Compatibility Mode for the affected browsers. – Here is a new Help Site entry for that Compatiblity Mode: [Edit: I removed the link now, as that Help Site section was removed now also – see the Update below]

    • Another Update:
      It seems, the new compatibility mode is only a temporary thing… Another “automatic” solution gets implemented and the compatibility mode will be removed with one of the next releases. (–> 🍒 PM-28545: Remove the compatibility mode toggle from the Autofill screen by SaintPatrck · Pull Request #6191 · bitwarden/android · GitHub)

• Especially if autofill sometimes works for you and sometimes it doesn’t work (for the same service): There is a current bug with Chrome/Brave/Chromium. – On Chrome 141 or Brave you can enable the following flag: #autofill-update-context-for-web-contents (chrome://flags, brave://flags). Eventually only browser updates will fix this bug.

• If you previously changed any browser autofill feature flags (chrome://flags, brave://flags…) – an older recommendation/necessity from 2023/2024 – you may need to reset them now to the default flag settings to prevent autofill from breaking with the new Chrome autofill framework.

• Passkeys and Bitwarden on Android: To use passkeys with Bitwarden on Android (i.e. with Bitwarden as your third-party passkey provider on your phone), you need at least Android 14 or above. And in some cases, even Android 14 doesn’t provide it. (see here: Android - passkeys.dev)

  • How to check that? → When you enter the Android Settings on your device and don’t see the menu entry “Passwords, passkeys & accounts” but only “Passwords & accounts”, then your device is not ready for using the Bitwarden mobile app as a third-party passkey provider.

  • Passkeys might not be working on Opera (–> Passkeys not working with latest Bitwarden and Android - #12 by andersaberg)

  • Firefox and Edge might not provide all passkey functionality (–> see the “Android” column here: Device Support - passkeys.dev)

  • Overall, due to the new browser (autofill) integrations, passkeys might work best on Brave and Chrome.

• Match detection on Android seems to be limited to “Base domain” and “Host” at the moment (meaning, “Starts with” and “Exact”… don’t work right now) → see this note: “Due to limitations in what the Android APIs can provide the autofill service, Android Password Manager clients cannot currently match URIs based on port or path.” from the Help Sites and this comment from a Bitwarden employee

• Card autofill is currently only available on Chrome/Chromium browsers (–> Autofill Cards & Identities | Bitwarden)

• Changing the font size on your Android device can currently cause autofill issues - changing the font size back and/or restart the device could help. (–> see this corresponding GitHub issue: [PM-26225] Autofill fails when system font is increased · Issue #5949 · bitwarden/android · GitHub)

 

1. General things

• on the fields you want to autofill: try it both on the username/email field and password field (the autofill suggestions might in some cases only appear when you are on a password field)

• Always install the Bitwarden mobile app (or rather any BW app) only from the official sources: https://bitwarden.com/download/#downloads-mobile

  • Using the Bitwarden browser extension on mobile browsers is not supported by Bitwarden.
    
    
    
    (–> https://bitwarden.com/help/product-faqs/#q-does-bitwarden-manage-in-browser-browser-extensions-on-android-mobile)

• usually, update to the latest app version (you can check the latest version here https://play.google.com/store/apps/details?id=com.x8bit.bitwarden or here Releases · bitwarden/android · GitHub)

• Using another (second) dedicated password manager on your device may interfere with Bitwarden’s autofill.

 

2. Make Bitwarden your “preferred service” on Android

You can set that up via Android → Settings:

If you press “change” – choose Bitwarden:

You can also achieve this by clicking on “Passkey management” in the BW mobile app (Settings → Autofill):

 

3. Set up autofill in the Bitwarden mobile app (Settings → Autofill)

 

3.1 Enable Autofill services

→ If you didn’t make Bitwarden your “preferred service” before, this toggle will also initiate that (again).

 

3.2 Choose how autofill suggestions should be displayed

• “Inline” requires Android 11+.

• “Inline” also requires the Android keyboard to be allowed to show inline suggestions, so check if this is activated in your chosen Android keyboard – because otherwise Bitwarden also isn’t allowed to show any inline autofill suggestions.

  • Ensure the suggestion strip is enabled in your keyboard settings menu. (e.g. for Gboard you can find it here: Android Settings → System → Keyboard → On-screen keyboard → Gboard → Text correction → Show suggestion strip)

  • If BW still doesn’t show inline suggestions, try switching keyboards, reinstall Gboard, or clear keyboard cache (Android Settings → Apps → Gboard → Storage & cache > Clear cache.)

• Additional tip: In some cases, autofill can also be evoked by a long press on a login form field, which may offer “Autofill” in a context menu:
  

  

 

3.3 For Chrome and Brave, use the new “autofill integration” (you can skip that if you don’t use Chrome or Brave)

→ Click the “Restart Chrome/Brave” button.

 

3.4 If you want to use Edge, Opera or Samsung Internet browser: enable “Use compatibility mode for browser autofill” (you can skip that if you don’t use any of these browsers)

More info on the new “compatibility mode for browser autofill” in the Help Sites: [Edit: I removed the link now, as that Help Site section was removed now also – see the Update below]

 

Update to the “compatibility mode”:
It seems, the new compatibility mode is only a temporary thing… Another “automatic” solution gets implemented and the compatibility mode will be removed with one of the next releases. (–> 🍒 PM-28545: Remove the compatibility mode toggle from the Autofill screen by SaintPatrck · Pull Request #6191 · bitwarden/android · GitHub)

 

3.5 If you want to use the Autofill Quick-Action Tile - or if needed otherwise - activate “Use accessibility”

(–> when you enable it: just follow the dialogue)

The Autofill Quick-Action Tile may be able to autofill when the other mechanisms can’t:

 

Usually, the above steps should be sufficient to “activate BW autofill” and it shouldn’t be necessary to deactivate the browsers in-built autofill/password managers separately (and the “autofill integrations” for Chrome and Brave deactivates the browser’s autofill). – But if you see, that autofill from the mobile browsers interferes, then try to deactivate it.

 

4. Make sure the URI you want to autofill on is stored in your corresponding login item

• a login item can have several URIs – and every URI can have an individual match detection setting, different from the default match detection (the latter can be set in Settings → Autofill → Additional options → Default URI match detection) – here two examples, where that might be relevant:

  • login forms are often on a domain, that is different from the main domain of a site – so, e.g. if you only have https://www.main-domain.com with match detection “Base domain”, autofill won’t work if the login form is on (example) https://login.second-domain.com → if that’s the case, then add https://login.second-domain.com as another URI to your corresponding login item

  • If you e.g. use “Host” as match detection (as default or for an individual URI) for https://www.main-domain.com, then autofill won’t work even on (example) https://login.main-domain.com → either add https://login.main-domain.com as another URI to your corresponding login item - or you could also change the match detection for https://www.main-domain.com to “Base domain” if you wanted to (as it then also covers https://login.main-domain.com for autofill)

  • (or other similar situations, where the URI that is needed for autofill is missing)

• see also here: Forming URIs for Autofill | Bitwarden

Just as an example of how it could look like in your login item (individual match detection settings for each URI not visible):

 

5. Autofill and Android apps

• For autofill in Android apps, the corresponding URI for that app is needed in your login item – the URI has the following form: androidapp://com... and here the info about how you can obtain the “package name” for an Android app: Forming URIs for Autofill | Bitwarden

• Another possibility to get the androidapp://com...-URI into your login item would be using “Fill and Save”:

  1. Without the URI in your login item, just try to autofill in the Android app.

  2. BW will open (just like everytime you use autofill), but it will show “no items” for autofill.

  3. You can now either create a new login item - or click on the search symbol on the top right corner and search for your corresponding login item.

  4. When you chose a login item via the search, a dialogue will open → chose “Fill and save”.

  5. By that, it will (auto)fill the credentials of that login items in the Android app and the androidapp://com...-package-URI for that Android app will be added to your login item, so that next time, autofill should work directly for that Android app.

 

6. Other useful guides / Official Bitwarden Help Sites:

• Autofill on Android: Autofill From Android App | Bitwarden

• Troubleshooting Autofill on Android: Troubleshoot Android Autofill | Bitwarden

• Passkeys on Android: Autofill Passkeys | Bitwarden

  • • General info about Passkeys and Bitwarden on Android: To use passkeys with Bitwarden on Android (i.e. with Bitwarden as your third-party passkey provider on your phone), you need at least Android 14 or above. And in some cases, even Android 14 doesn’t provide it. (see here: Android - passkeys.dev)

• Card Autofill on Android: Autofill Cards & Identities | Bitwarden

 

7. If it still doesn’t work:

• You may need to disable/reenable autofill settings in the BW app and in the Android system autofill setting

• you may try to reinstall the BW app

  • alternatively to a reinstall, it could also be enough to just wipe the data of the BW app (Android Settings → Apps → Bitwarden (password manager) → Storage & cache → Clear storage)

  • regardless of whether you reinstall or wipe data: make sure, you can login again, i.e. you have your master password and either have your 2FA at hand or can access your emails for the email verification code if “New Device Login Protection” is active

• restart your mobile browser

• if it still doesn’t work, you should also try to restart your device in between

 

8. When everything is set up correctly and it still doesn’t work on a specific site:

• Use this form to report autofill issues with a specific site: Report mobile autofill failure

 

9. Further troubleshooting:

• Please temporarily enable flight recorder, attempt autofill actions, and share with the Bitwarden support team:

 

[bit]

Thank you for this excellent guide. It’s much more useful than the “official” documentation provided!

Even following this guide, long-pressing on an input field in an app seems to still be required for popup mode to work. To make matters worse, the Autofill option is in a hidden overflow menu. So the correct procedure is currently:

1. Long press on the input field (username/password/etc.)
2. In the popup that appears, click the button to show the hidden overflow menu
3. From the overflow menu that now appears, select Autofill
4. Select the information to autofill (with the term “autofill” clearly being hyperbole here!)
5. Repeat this process for every field, as needed

It’s not obvious at all, so I wrote it all out to hopefully help others.

[Nail1684]

@bit Thanks for your feedback!

And do you have an innocuous and “popular” site to reproduce your addition about that long-press-procedure? Also which browser do you use?

[mauricio]

Passkeys not working fine on Android, I have to disable and re enable Bitwarden to work

[Nail1684]

@mauricio

Passkeys not working fine on Android

This seems to be also dependent on the mobile browser you use – see the comments in the first section of my post: [Short Guide / Tips] Autofill on Android (TL;DR: Chrome and Brave might work best with passkeys, also due to the new autofill integration)

@mauricio

I have to disable and re enable Bitwarden to work

Did you try to enable the following flag (on Chrome 141+ or Brave): #autofill-update-context-for-web-contents (chrome://flags, brave://flags)? – It’s a current browser bug, which only browser updates will fix eventually.