Forum Discussion

D11L's avatar
D11L
New Contributor
4 months ago

Pixel 10 Pro Issues

I recently switched from an iPhone 16 to a Pixel 10 Pro and am experiencing significant functionality issues with 1Password that need to be addressed.

The autofill feature is consistently unreliable. In Chrome, username and password autofill succeeds roughly half the time. When automatic filling fails, I have to manually click and hold to select "Autofill," which still frequently doesn't populate the form fields correctly. This forces me to open the 1Password app and manually copy credentials multiple times per day, which is both inefficient and frustrating.

Native app integration has similar problems. Login functionality is inconsistent at best, and browser-based authentication within apps rarely works (I've had it succeed perhaps once since switching devices).

Passkey functionality is particularly problematic. 1Password consistently fails to recognize available passkeys across multiple sites. This is reproducible every time I attempt to authenticate on Microsoft's website, where the passkey option simply doesn't function.

Additionally, OTP codes still require manual copying and pasting rather than seamless integration.

I've been a loyal 1Password user for years without experiencing these issues on iOS. The Android performance gap is substantial enough that it's affecting my daily workflow and making me reconsider the platform entirely.

Could you please confirm whether your team is aware of these Android-specific issues and provide an estimated timeline for fixes? I need to understand if these problems are being actively addressed or if I should evaluate alternative solutions.

I appreciate your time and look forward to your response.

6 Replies

  • DerekC's avatar
    DerekC
    New Contributor

    OK, thanks Dave.   Most of those things were already in place, with the exception of the "flags" thing, which I just did.   I'll report back on any further problems. 

  • Hello folks, 

    I'm sorry for the issues that you're experiencing when using 1Password on your Pixel phones. I've recently been using a Pixel 10 Pro myself as a work device and I can definitely understand the frustration.

    That being said, I do have some good news to share! We're reported several Android filling issues to the Chromium team and that team has implemented multiple fixes and improvements that help the experience a lot. Some additional steps are needed to access those improvements at this time. First, make sure that you're using the following: 


    Then, double-check that 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 (the improvements are currently gated behind this feature flag by the Chromium team, eventually the feature flag won't be needed): 

    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. Let me know how that goes, if you run into filling issues after implementing these steps then let me know the specific app/browser/webpage where you're running into issues. 

    -Dave

  • calstevej's avatar
    calstevej
    New Contributor

    I just switched to a Pixel 10 from and iPhone 16 yesterday and I've also run into all these same issues. This thread looks to be several months old so it doesn't seem that much progress has been made. That's very disappointing. My whole family uses 1Password. Might be time to switch to something else. 

    • GSK's avatar
      GSK
      Occasional Contributor

      I have Pixel 8 Pro, but the following (posted recently) took care of the problem for me.

      https://www.1password.community/discussions/1password/ongoing-autofill-issues-on-android/159059/replies/164127

       

  • D11L's avatar
    D11L
    New Contributor

    I've been working with the 1password team through email who have been incredibly helpful. They've made me aware that the issue is known and have been working with Google to iron out the kinks. 

    For those that would like an immediate fix. Do the following: 
    1. Install Chrome Beta - there are fixes that are intended to go out at the end of September '25 that will help with autofill.
    2. https://support.google.com/android/answer/14324187?hl=en-GB.
    3. Set the Chrome flag "Android autofill updates context for WebContents (#autofill-update-context-for-web-contents)" in Chrome Beta to "Enabled" instead of "default". You may access chrome flags by navigating to "chrome://flags" in your chrome beta browser.

    While this doesn't fix all issues. It does significantly improve the experience. I still run into issues with native app autofill and passkey issues at times. Hope this helps you all!

  • robdersen's avatar
    robdersen
    New Contributor

    Strong +1 on this observation.
    (Another person here just switched from iOS to Android)

    The reliability of 1password Autofill on a Google Pixel with "plain Android on a Google Pixel" is very bad and unreliable compared to iOS.

    I am certain to have all the recent settings correct (Autofill set to 1password in Android Settings, Lastest Chrome settings are set as written here https://support.1password.com/android-autofill/ ) but no matter the settings I tried (having the popups on the keyboard or inline with the fields) the autofill sometimes works and sometimes don't.

    I only signed up here today as I saw this post but I have little faith in this getting fixed as this feels "Android" and not "1password" (as Bitwarden has the same bad behaviour on Android) 
    My alternative would be Google Password Manager only (which I would like to avoid...)

    Grateful for any tips here ...

    EDIT - Searching through this community brought these threads to life showing the exact same issues: