Recent autofill issues on Android and iPadOS

Hello JasonDunnCA​! 👋

Thank you for sticking with 1Password for so many years! On both iPadOS and Android, since those platforms are more locked down, 1Password relies on the native credential filling methods provided by those operating systems to save and fill credentials. This means that we have less control over filling there than we do in desktop browsers on macOS where filling is entirely handled by 1Password in the browser. 

That being said, the team is always working to improve filling across all platforms and I might have some suggestions that can help. I'll reply directly below: 

On Android, specifically a OnePlus 13 phone, it fails to trigger in Chrome probaby 80% of the time. It simply doesn't offer itself as an auto-fill option above the keyboard. Yes, it's configured to do so.

There have been some recent updates to Chrome that improve autofill but some additional steps are needed. First, can you make sure that you're using the following: 

• Chrome version 141 or later: Update Google Chrome
• 1Password for Android version 8.11.20 (or later): How to keep 1Password up to date

Then, double-check the autofill is setup correctly: 

1. Open Chrome.
2. Tap the three dots (⋮) in the top-right corner > Settings > Autofill Services
3. Tap Autofill using another service, then tap Restart Chrome when prompted.

Next, make sure that the following feature flag is turned on in Chrome: 

1. Open Chrome/Brave.
2. Type chrome://flags into the address bar and open the page.
3. Search for Android autofill.
4. Under Android autofill updates context for WebContents (#autofill-update-context-for-web-contents), choose Enabled.
5. Tap Relaunch when prompted.

Then try to fill again. If that still doesn't work then can you share a couple of the webpages where you're still running into this issue on? 

On Android, a Pixel 9 Pro phone, I have to go into the stand-alone product quite often because (I think) web sites aren't using form fields that 1Password can recognize. This happens often on sites such as The Verge where they ask for email and password as seperate form fields, one after another. This is very common now, so why doesn't 1Password support this better?

Does The Verge's website now work better with autofill after you've followed the steps that I described above? Let me know if it doesn't. 

When I use it in Edge on iPadOS 26, on many web sites, 1Password triggers, but then doesn't put anything into the form fields until I tap into the form then the username and password suddenly appear. If I press submit before tapping into the form field, it will fail

On iPadOS, we rely on an Apple Technology called iOS Password AutoFill to detect and fill fields and 1Password only provides the data for the experience. This is likely something that you'll need to report to the developer of the website in question so that they can determine why AutoFill isn't properly filling into their website. However, so that I can confirm where the issue is occurring, can you tell me the following:

1. Can you provide a website where you're seeing this issue so that I can test on my end? 
2. Do you see the same issue in Safari? 

I look forward to hearing from you.

-Dave