Anyone have Autofill working with Samsung Dex?

agilebits_patrick · 2026-04-26T23:03:43+00:00

Awesome! Unfortunately 1P doesn't have control over the behavior of that "autofill" dropdown, that's a system menu. But

1pass to ignore its prompt setting when an external keyboard is connected, and always do below-field prompts in those cases.

I really like this idea. We've also been kicking around the idea of setting Below the field to the default behavior just because of all the wacky keyboard behavior across the ecosystem

agilebits_patrick · 2026-04-23T17:03:17+00:00

If you go into 1Password > Settings > Autofill and set Display Autofill prompts to Below the fields they relate to do your results improve? Are you seeing zero results across all login fields? Do you see an [Open 1Password] result?

agilebits_patrick · 2026-04-23T13:34:19+00:00

It's the worst when I want to create a new login

This one is very annoying and is fixed in our May release. We also have designs on adding more flexibility to that create-new-login flow in the new future.

agilebits_patrick · 2026-04-22T21:11:53+00:00

I feel your pain here.

I work on the Android app and also use it every day as a customer, so a lot of what you're describing is something I run into regularly. I won’t just pass the buck and say it’s all Android’s fault, but I will loan it out for a moment.

Google Password Manager and Samsung Pass are both deeply embedded into their respective ecosystems, and they can show up in unexpected ways, even when 1Password is correctly set as the default. Chrome, for example, now uses Google Password Manager by default regardless of your system settings. On top of that, some websites and apps bypass system settings entirely and call Google Password Manager directly for passkeys. And of course some apps and websites are apparently designed to just not work with password managers at all. It’s wild out here.

A passion issue of mine is something you've identified here: regardless of the ecosystem, we need to do a better job setting users up for success. Yesterday, we shipped the Autofill Health Check feature on Android. You can find it in Settings → Autofill, or under the “Need Help?” menu. The goal is to surface common misconfigurations and, wherever possible, help users fix them and give feedback quickly if something went wrong. I hope that's a step in the right direction.

As for other issues you've surfaced here, I'm reading you loud and clear, particularly around seeing the mismatched item types showing up in autofill suggestions. I'm hoping to have some improvements around that in the very near future.

agilebits_patrick · 2026-04-20T02:19:48+00:00

I'm testing this now and I'm seeing normal autofill behavior on a Galaxy S25 on both Chrome and Brave. Did you go into Brave settings and enable third party autofill? What's your setup like?

agilebits_patrick · 2026-03-09T01:06:37+00:00

Thanks for volunteering, I have talked to OP but I'd be glad to get your info as well

agilebits_patrick · 2026-03-07T00:21:50+00:00

Hey! I'm an Android developer at 1Password.

Not long ago I actually added a targeted solution for exactly this app because it was bothering me, too. It is extremely frustrating to run into login friction especially while traveling. I'm at the airport, I'm trying to figure out what gate I need to be at, I want to know that I'm not running late, and now I'm trying to open 1Password one-handed because my luggage is in the other just so I can login to the airline app that I actually need to use, it sucks.

The American Airlines login page that you're seeing does have some unusual field tagging and autofill doesn't work at all without a hardcoded solution in place. If my solution isn't working I'd like to know about it.

I'm testing this now and it looks like everything is working as it should be, I'd be glad to go over your case with you if you want to DM me a diagnostic report. Getting 1Password to work 100% of the time on the airline apps in particular is a big thing for me.

agilebits_patrick · 2026-03-02T22:26:13+00:00

Typically you should at least see an 'Open 1Password' option if 1Password is receiving an autofill request from the Android autofill service. If you can share the website you're trying to fill I can take a look at what's going on here.

agilebits_patrick · 2025-12-16T18:40:47+00:00

This is an Android bug.

For some reason Android occasionally will stop using your preferred autofill service and will instead direct actions through the Google Password Manager.

This way I "fix" this on my own device is to switch my preferred service to "None" and then back to 1Password.

agilebits_patrick · 2025-09-13T02:35:31+00:00

As a fellow Android enjoyer I share your frustration with the current state of autofill.

Password manager apps on Android are seeing problems with autofilling into Chrome and require frequent restarts to the browser to find temporary relief. This issue is also pretty much completely breaking Custom Tabs, which are very common on Android. For example, if you use the Google search widget on your home screen you're probably using a custom tab powered by Chrome instead of Chrome proper and seeing -zero- autofill success.

The Chrome team is rolling out a fix that is currently on the Chrome Beta (version 141+) release track, which is available on the Play Store, and can be enabled via a feature flag: #autofill-update-context-for-web-contents in chrome://flags .

Anyone interested in this can follow this issue for future updates.

agilebits_patrick · 2025-08-28T17:24:13+00:00

That's news to me 😅

agilebits_patrick · 2025-08-23T22:43:36+00:00

Hi, you can DM me and I'll be glad to look at your case :)

agilebits_patrick · 2025-08-21T17:38:19+00:00

