New Item (Category Password) does not store password [Confirmed, will fix soon]

MichaelKaras
MichaelKaras
Community Member
edited April 2023 in 1Password 7 for Windows

If I add a new Password-item, then password is not stored in the vault. It is always visible in the beta-app, but not in iOS-App. Notes in this category get populated correct.
Adding a Login-Item works fine.

Password-Beta: 2016.6.510d

regards Michael


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • Which version of 1Password for iOS are you using?
    I just tried to reproduce this but it worked as expected for me.

  • MichaelKaras
    MichaelKaras
    Community Member

    ios 9.2.3
    1password 6.4.1
    iphone 6

    pc: windows 10

  • mohamedosman
    mohamedosman
    1Password Alumni

    If I add a new Password-item, then password is not stored in the vault. It is always visible in the beta-app, but not in iOS-App.

    @MichaelKaras, could you explain exactly what you mean by then password is not stored in the vault? I want to make sure I fully understand what you're seeing so that I know exactly what to fix.

  • MichaelKaras
    MichaelKaras
    Community Member

    Hi

    seems difficult to explain ...
    starting situation: Family Account wiith differents vaults (personal, shared and some others).
    I add a new password-item in the Windows-Beta-App and save it. If I leave the App and start again, I can see the item and also the entered password. If I open the app on the iPhone I can see the newly created password-item, but the field for the password is empty. If I change notes field in Windows, I can see this changes also on the iPhone. Adding a Login-Item works fine, means I can see all fields filled on Windows-Beta and on iPhone.
    Now clear what I mean?

    Michael

  • MikeT
    edited June 2016

    Hi @MichaelKaras,

    This is a confirmed bug in the Windows apps. The way we're saving the password field in the Password item isn't being read in other 1Password apps. We're investigating for a proper solution to ensure this doesn't happen again and that all 1Password apps are consistent with their template data.

    For now, I would recommend creating a new Password items on 1Password.com instead until we fix this. For existing items, copy the current password from the Windows app and save it in the 1Password.com web app.

    ref: #199

  • MichaelKaras
    MichaelKaras
    Community Member

    Hi @MikeT

    thanks for update. I have already done the bypass by entering it in the other apps.
    Will wait for fix and then do the test again. From outside it is a bit difficult to understand why the same object (password) is handeld different in Login-Item and Password-Item

    regards Mike

  • Hi @MichaelKaras,

    From outside it is a bit difficult to understand why the same object (password) is handeld different in Login-Item and Password-Item

    We use a flexible JSON structure to store your items in but there is no strict requirement for the field names since we lets you create custom sections and fields as well, meaning you can create any number of additional password fields if you want to the same item.

    So, the web apps and other 1Password apps are expecting a specific field name to show up in the main section but we've named it differently or stored it in a separate section of the raw JSON. We can either adjust the other apps to fix this or we can add additional rules to our apps to be consistent with how it is naming its fields by default.

    Your passwords are still there in the Password items, it's just that the other apps aren't looking for it to display it in the UI.

This discussion has been closed.