Support for fingerprint unlock [released]

145679

Comments

  • juanii
    juanii
    Community Member
    edited January 2016

    Great to hear that the new beta is available. I'll try it right away.

    We look forward to hearing your feedback on the beta! Thanks.

    @saad I don't think I'll have any valuable feedback this time, I ain't a Teams user and I don't own a fingerprint capable phone, anyway I'm glad the new beta is out. I'll wait until the next release (hopefully with multiple local vaults) to contribute.

    Regards

  • hubpf
    hubpf
    Community Member

    I only see 1Password 5.0 Beta 1. No 1Password 6.

  • Xaelias
    Xaelias
    Community Member

    @hubpf because android was 4.x, so next version is 5.

  • hubpf
    hubpf
    Community Member

    @Xaelias I'm using S6 with Android 5.

  • juanii
    juanii
    Community Member
    edited January 2016

    @Xaelias Maybe @hubpf is a little confused because the release post mentions "1Password 6" everywhere :p

    Edit: Oh, @saad also mentioned the new "1Password 6" in his post. I hope that's not a mistake and the next incarnation featuring OPVault and multiple vaults support is around the corner :)

  • bdbplatano
    bdbplatano
    Community Member

    I'm really happy to see this beta, and will gladly report any bugs I see. So far.. none :D

    I do have one question though. Universal Search. I can't imagine it would be that hard to implement search into the top bar. It's already there, just hidden under a few taps unfortunately. Other than that the update looks really good!!!

  • hubpf
    hubpf
    Community Member

    @juanii You are right... :)

  • amcelwee
    amcelwee
    Community Member

    @saad @peri @brenty looking good so far. This is a good step in the right direction, so hopefully we see continued momentum on the platform.

  • EnerJi
    EnerJi
    Community Member

    @sameerchavan They've said a few times they are using the Android 6 fingerprint API, so you'll need to be running Android 6 to get fingerprint unlock. What kind of phone are you using?

  • Xaelias
    Xaelias
    Community Member

    Yeah I think some of you are confusing your android version and 1password version.

  • AGAlumB
    AGAlumB
    1Password Alumni

    @Xaelias: I'll have to come back here after I get some sleep to take in all the feedback, but I think this confusion is at least partially our fault. It looks like we've got some material showing version 5 and others are version 6. Sorry about that! :blush:

    To be clear, it's going to be 1Password for Android 6.0, which lines up nicely with both Android M(arshmallow) and (most of) our other platforms. That's my story and I'm sticking to it. ;)

  • 411pass
    411pass
    Community Member

    This is another area where you could be doing a much better job: versioning. For those of us who use all the platforms the versioning is very confusing, it ranges from 4 to 6. Why can't you just be consistent, in terms of look and feel and version numbers?

  • Xaelias
    Xaelias
    Community Member

    @411pass Because these are different teams, and they won't just change the version number to stick to the other apps progress. Obviously the android app was far behind the iOS one, and should NOT have the same version number. It was lacking most of the funcitonnalities...

  • 411pass
    411pass
    Community Member

    This would have been a great time to call it 6 instead of 5 ...

  • Hey @411pass and @Xaelias. Indeed the versioning has been different because, well, we were on different versions on iOS and Android. In fact, until last week, 1Password on iOS and Mac were even different versions, since 1Password 6 for iOS came out while 1Password 5 for Mac was still the latest on Mac.

    That said, we've decided to go with 1Password 6 for this release, since it contains support for Teams. We'll work from there. :)

  • Arm
    Arm
    Community Member

    @brenty fingerprint works great when entering app but when trying to fill login on any website I am always asked for master password. I assume this is a bug and not a feature right? The whole point of fingerprint is to avoid entering master password every time right?

  • EnerJi
    EnerJi
    Community Member

    @Arm

    It's a "feature" which hasn't made it in yet. Source:
    https://discussions.agilebits.com/discussion/comment/271892/#Comment_271892

  • Yes indeed! We are planning on adding fingerprint unlock to the keyboard in an upcoming update. :)

  • morandd
    morandd
    Community Member

    The beta for 6 only supports fingerprint via Nexus Imprint. Dare I hope that the full v6 will also support the Samsung Fingerprint API (e.g. for me S5)?

  • peri
    edited February 2016

    @morandd. 1Password requires the new fingerprint APIs introduced in Android Marshmallow. Unfortunately, it doesn't look as though Samsung is supporting these APIs at the moment. :(

    I'll forward your feedback regarding fingerprint unlock for devices without Nexus imprint to the team. :)

    ref: OPA-758

  • mariozaizar
    mariozaizar
    Community Member

    Just waiting on this feature in order to buy a nexus 5x. I can't work/live without 1password! :(

  • AGAlumB
    AGAlumB
    1Password Alumni

    @mariozaizar: Indeed! It's currently in beta, and you're more than welcome to participate. We're looking forward to getting it out to everyone! :pirate:

  • bdbplatano
    bdbplatano
    Community Member

    How does one leave the Beta? Simply uninstall?

  • AGAlumB
    AGAlumB
    1Password Alumni

    @mariozaizar: ;)

    @bdbplatano: Sorry to leave you hanging! As you can imagine, there's a lot going on right now. :lol:

    To return to the stable version, just visit our beta page and click "Leave the program":

    https://play.google.com/apps/testing/com.agilebits.onepassword?authuser=1

    Since Nexus Imprint support is now a reality for 1Password 6 / Android 6 users, I'll close this discussion. But don't hesitate to start a new one if you have any other questions or feedback. We love hearing from you! :chuffed:

This discussion has been closed.