Autofill prompts only appear after opening 1password app

Hi @belzy, thanks for the update. I'm glad to hear that helped!

If you're seeing consistent behavior in the browser now, you can try re-enabling "Show filling suggestions".

If the inconsistency returns, I would suggest confirming your browser is up to date as well as restarting your browser if you see unresponsive behavior. You can restart your browser by opening Recents (the square icon on a Pixel or a short swipe up on home), swiping up on the browser window in Recents, then reopening the browser.

By turning off the suggestions and switching to a prompt above the keyboard it seems to work now without having to switch focus. You still need to click on the 1Password button above the keyboard, but I can live with that. Just glad it works every time now.

Hi @timbishop, @belzy, Kumnaa and @terahertz thanks for writing in and letting us know you're seeing this behavior as well.

The investigation on this continues and we're looking at a few optimizations to Autofill that should help. My apologies for any disruption. When you next run into inconsistent or non-responsive Autofill in Chrome I'd like to ask you to try restarting the browser then let us know if you see any improvement in behavior.

To restart Chrome, you can open the Recents menu on your device. Recents can be opened by tapping the square or three bars icon along the bottom of your screen. If you use gestures, it's typically a short swipe up from the bottom of the screen. From there you can locate the Chrome window, swipe up on it, then reopen Chrome.

Thanks again!

Signed up just to post.

1pw8 has been a nuisance for a while now on my OnePlus 9 pro.

Got a new nothing phone 2 and exactly the same issues.

Have to open and login to 1password then switching back to the app or chrome for a chance at autofill showing me some autofill options.

Another +1 for this on my Pixel 7

+1 for this issue. Pixel 7.

Just wanted to add a "me too" to this. Pixel phone with latest Android, same situation as above. I'd noticed when coming out to the app to copy the password as a workaround that the autofill was working when coming back to Chrome. jkane001's suggestion of just switching focus from Chrome to something else and back is sufficient.

Will give the beta a whirl.

Hi Ekalb, thanks for following up with us. That's no problem! There's a lot of information in this thread, it's easy to miss a few details.

Hi sethmad, thanks for giving that a try. I'm sorry to hear that only worked temporarily. Hi jkane001, thanks for your input on this.

From our investigation into reports of this sort of behavior we believe it may be related to changes in Autofill that have caused a slight delay in the filling response, or that browsers that rely on Autofill compatibility are not restarting the Autofill service in some cases once it is stopped.

I'd like to ask you to try filling in another supported browser that does not use Autofill compatibility such as Firefox or DuckDuckGo. Is filling behavior more consistent for you there?

We've also included some improvements to Autofill in our recent beta releases. If you'd like to update to the beta and check the filling behavior in Chrome you can find steps to join in our guide: Use 1Password beta releases

I will note that there is a regression with the latest beta that causes Biometric unlock to be reset. So, if you update, your password will be required to unlock the app before resetting Biometric unlock.

I've noticed this too, but I've found a workaround that seems to work consistently (and might help troubleshoot): If you do anything that changes the focus of Chrome WRT the OS, then bring it back to focus, it works. What I mean by that: when you are on a form that isn't popping suggestions, go back to the launcher (phone's home screen) and then go back to the browser. Even just opening the recents view (on my Pixel, by swiping up from the bottom of the phone just slightly) and picking the browser again will do it.

It does seem that once 1Password is unlocked, it's more consistent for other sites on the first attempt, so it seems to be a combination of things happening, perhaps? Started (for me) a few weeks ago, but I just kept forgetting to mention it. I'm on version 8.10.9 (81008012), and I'm in the beta channel.

Hi 1P_Timothy, that fix worked temporarily, but after a restart the problem returned as before.