One-Time Password for Dropbox not saving

bramhubbell
bramhubbell
Community Member

Hi,

I set up 1Password to provide me with one-time passwords for Dropbox. For some reason, the setting won't save. All my other accounts work, but not Dropbox. Any ideas?

Comments

  • Winnie
    Winnie
    1Password Alumni

    Hi @bramhubbell,

    sorry for the troubles you are having. You might be running into a bug there. Can you explain which steps you are taking to save your Dropbox one-time password?
    Are you scanning the QR code or are you typing the secret?

  • bramhubbell
    bramhubbell
    Community Member

    Hi @Winnie,

    I'm using the camera on my iphone to scan the QR code. I also tried scanning the QR code on my iPad. Each time the OTP is available right after I click save, but as soon as I leave that login and come back, the OTP field is gone.

    Thanks.

  • liamget
    liamget
    Community Member

    Hi,

    I am having the same issue. The OTP works for all the others I've set up (Google/Gmail, Hover) but the Dropbox one keeps getting lost for some reason.

    Thanks.

  • Hi @bramhubbell ,

    There was an issue in 5.2 with saving some OPTs, and a fix went into 5.2.1 that came out recently - are you running the this version? You can check by going to Settings. It is listed right over the Advanced button.

  • bramhubbell
    bramhubbell
    Community Member

    Hi @hayesk
    I have 5.2.1. No OTP.

  • Winnie
    Winnie
    1Password Alumni

    Sorry @bramhubbell for that - it seems like our fix indeed didn't go into 5.2.1. As a work-around you could edit one-time password field title after you scanned the QR code. With that saving the one-time password should be possible.

    Let me know if that works for you.

  • liamget
    liamget
    Community Member

    Weirdly, my OTP for Dropbox has persisted and has been there for about a week now... I'm on 5.2.1.

  • bramhubbell
    bramhubbell
    Community Member

    @Winnie
    I renamed the field "special code" and it saved fine. Thanks.

  • Thanks for the update, @bramhubbell. Glad to hear that has resolved it for you.

This discussion has been closed.