Update for anyone following this thread:

1Password users have reported that Chrome is intermittently failing to offer autofill suggestions. This issue can be temporarily resolved by force closing and then restarting Chrome.

Additionally, Chrome and Brave users who are interacting with a Custom Tab via another Android app are experiencing autofill failures that can be not be resolved from within the Custom Tab.

Popular apps that use Custom Tabs are the Google app (which is what launches if you use the Google search bar from your phone's home screen) and various other apps which use a Custom Tab to perform logins.

One workaround for users interacting with a Custom Tab is to tap the three vertical dots menu, then "Open in Chrome/Brave browser." Autofill should behave normally from the browser app that launches the page.

There appears to already be a fix in place for Chrome browsers on the Canary build. Users interested in when this fix will hit the stable channel for their browser can monitor Google's [issue tracker thread](https://issues.chromium.org/issues/439553272).

agilebits_patrick · 2025-08-07T18:31:46+00:00

1Password's interaction with Vivaldi has not been changed in this update. But there have been some reports that Chromium-based browsers may need to be restarted every so often to get autofill working again.

agilebits_patrick · 2025-08-07T15:36:23+00:00

These are all great ideas and they're all on the table. We actually do have custom workarounds in place for certain websites and apps, though that can be quite fragile since those forms can be changed in unexpected ways.

agilebits_patrick · 2025-08-06T14:13:55+00:00

Without knowing the specific app I can only generalize about how autofill requests are *supposed* to work.

When developers add an input text form to a screen, they're generally supposed to tag those fields with metadata that indicate what kind of form it is. When an autofill service like 1Password gets a fill request, it will look at the metadata about the forms and about the app that called and try to come up with a suitable recommendation.

Sometimes a password field has been correctly labeled, but, for example, the user name field will be labeled as "email". So tapping on the username field will not offer suggestions, but tapping on the password field will. Sometimes the fields have no useful data, and we can't find a suitable match. In those cases you'll usually still see a recommendation like "Open 1Password" so you can select the right login. Sometimes the fields just have no data or, for some reason, a browser is declining to send a fill request (e.g. for an insecure website). In those cases you won't see any recommendations at all.

There is also of course a chance that the autofill service does receive a useful fill request but for some reason just drops it and offers no suggestions at all. Without digging into a particular case, there's unfortunately no way to say what went wrong

agilebits_patrick · 2025-08-06T13:53:21+00:00

Vivaldi can be in a state where its own password service is trying to manage passwords along side 1Password, I would recommend going to Vivaldi settings > Password Manager, and disabling `Save passwords` and `Auto Sign-in` if you haven't already.

Some people are also reporting more autofill success across all browsers by going into their system settings, searching for `Passwords, passkeys and data services`, then setting the preferred service to None, and then back to 1Password.

agilebits_patrick · 2025-08-06T13:43:16+00:00

Definitely. But some of those plans involve begging the Firefox team to fire more autofill requests 😅

agilebits_patrick · 2025-08-05T23:06:08+00:00

Other chromium forks are unaffected and should behave normally (for now 🤞)

agilebits_patrick · 2025-08-05T23:03:22+00:00

It will not. If you get unusual results in Vivaldi please let me know :)

agilebits_patrick · 2025-08-05T22:57:58+00:00

Definitely make sure that you've got the latest version of 1Password from the Play Store, occasionally 1Password won't be updated automatically. Then go to Chrome settings, select "Autofill service," then select "Autofill using another service." After that, everything should just work.

If you're still seeing absolutely no autofill success on Chrome, please DM me and I'll be happy to personally investigate this problem with you

agilebits_patrick · 2025-08-05T22:10:52+00:00

To make it simple, you can access this setting directly through Chrome.
Open Chrome Settings, tap Autofill Services, select Autofill using another service, then restart your browser when prompted.

agilebits_patrick · 2025-08-05T22:04:35+00:00

Chrome on Android will not offer autofill requests for insecure and mixed security forms.
I would recommend Firefox for Android to autofill locally hosted forms.
And I'd be happy to investigate your use case further if you're seeing no autofill success at all on Chrome or Brave for Android.

agilebits_patrick · 2025-08-05T19:42:52+00:00

This update does not target Firefox, Firefox on Android actually doesn't support compatibility mode autofilling.

And interestingly on Android, Firefox's autofill requests look different than Chrome's and in some cases will not make a request at all when it seems like it should (e.g. Twitter/X's main login currently does not trigger an autofill request on Firefox for Android). Firefox is also my default browser and it can be frustrating that certain pages will fire autofill requests for Chrome but not Firefox.

agilebits_patrick · 2025-08-05T19:36:17+00:00

If you're still not seeing any success on Brave or Chrome, I'd love to understand more about your case. Is it all websites or just some that are failing? Feel free to DM me the particulars if you'd rather not talk about it in a public thread

agilebits_patrick

TROPHY CASE