mirror of
https://github.com/bitwarden/android.git
synced 2026-03-09 03:33:36 -05:00
AutoFill Missing in Chrome and Chrome Beta #2267
Open
opened 2025-11-26 23:13:44 -06:00 by GiteaMirror
·
46 comments
No Branch/Tag Specified
main
crowdin-pull
PM-33266-crashlytics-bug
PM-32123/cookie-sync-error-message
PM-29861-update-overflow-content-description
PM-33227/clear-cookies-debug-button
update-agp
PM-26059-remove-cipher-key-encryption-flag
remove-remember-viewmodel
PM-29871-external-links
PM-29673/flight-recorder-export-header-info
renovate/lock-file-maintenance
sdlc/sdk-update
release/2026.3-rc48
PM-24380/flight-recorder-redact-hostname
release/2026.2-rc47
PM-32714/fallback-to-web-vault-host
pr-6572
PM-28834/setting-app-layout-horizonos
PM-26896-autofill-fix
vvolkgang/process-release-notes-v2
PM-26577-app-links-support
release/2026.2-rc46
release/2026.1-rc45
PM-30644/added-logs-for-debug
PM-30644/quicktile-nav-not-showing-migration
minor-gradle-updates
release/2026.1-rc42
release/2026.1-rc44
release/2026.1-rc43
PM-28834/set-landscape-on-horizonos-devices
context-rules
devclarity/update-code-review-command
PM-20026/force-ltr-passwords-and-codes
release/2025.12-rc41
cmcg/testCoverage
claude-skill/creating-feature-flags
PM-29014/talkback-support-for-passwords
release/2025.12-rc40
BRE-1305/publish_test
accept-user-certs
autofill-permissions
release/2025.11-rc39
PM-22479/check-all-certificates-validate-asset-links
release/2025.10-rc38
agalles/android-latest
optimize-test-workflows
tier2-test-sharding
retro-agent
PM-27001/skip-account-selection-only-one-exists-cxp
release/2025.10-rc37
agalles/test-1118
release/2025.10-rc36
PM-20593-token-refresh
QA-1126b/adding-native-sanity-test
release/2025.9-rc35
pm-25933/sdk-update-password
release/2025.9-rc34
release/2025.8-rc33
agalles/20250821-release
debug-release-issues
pm-24249-allow-automated-prs-for-sdk-updates
release/2025.8-rc32
release/WORKFLOW-TEST-2025.8-rc28
agalles/20250807release
release/2025.07-rc25
release/hotfix-v2025.7.0-bwa
pm-23311/export-vault-policy-bypass
release/2025.07-rc24
authenticator-pm-sync-flags-issue
ps/implement-sdk-repository-example
release/hotfix-v2025.6.0-bwpm
release/2025.06-rc21
agalles/automate-android-fastlane-patch
release/2025.05-rc20
release/2025.04-rc19
languages/basque
release/2025.03-rc19
update-readme
qrcode/feature
innovation/archive/pm-19153-archive-items
qrcode/2-ui-fields
qrcode/1-page
hold-on-biometric-prompt-alternative
release-notes-process
release/2025.02-rc16
bwa-monorepo
PM-8223/new-device-verification-ux-improvements
pm-18451/exempt-from-policies
test-bwa
cs-workaround-linked-0-copy
release/2025.01-rc15
release/2025.01-rc14
release/2024.12-rc13
pm-16670/sync-leave-notice
821
PM-16695/backport-lean-more-new-device-verification
km/15084-testing
release/hotfix-v2024.11.7
release/2024.11-rc1
pm-11304/collection-add-item-button
PM-14241/disabling-logs-app-crash
poc/offline-editing
new-version-calc
pm-11649/expired-link-services
pm-6702/add-feature-flag
pm-6702/email-verification-feature
pm-9933/marketing-copy-update
pm-6702/registration-flows
update-templates
pm-6701/email-verification-selfhost-registration
v2026.2.1-bwpm
v2026.2.1-bwa
v2026.2.0-bwpm
v2026.2.0-bwa
v2026.1.1-bwa
v2026.1.1-bwpm
temp-test
v2026.1.0-bwpm
v2026.1.0-bwa
v2025.12.1-bwa
v2025.12.1-bwpm
v2025.12.0-bwa
v2025.12.0-bwpm
v2025.11.1-bwpm
v2025.11.1-bwa
v2025.11.0-bwpm
v2025.11.0-bwa
v2025.10.1-bwa
v2025.10.1-bwpm
v2025.10.0-bwa
v2025.10.0-bwpm
v2025.9.1-bwa
v2025.9.1-bwpm
v2025.9.0-bwa
v2025.9.0-bwpm
v2025.8.1-bwa
v2025.8.1-bwpm
v2025.8.0-bwa
v2025.8.0-bwpm
v2025.7.2-bwa
v2025.7.2-bwpm
v2025.7.1-bwa
v2025.7.1-bwpm
v2025.7.0-bwa
v2025.7.0-bwpm
v2025.6.1-bwpm
v2025.6.0-bwa
v2025.6.0-bwpm
v2025.1.0-bwa
v2025.5.0-bwa
v2025.5.0-bwpm
v2025.5.999
2025.4.0
v2025.4.0
untagged-4731eaadac73f3dfbbb8
v2025.3.0
v2025.2.0
untagged-815a165c5d70ffe75bc7
v2025.1.2
v2025.1.1
v2025.1.0
v2024.12.0
untagged-5a76b6392a4c8998c63a
v2024.11.7
v2024.11.6
v2024.11.5
v2024.11.4
v2024.11.3
v2024.11.2
v2024.11.1
v2024.11.0
v2024.10.2
v2024.10.1
v2024.10.0
v2024.9.0
v2024.8.1
v2024.8.0
v2024.7.3
v2024.7.2
v2024.7.1
v2024.7.0
v2024.6.1
v2024.6.0
v2024.5.1
v2024.4.1
v2024.4.2
v2024.4.0
v2024.3.3
v2024.3.1
v2024.3.0
v2024.2.1
v2024.2.0
v2024.1.1
v2024.1.0
v2023.12.0
v2023.10.0
v2023.9.2
maui-single-project-android
v2023.9.1
v2023.9.0
v2023.8.0
v2023.7.0
v2023.5.0
v2023.4.0
v2023.3.2
v2023.3.1
v2023.3.0
v2023.2.0
v2023.1.0
v2022.11.0
v2022.10.0
v2022.9.1
v2022.9.0
v2022.8.0
v2022.6.2
v2022.6.1
v2022.6.0
v2022.05.0
v2.18.0
v2.17.0
v2.16.4
v2.16.3
v2.16.2
v2.16.1
v2.15.0
v2.14.2
v2.14.1
v2.14.0
v2.13.0
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.0
v2.9.1
v2.9.0
v2.8.2
v2.8.1
v2.8.0
v2.7.2
v2.7.0
v2.6.1
v2.6.0
v2.5.6
v.2.5.5
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.1
v2.3.0
v2.2.8
v2.2.7
v2.2.6
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.0
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.22.1
v1.22.0
v1.21.0
v1.20.0
v1.19.0
v1.18.1
v1.18.0
v1.17.0
v1.16.0
v1.15.2
v1.15.1
v1.15.0
v1.14.4
v1.14.1
v1.14.0
v1.13.0
v1.12.2
v1.12.1
v1.12.0
v1.11.1
v1.11.0
v1.10.0
v1.9.0
v1.8.1
v1.8.0
v1.7.0
v1.6.5
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.4
v1.4.3
v1.4.0
v1.3.0
v1.2.1
v1.2.0
v1.1.0
v1.0.0
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/android#2267
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @StevenJonSmith on GitHub (Jun 26, 2025).
Steps To Reproduce
Expected Result
AutoFill appears and is on Gboard auto complete.
Actual Result
It doesn't.
Screenshots or Videos
No response
Additional Context
Also happens in other apps, such as My Virgin Media where it directs you to a browser to login.
Build Version
2025.5.0 (20269)
What server are you connecting to?
EU
Self-host Server Version
No response
Environment Details
© Bitwarden Inc. 2015-2025
Version: 2025.5.0 (20269)
📱 google Pixel 9 Pro 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2025.05-rc20@1e665db8aeb92989bdc7e312506cddd4887cde8e
💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1
Issue Tracking Info
@bitwarden-bot commented on GitHub (Jun 26, 2025):
Thank you for your report! We've added this to our internal board for review.
ID: PM-23081
@SaintPatrck commented on GitHub (Jun 26, 2025):
@StevenJonSmith have you enabled "Autofill using another service" in Chrome and Chrome Beta? Note this is a relatively new setting added to Chromium browsers and is separate from the Autofill Services set in Android Settings.
We recently added deep links in Bitwarden (Settings > Autofill) that will indicate if the option has been enabled in the corresponding browser. When the toggle is clicked it will launch the appropriate settings page of the corresponding browser.
When navigating manually on Chromium browsers you can find the option in "Settings > Autofill services > Autofill using another service".
@StevenJonSmith commented on GitHub (Jun 26, 2025):
Yes all enabled, along with accessibility settings too.
I've also been experiencing issues where it displays AutoFill but when an account is selected it fails to actually fill anything.
@Daniel-dev22 commented on GitHub (Jun 28, 2025):
I'm noticing this as well after updating to this version from a version a few months old.
After turning the setting on in chrome sometimes it appears now to auto fill but the username and password isn't even being filled in after I press the account to use in the auto fill pop-up only the totp is filled in.
I tested and this occurs with and without in-line auto fill.
@Daniel-dev22 commented on GitHub (Jul 15, 2025):
I think this may have something to do with chrome as this also is an issue on the production bitwarden app release from Android Play store. Its inconsistent and when it does appear it doesn't always enter anything after pressing on the credential. I also switched to using pop-up to see if that was more reliable than inline autofill.
Interestingly when using Firefox or terminus autofill pop-ups work every time.
It does seem chrome does require you to select auto fill service which sucks because bitwarden doesn't do autofill for cards still so we are now forced to give up using Google for cards and bitwarden for passwords which works 50% of the time if that now. Or choose Google for cards and have to retrieve passwords manually.
When bitwarden autofill does appear as a pop-up sometimes it flashes for a second and goes away. If I click on it fast enough nothing pastes.
@StevenJonSmith commented on GitHub (Jul 24, 2025):
Any update on this? I am still experiencing this, and if it seems to have got worse. Bitwarden is almost unusable at this point on my Pixel 9 Pro with the July drop installed. Bitwarden version 2025.6.1 (20398).
I have accessibility on, autofill settings set. I'm at my wits end with having to manually copy and paste username and password from app to app.
@Daniel-dev22 commented on GitHub (Jul 24, 2025):
I too still am experiencing this :(
@erlonbie commented on GitHub (Jul 27, 2025):
I'm experiencing the same thing :(
Everything enabled as it should. Sometimes for les than 1 second as soon as I refresh the page, I see the bitwarden autofill box, but it disappears right after.
@weirdcrap commented on GitHub (Jul 30, 2025):
I've also been noticing this. 2025.7.1
@jbbolted commented on GitHub (Aug 3, 2025):
This same issue is happening to me as of 8/3/2025. I go to certain websites and nothing shows up, if I manually hit my apps button and open bitwarden I have to copy and paste first username , then password. To put it bluntly this is just a step above using "monkey 123"
I am a single user only "I" use the app, and I pay the 10 dollars a year to support the devs,I can get by with the free version yet you don't seem to care enough about supporting me. All i have is a desktop at home and my phone when out, that I use it for. Lately bitwarden has been very condescending in that it doesn't even email it's paying customers that it is making changes, google pixel phone does post changes but you have to be a monkey jumping through a hoop to find them. I'm 63 recovering from a stroke and this stuff is not fun or convienient, it makes me feel stupid. Believe me when I tell you the stroke already did that to me. there's no need to pick on the old man.
For the first time in over 5 years I am seriously considering changing managers, I don't mind paying to support the devs but I don't like it when you just make changes and not let us know.....you have all our contact info already. I'm sure you have my medical history too so you will know I'm telling you the truth about my stroke. This is dangerous territory your playing in. Some of us don't have a lot of money & still support the devs how about showing a little consideration back.
@jbbolted commented on GitHub (Aug 3, 2025):
This is exactly my problem I try to catch it before it disapears & feel like an idiot doing it.
@MrSourceUnknown commented on GitHub (Aug 4, 2025):
Same issue, where the autofill system stops working with the new Chrome Autofill Integration, or when it does appear it doesn't actually fill any fields.
Have seen some mentions on the Bitwarden community forum that this is being improved, but on the latest Beta track it is actually getting worse instead.
Only reliable workaround I've found is Force Closing Chrome and reopening it when the autofill stops responding.
@jbbolted commented on GitHub (Aug 5, 2025):
This is definitely an integration problem with Google.
I have all my settings set in Google Chrome as recommended. Don't do anything.
I just tried it in Firefox because it's just about the only other browser not forked off chromium.
Hope this helps the devs find a solution.Chrome has been one temperamental s.o.b lately. Google in a nutshell, they just make hidden changes and wait for us beta testers to find them. This is presicely why I don't get involved with beta testing. You encounter a problem in Google you have to convince them it's real. My apologies to the bitwarden devs.
@Estradamis commented on GitHub (Aug 6, 2025):
Subscribing here to get updates as this is very annoying :(
@jbbolted commented on GitHub (Aug 6, 2025):
I just got a Chrome update & it did nothing. Why is Firefox working & no Chrome derivative will?? Maybe this is on the bitwarden devs...It shouldn't be rocket science to fix. This is what irks me with open source..yeah anybody can work on the code but money talks & the other thing walks.
I know 1 thing, it seems like a hand doesn't know what the other hand is doing. This wouldn't take this long with proprietary. Oww....bite my tongue...
@Talkabout commented on GitHub (Aug 13, 2025):
Hi all,
wanted to also chime in that I am facing the same issue. Auto-Fill works for Firefox, Brave and Vanadium. Does not work for Edge. Interesting part: when installing Brave a new option becomes visible in Bitwarden app that activates a "special mode" for Brave Auto-Fill. Only with this option Brave also works. Maybe this option is missing for Edge?
@pamperer562580892423 commented on GitHub (Aug 14, 2025):
Another user here. -- And just FYI for everyone: Android app version 2025.7.2 is out on the PlayStore and there are new settings in the app (Settings --> Autofill), which might improve autofill on Chrome (and Brave):
And two more things, which I also just learned a few days ago:
If you previously changed any browser autofill feature flags (chrome://flags or brave://flags), you may need to reset them now to prevent autofill from breaking with the Chrome’s autofill framework.
You may need to disable/reenable settings and restart the device in between.
PS: The corresponding Help Site was also updated: https://bitwarden.com/help/auto-fill-android/#set-up-autofill
PPS: According to this and this comment to another GitHub issue, you might also check your Android keyboard settings (if I understand it correctly and "in short": the keyboard, e.g. Gboard, must enable "Show suggestion strip" under "Text correction" settings, so that Bitwarden's inline autofill suggestions can also be shown - I'm not sure, if the "suggestions" must be disabled in the keyboard, if you want to see Bitwarden's overlay autofill suggestions 🤔)
@Talkabout commented on GitHub (Aug 14, 2025):
@pamperer562580892423 I saw these settings already, this is what I meant by "special mode" for Brave. Unfortunately this does not help me with Edge.
@SaintPatrck commented on GitHub (Aug 14, 2025):
Hi @Talkabout
I investigated adding a similar option for Edge, but it does not have the same setting for us to deep link to like we can in Chrome and Brave. That being said, I attempted to replicate the issue and Bitwarden is showing suggestions for me, without changing any settings in Edge version 139.0.3405.86.
As a sanity check, could you make sure you have the latest version of Edge? Also, if you enable our Flight Recorder in Bitwarden (Settings > About > Flight recorder) then attempt to trigger autofill and review the logs you should be able to clearly see if Bitwarden is receiving Autofill requests. If we do receive the request you will see logs similar to the ones below. The logs will also indicate if a received request is considered fillable or not. If you do not see these logs being generated while viewing and clicking on fillable fields that usually indicates an issue with the site, browser, or autofill API. Sometimes refreshing the page or restarting the browser can resolve these problems. Should you notice the request being considered "unfillable", we can investigate potential solutions if you provide us the URI.
Example Flight Recorder logs from an Autofill request:
@jbbolted commented on GitHub (Aug 14, 2025):
It Doesn't work on some websites..."https://www.zenni.com" on android Pixel
8 phone. This app was so reliable when it came out. What went wrong? 🙄
Message sent from: John Baumann
On Thu, Aug 14, 2025 at 8:58 AM pamperer562580892423 <
@.***> wrote:
@jbbolted commented on GitHub (Aug 14, 2025):
If I copy and paste from the bitwarden app.. it will work. But that just
defeats the whole purpose of having a password manager..
you guys broke this app. Too many hands spoiled the broth. I'm sick of it.
Take your ai and shove it. AI don't work!
Message sent from: John Baumann
On Thu, Aug 14, 2025 at 8:58 AM pamperer562580892423 <
@.***> wrote:
@Talkabout commented on GitHub (Aug 14, 2025):
Hi @SaintPatrck ,
thanks for taking the time to analyze!
I have enabled Flight Recorder and testet Edge and Vanadium. With Edge, Bitwarden DOES NOT receive any autofill requests, whereas with Vanadium it does. I have tested Edge stable (the same version you did) and Edge Canary. In both cases I do not see any autofill requests in Flight Recorder. I restarted many times, it does not change anything. Not sure What goes wrong or which setting I missed but I would like to mention one more thing: I am using GrapheneOS, not stock Android. Can this be an issue? But why does it work with Brave and Vanadium? Very strange...
@jbbolted commented on GitHub (Aug 14, 2025):
I'm using Google Pixel 8.. from the factory, no adjustments. The chromium
browsers ie. Edge, Chrome, etc are the browsers not working. Firefox works
fine. My apologies to the devs, I just have had it with AI that I see it in
my sleep & have started blaming everything on AI...my bad
Message sent from: John Baumann
On Thu, Aug 14, 2025, 10:15 AM Talkabout @.***> wrote:
@pamperer562580892423 commented on GitHub (Aug 14, 2025):
@jbbolted I just tested it with
https://www.zenni.com/on my Fairphone 5 (Android 15), BW mobile app 2025.7.2, and could successfully autofill username and password in the login screen (I didn't went further as I don't have an account there).It works for me on all four browsers I tested it on: Chrome, Brave, Vivaldi and Edge.
If you want to copy my setup to try it again:
https://www.zennioptical.com/, 2.https://www.zenni.com/, 3.https://auth.zennioptical.com(the third shouldn't be necessary, theoretically, with the first one, but the mobile app needed it for finding it for autofill)I think in one of the browsers, "inline" didn't work at some point, but then the overlay popup appeared (so it seems that there is a fallback to the other option... @SaintPatrck could you verify that?! Because it was like an open question until now, what happens if your "inline choice" didn't work on a given site...)
@jbbolted commented on GitHub (Aug 14, 2025):
The BW auto fill appeared on the keyboard...yes...but when you press it
nothing happens. Maybe it's just that website. I do notice that my passkeys
are working in all apps I tried. I'll try another app that only takes
username and password...
Message sent from: John Baumann
On Thu, Aug 14, 2025, 10:56 AM pamperer562580892423 <
@.***> wrote:
@jbbolted commented on GitHub (Aug 14, 2025):
I just tested it with https://www ups.com and it worked. Your results on
Zenni were the same as mine, the only difference is I have an account in
bitwarden. It goes so far as to let you choose BW, but when you ask it to
fill in it doesn't work... very strange & frustrating
Message sent from: John Baumann
On Thu, Aug 14, 2025, 10:56 AM pamperer562580892423 <
@.***> wrote:
@pamperer562580892423 commented on GitHub (Aug 14, 2025):
@jbbolted
When I pressed it, Bitwarden opened and I could autofill username and password. So it works on my device, but not on yours.
I don't think we have the same results. I created a test account in Bitwarden for "Zenni" and could autofill that random username and password into the Zenni login form (as I wrote above, it worked in Chrome, Brave, Vivaldi and Edge). So it asked me to fill in AND the autofill did work.
@jbbolted commented on GitHub (Aug 14, 2025):
Okay I tried your suggestions, I even added https://auth.zennioptical.com
into BW... It now has a bunch of uri's. I tried inline...BW showed up but
did nothing, I waited for the screen hover but that never showed up.
Let me ask is there a way to reset all the uri's?
Message sent from: John Baumann
On Thu, Aug 14, 2025, 10:56 AM pamperer562580892423 <
@.***> wrote:
@pamperer562580892423 commented on GitHub (Aug 14, 2025):
@jbbolted
Not really in the sense of something auto-magically doing it... Most direct path: delete manually all (unnecessary) URIs...
@StevenJonSmith commented on GitHub (Aug 14, 2025):
I wanted to stop in and say this issue now appears to be resolved for myself. I'm going to leave it open for a BW dev to close as it seems others are still having issues.
Thank you for resolving it Devs, you're awesome. I wish I had the time and understanding to contribute.
EDIT: I've since had the issue again on holiday cottages so I rescind my prior statements. Please fix.
My current version: © Bitwarden Inc. 2015-2025
Version: 2025.7.2 (20551)
📱 google Pixel 9 Pro 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2025.07-rc25@277fcbf14c8332179fcb8bdaef8943eae39dcab6
💻 build source: bitwarden/android/actions/runs/16758228945/attempts/1
🦀 SDK: 1.0.0-20250715.111352-243
🌩 Server: 2025.7.3 @ US
Flight recorder log: https://drive.google.com/file/d/1wKgjh_bHC58nV45Zt0fO-mG2g7wnZ1Lv/view?usp=drivesdk
@jbbolted commented on GitHub (Aug 14, 2025):
Well I tried all your suggestions & I'm going to chalk this one up to..🤔at
least most apps work. I would love to recreate the process of reinstalling
the information into bitwarden and see if that works. Because other
websites & apps work...
Message sent from: John Baumann
On Thu, Aug 14, 2025, 11:38 AM pamperer562580892423 <
@.***> wrote:
@jbbolted commented on GitHub (Aug 14, 2025):
I can't delete my account and start fresh because I have over a hundred
bucks on credit coming to me when I need a new prescription because they
messed up a pair previously made & gave me store credit.
Message sent from: John Baumann
On Thu, Aug 14, 2025, 11:38 AM pamperer562580892423 <
@.***> wrote:
@jbbolted commented on GitHub (Aug 15, 2025):
I've been trying various websites and they are working from both the web
browser and from phone apps...all except Zenni optical. So I'm going to
chalk it up to the website itself. These were all tested on Google Chrome &
Firefox from my phone & the same from Windows 11 on a desktop and from a
Samsung tabA tablet & are working. So I know your a busy team and I thank
you for trying to help me. I can still get into Zenni optical if I need to,
just not from auto fill. So unless other people are reporting issues your
free to close the ticket.
Thank t for all your help and patience in this matter.
I'm going to make a choice & may decide to just go to Firefox as daily
driver
Message sent from: John Baumann
On Thu, Aug 14, 2025, 11:38 AM pamperer562580892423 <
@.***> wrote:
@jbbolted commented on GitHub (Aug 15, 2025):
Just to update you for your hard work & help.
I took a try and just deleted all uri's, and clicked on forgot password.
The phone app sent a link to my email to rest password and it worked. So
what little hair I've left on my head is safe for now 😄
Message sent from: John Baumann
On Thu, Aug 14, 2025, 11:38 AM pamperer562580892423 <
@.***> wrote:
@Talkabout commented on GitHub (Aug 17, 2025):
As feedback: installed Chrome Beta and after enabling "Chrome Beta autofill method" in Bitwarden autofill also works. So it seems that Edge is the culprit here.That is really bad luck as I need Edge as it seems to be the only android browser supporting extensions (especially Floccus, that I need)...
@pamperer562580892423 commented on GitHub (Aug 17, 2025):
If you are using 2025.7.2, that function shouldn't be "Beta". 🤔
@Talkabout commented on GitHub (Aug 18, 2025):
@pamperer562580892423 It is not the option being beta, I installed "Chrome Beta" and this is what is mentioned in the option description.
@pamperer562580892423 commented on GitHub (Aug 18, 2025):
@Talkabout Ah, so BW app can recognize it's the Chrome Beta - and then offer that as "autofill integration"? Interesting to know!
@Talkabout commented on GitHub (Aug 27, 2025):
Hi all,
for me autofill with Edge still does not work. It might be related to the fact that I am using GrapheneOS where Chrome (and its framework) is not installed globally.
Found some other browsers with extension support where autofill works and installed "Mises Browser". Will test it the next days but it looks promising.
@kkplein commented on GitHub (Sep 18, 2025):
On my pixel 8a, it only occasionally actually fills in credentials. Much more often, the bitwarden popup appears, I am able to select the proper username/password, and then I'm returned to the browser (chrome/brave) without anything filled in. The flight recorder shows "Autofill success". Two attempts:
2025-09-18 14:25:12:520 – DEBUG – c – App is foregrounded
2025-09-18 14:25:12:525 – DEBUG – e – Autofill -- Cipher found
2025-09-18 14:25:12:525 – DEBUG – a – Parsing AssistStructure -- null
2025-09-18 14:25:12:531 – DEBUG – a – Autofill request isInlineEnabled=false -- null
2025-09-18 14:25:12:531 – DEBUG – c – Autofill request constructing FilledData
2025-09-18 14:25:12:533 – DEBUG – T – Autofill success
2025-09-18 14:25:13:257 – DEBUG – c – App is backgrounded
2025-09-18 14:25:16:375 – DEBUG – c – App is foregrounded
2025-09-18 14:25:16:384 – DEBUG – e – Autofill -- Cipher found
2025-09-18 14:25:16:384 – DEBUG – a – Parsing AssistStructure -- null
2025-09-18 14:25:16:388 – DEBUG – a – Autofill request isInlineEnabled=false -- null
2025-09-18 14:25:16:395 – DEBUG – c – Autofill request constructing FilledData
2025-09-18 14:25:16:396 – DEBUG – T – Autofill success
2025-09-18 14:25:17:125 – DEBUG – c – App is backgrounded
@Gruven commented on GitHub (Sep 21, 2025):
Same problem :(
© Bitwarden Inc. 2015-2025
Version: 2025.9.0 (20692)
📱 vivo V2454A 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.9-rc34@2bd4834b14d1e199aaa8a9ee4f0db812c27dba53
💻 build source: bitwarden/android/actions/runs/17498992515/attempts/1
🦀 SDK: 1.0.0-2887-7b5d9db2
🌩 Server: Vaultwarden 2025.6.0
@pamperer562580892423 commented on GitHub (Sep 21, 2025):
I would like to add a few things here that might be relevant for at least a part of the current issues. First, there are two things that @dwbit shared first on the Community Forum (and probably also on Reddit etc.):
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.
And there also is a new current bug on the Chromium browsers side – but on Chrome 141 BETA you can enable the following flag: #autofill-update-context-for-web-contents (chrome://flags). Eventually only browser updates will fix this bug.
There is also a new short guide about Autofill on Android, which collects all current "tips" etc.: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941/
@crockk commented on GitHub (Oct 12, 2025):
Chiming in that I am still seeing this issue, pretty inconsistently but very annoying. Should I just switch browsers? Sounds like a chrome issue at its core
@pamperer562580892423 commented on GitHub (Oct 12, 2025):
@crockk In Chrome 141 "stable" you can set that flag: #autofill-update-context-for-web-contents (in chrome://flags), if not already done. (same goes for Brave BTW)
@crockk commented on GitHub (Oct 12, 2025):
@pamperer562580892423 Unfortunately didn't work for me. Specifically the context menu appears above the keyboard but it won't fill any content. Also I am testing on a Google login form. I tried everything suggested in this thread to no avail. :(
@pamperer562580892423 commented on GitHub (Oct 12, 2025):
@crockk That flag has more to do with autofill showing up (not) constantly, I think... Did you check with this short guide also: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941 ?