Repeat credential process twice before fields populated

mikejg
mikejg
Community Member
in iOS

iPad Pro 13 (m4). I access a protected site, and the credentials show up in the floating tray at the bottom of the screen. After selecting the credentials, 1Password opens, authenticates with FaceID, and then disappears, without populating the credentials. If I do it a second time, the credentials are then populated as expected.

I’ve switched back to the official/stable channel version to see if the problem goes away.

Comments

  • Kakkoister2
    Kakkoister2
    Community Member

    Hopefully they fix this bug soon, also affects myself as well.

  • Dave_1P
    Dave_1P

    Hello @mikejg and @Kakkoister2! 👋

    I'm sorry that biometric unlock isn't working properly for 1Password on your devices. So that I can investigate this further, I'd like to ask you to reproduce the issue one more time and then create a diagnostics report from your iOS device:

    Sending Diagnostics Reports (iOS)

    Attach the diagnostics to an email message addressed to support+forum@1password.com.

    With your email please include:

    Please send the entire file.

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

    -Dave

    ref: dev/core/core#26726

  • Kakkoister2
    Kakkoister2
    Community Member

    @Dave_1P Thanks for your time Dave, this happens to me using just device passcode unlock, the filling issue I noticed can be hit or miss, depending on the app, did you still want a diagnostics report?

  • Dave_1P
    Dave_1P

    @Kakkoister2

    I'm sorry for the delayed reply. Are you able to reproduce the issue using 1Password for iOS 8.10.36-1? If you are then, the next time that the issue occurs, please follow the steps posted earlier in this thread to send in a diagnostics report so that the team can take a look.

    -Dave

  • Kakkoister2
    Kakkoister2
    Community Member

    @Dave_1P No, current Beta version fixed issue and works as expected, thanks for checking!

  • Dave_1P
    Dave_1P

    I'm glad that the current beta fixed the issue. 🙂

    -Dave