mirror of
https://github.com/bitwarden/android.git
synced 2026-03-15 06:59:05 -05:00
Autofill in browsers on Android P #231
Closed
opened 2025-11-07 08:31:50 -06:00 by GiteaMirror
·
36 comments
No Branch/Tag Specified
main
crowdin-pull
sdlc/sdk-update
pm-33356/policy-changed-push-sync
premium-upgrade/PM-33508-billing-api-service
PM-30130-remove-archive-feature-flag
tooling/improve-review-workflow
PM-32663/update-vault-migration-screens
llm/add-resolving-sdk-updates-skill
QA-1523/sanity-test-saucelabs
release/2026.3-rc48
PM-24380/flight-recorder-redact-hostname
PM-26577-app-links-support
PM-26896-autofill-fix
release/2026.2-rc47
PM-32714/fallback-to-web-vault-host
pr-6572
PM-28834/setting-app-layout-horizonos
vvolkgang/process-release-notes-v2
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
No Label
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#231
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 @szale9001 on GitHub (Jun 4, 2018).
Android P, which is currently in Beta, now allows apps to take advantage of the Autofill framework in browsers without using a full Accessibility service. It requires that both the browsers and apps update things to take advantage of this.
Currently, bitwarden autofill DOES work in android P, but only in apps. So, I wanted to post some info I found with regards to getting autofill working in browsers to since using the autofill framework is always going to be better than using the accessibility service. I hope it can be implemented!
https://blog.dashlane.com/android-p-autofill/
https://developer.android.com/preview/features/autofill#compat-mode
I'm signed up for the bitwarden Android beta and running Android P, so if you make any changes and would like some feedback, I would be happy to help.
@kspearrin commented on GitHub (Jun 5, 2018):
Thanks for the info. Unfortunately we will have to wait until Xamarin releases support for android p before I can begin working on this.
Also, we support autofilling in Oreo on a few browsers like Firefox Focus and DuckDuckGo. Do you know if these work in Android P?
@szale9001 commented on GitHub (Jun 5, 2018):
I understand.
Also, I dl'ed Firefox focus, and I got an autofill prompt, so I think you're good there. Hoping you can get things working for chrome, when xamarin updates. And thanks for the app/service. Really enjoying it.
@fredgolightly commented on GitHub (Aug 7, 2018):
9 is released in preview form - will this allow you guys to work on Android P autofil?
https://blog.xamarin.com/xamarin-android-9-0-p-preview/
@szale9001 commented on GitHub (Aug 16, 2018):
Just wanted to follow up on this. Is this possible with the xamarin P preview release? Or will you be waiting for stable channel?
@kspearrin commented on GitHub (Aug 16, 2018):
Sounds like it is. I have not got around to installing the preview yet though.
@Mentis commented on GitHub (Sep 2, 2018):
It was released: https://developer.xamarin.com/releases/android/xamarin.android_9/xamarin.android_9.0/
@szale9001 commented on GitHub (Sep 3, 2018):
Very exciting! Just fyi @kspearrin, looks like they moved the documentation here. It's not longer at the link the in the first post.
https://developer.android.com/reference/android/service/autofill/AutofillService#compatibility-mode
@kspearrin commented on GitHub (Sep 3, 2018):
Thanks, I'll update soon and check it out.
@kspearrin commented on GitHub (Sep 3, 2018):
Tried this out today following the instructions from their docs here:
https://developer.android.com/reference/android/service/autofill/AutofillService#compatibility-mode
I have compatibility mode set like:
Tried both Opera and Chrome, yet I get no
OnFillRequestevent in the autofill service...@kspearrin commented on GitHub (Sep 3, 2018):
Commit with updates:
4f0ea44078@szale9001 commented on GitHub (Sep 3, 2018):
Hmm, I'm honestly not really a programmer so I'm not sure why it wouldn't have worked. I tried searching github though but really only found this:
03c9e1de1bNot sure if it might help, and it looks somewhat similar to what you did. That said, I would be happy to test a beta and report back (I'm in that channel on the Play Store and running Pie on a Pixel 2)
@kspearrin commented on GitHub (Sep 4, 2018):
I'm not sure what could be wrong. Maybe I need to update to Android Support libraries v28 as well, but those don't seem to be available for Xamarin yet.
@kspearrin commented on GitHub (Sep 5, 2018):
If you want to try the dev build apks with the compat mode enabled on a device, you can download them from here: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts
I don't have a device that can run Android P, so I was only testing on a simulator. Maybe there is a difference?
@Mentis commented on GitHub (Sep 5, 2018):
Actually it works for me in Chrome (took build 1515)! We just need to add more browsers now.
@Mentis commented on GitHub (Sep 5, 2018):
I have Pixel XL and Android 9
@szale9001 commented on GitHub (Sep 5, 2018):
@kspearrin Yea, it actually worked for me as well (Pixel 2 with Android 9). That said, it stops working after 2 or 3 sites on my device. Restarting chrome seems to fix it though, so that might be a chrome issue (Chrome 69) vs a bitwarden issue
EDIT: Also, not sure how good the Android simulator is, but there is a flag in chrome (Autofill Accessibility) that is enabled by default on most chrome loadouts. Maybe if you explicitly enable it in the simulator, you'll be able to test it successfully?
@kspearrin commented on GitHub (Sep 6, 2018):
@szale9001 Where do you see this setting in Chrome? I can't find it on my simulator. Chrome 68
@szale9001 commented on GitHub (Sep 6, 2018):
Should be about to find it here:
chrome://flags/#enable-android-autofill-accessibility
Just set the flag to enabled and restart the browser.
@kspearrin commented on GitHub (Sep 6, 2018):
@szale9001 Thanks, that fixed it! I guess default is off for whatever reason.
@szale9001 commented on GitHub (Sep 6, 2018):
Well because Google is Google, default means whatever they want (just to make it extra confusing). So default for Android 9, Pixel is probably enabled and default for your sim is probably off. Either way, glad it worked!
@kspearrin commented on GitHub (Sep 6, 2018):
I added more support for other browsers in latest build
@fredgolightly commented on GitHub (Sep 6, 2018):
This still isn't native support, is it? It's just enabling the acessability service which can cause lag and batter drain. AFAIK there's still not native web browser autofil api working
@kspearrin commented on GitHub (Sep 6, 2018):
Not sure what you mean, but it's about as native as you can get with browsers.
@szale9001 commented on GitHub (Sep 6, 2018):
@fredgolightly In Android Pie they built in a way to allow the autofill API to access certain parts of the accessibility system on a per-app basis (mostly browsers). So while there might be a performance hit while using this autofill mode in those specific apps, it is nowhere near as bad as enabling the global Accessibility service.
@szale9001 commented on GitHub (Sep 17, 2018):
I think we are good with this now. Closing issue.
@szszoke commented on GitHub (Oct 29, 2018):
The issue @szale9001 mentioned still happens to me. I'm running a OnePlus 6 on Pie. I enabled the accessibility flag explicitly in the browser. It still stops working after 2-3 sites and I have to restart Chrome to fix it.
@szale9001 commented on GitHub (Oct 29, 2018):
Yea, still happens. Unfortunately I think it is a chrome bug. I tried dashlane and 1password to see if they consistently threw autofill prompts and they seemed to have the same problem.
@Chevrah commented on GitHub (Nov 29, 2018):
Is this something that is being worked on?
@kspearrin commented on GitHub (Nov 29, 2018):
No, since it was completed several months ago.
@Chevrah commented on GitHub (Nov 29, 2018):
I just updated to Pie on my S9 and Autofill just doesn't work in the browser.
@kspearrin commented on GitHub (Nov 29, 2018):
Are you using a browser that is compatible with autofill ?
@Chevrah commented on GitHub (Nov 29, 2018):
I'm using chrome, and enabled chrome://flags/#enable-android-autofill-accessibility
@kspearrin commented on GitHub (Nov 29, 2018):
Did you enable the Bitwarden auto fill service?
@Chevrah commented on GitHub (Nov 29, 2018):
Yes. It works in apps.
@ghost commented on GitHub (Jan 5, 2019):
Same issue here, not working in Chrome 71 or Chrome beta. I tried setting the flag, auto fill in apps and Firefox works. I have s9, i'm thinking this might be a Samsung bug?
@ozolli commented on GitHub (Jan 6, 2019):
Tested today the autofill framework on a Huawei Mate 10 Pro, Android 9 and Bitwarden or Dashlane with Chrome Beta or Firefox Beta.
Each of the 4 combinations has the same issue : It works on 1 or 2 sites then I have to restart the browser to make it work again. Looks like an Android 9 bug...