1Password Keyboard for the smartphone

I could not agree more. Something needs to be done by 1Password to solve this problem.

Hello @dlitz, @DrSuSE, @rscott78, @bjlewis2, @RichardGaspa, thanks very much for sharing your feedback. I've passed it along to the team and added your +1's.

As mentioned, our focus for filling is currently the Autofill service with split screen mode to drag and drop as an alternative. With the 1Password keyboard being part of your normal workflow, I can fully understand why this feels like a step back and I'm sorry for the trouble.

DrSuSE thanks for letting us know about the Ox the Barber app. I've filed that with the team. I did try using their website in Chrome instead and I was able to fill test credentials in the login page.

Thanks again!

ref: IDEA-I-1699

I also frequently needed to use the keyboard. eg I just tried to log in to the sonos app, and didn't get any autofill suggestion, so I had to do the tedious switch to 1P8 app and back. There are far too many problem sites/apps for this to be solvable by just fixing them one by one, we really need a catchall and the keyboard worked pretty well for that.

Hi @benhandley, thanks for weighing in on this. I can definitely see the benefit of an alternate filling option, especially on small screens where drag and drop can be a bit cumbersome. +1 added.

I second the need for a way to have 1 password work in apps consistently.

I am also interested in this to work around flaky behavior with Samsung Keyboard in Chrome. Having a way to force 1password to pop up and fill would be helpful. Specifics of the motivating problem (which I already emailed to support):

I am using 1Password 8.9.3 on Samsung A52 5G (Android 12, One UI 4.1) with Samsung Keyboard 5.4.80.1.

When I put the focus in a username/password entry in Chrome for Android the 1password overlay bar does not appear. The workaround is to press the settings icon on the Samsung keyboard bar to open the settings menu, then the back button to close the menu; after that, the 1password bar overlays the Samsung keyboard bar. This is reproducible 100%. I can supply additional information including screenshots.

Hi @underhat, +1 added for the keyboard.

I suspect loading the Autofill data is exceeding the 5 second limit set by the system causing it not to appear. If that's the case, reloading the app or webpage in a number of ways (including opening you keyboard settings) might give 1Password the second chance it needs to load the relevant data.

The team here is working on some changes to help improve this behavior. Do you see similar results if you slowly tap between the username and password field, minimize then re-open Chrome or refresh the page?

I have upgraded to Android 13 and find the 1password bar rarely shows. If I switch keyboard between Samsung and SwiftKey then back to Samsung the 1password bar then appears, but I have to keep doing this.

Hi @AndyBushman, thanks for letting us know this has been an issue for you.

I'd like to ask you to reach out to us directly via email at support@1password.com so we can help investigate further. Please include a brief description of the issue with your message.

After emailing in, you'll receive a reply from BitBot, our automated responder, with a Support ID that looks something like [#ABC-12345-678]. You can post that here so I can help make sure your message gets to the right place. Thanks again!

1Password autofill doesn't work with the Samsung Keyboards. Or Opera. It does work for my Bank App but only after lost of menu clicking. A fallback is needed.

Thanks for your input @krischik! I've gone ahead and shared it with the team.

You should see in-line suggestions from 1Password with the Samsung's on-screen keyboard. When you tap a sign in field while Samsung Keyboard is in use do you see any prompt from 1Password?

While Opera is not a supported browser, Opera Touch is. If you enjoy Opera, switching to Opera Touch might be a good option for you.

Could you let us know which banking app you're using? I'd be happy to take a look and report any issues.

Thanks again!