Google Chrome for Android will soon be updated to support third-party autofill services, including password managers. I guess I had assumed this just worked, but looking at it now, I can see that's not the case.
"Google is the default autofill service on Chrome, providing passwords, passkeys and autofill for other information like addresses and payment data," Google developer advocate Eiji Kitamura writes. "A third-party password manager can be set as the preferred autofill service on Android through system Settings. The preferred autofill service can fill across all Android apps. However, to autofill forms on Chrome, the autofill service needs to use 'compatibility mode.' This causes glitches on Chrome such as janky page scrolling and potentially showing duplicate suggestions from Google and a third party."
To address this problem, Chrome 131-which arrives on November 21-will allow third-party autofill providers to natively autofill passwords, passkeys, credit cards, and other personal data.
But you don't have to wait for Chrome 131: You can enable this functionality today by enabling a Chrome flag. Assuming you've already chosen a third-party autofill provider in Android Settings (in Passwords, passkeys, & accounts), open Chrome for Android and navigate to the following URL:
chrome://flags#enable-autofill-virtual-view-structure
Then, change that flag to "Enabled" and restart Chrome as prompted. Then, open Chrome settings and tap "Autofill Options." Change this setting to "Use other providers." Then, restart Chrome again.
When you get back, you should be able to sign in using whatever Autofill provider you selected in Android. I assume a similar change is coming to Chrome for iOS: Looking at that app, I see it behaves as does Chrome for Android, in that it uses Google Password Manager, not the autofill provider I selected in iOS.