I have items that do not show the password field on IOS. Is it because I created a custom field?

mrgjlgx
mrgjlgx
Community Member
in iOS

I created some unique entries in 1Password in Windows that contain a custom section. In that custom section I defined another field that starts with the word "Password", and then added some additional characters. I then sync from Windows to IOS (the IOS copy of 1Password is empty before the sync). After the sync, on IOS, those login entries (and only those login entries) do NOT show the standard "Password" field. Instead, it only shows the custom field that I added that starts with "Password" (I have a reason to do this). Other custom fields appear just fine. My suspicion is that 1P is somehow parsing for fields that start with "Password" and it only displays the last one found. I suppose I could rename my fields, but this seems like a bug. Looking to see if anyone else has encountered this.

1Password Version: IOS 5.4.3
Extension Version: Not Provided
OS Version: Windows 4.6.0.585
Sync Type: WiFi
Referrer: forum-search:password field not shown

Comments

  • Ben
    Ben

    Hi @mrgjlgx,

    Sorry to hear about the trouble. Have you purchased the Pro features on iOS? You'll only be able to view/edit custom sections after purchasing the Pro features.

    Thanks.

    Ben

  • mrgjlgx
    mrgjlgx
    Community Member

    Yes, I've had the Pro features for IOS since day one. I can see the other custom fields in this entry and other entries.

  • Megan
    Megan
    1Password Alumni

    Hi @mrgjlgx,

    Let's test your theory. If you rename that 'Password' field to something else, does it sync properly?

  • mrgjlgx
    mrgjlgx
    Community Member
    edited August 2015

    Renaming the custom field didn't work. In this entry I have 4 custom fields on my PC (and the Password field). After transferring to IOS via WiFi - all 4 custom fields are shown. But not the Password field! (And all of those custom entries are part of the same custom section.) I am noticing more about this - other 1Password entries that I have with custom fields show the password, but on IOS it puts the custom items into a section called "CONFLICTS" - but actually shows the proper information for each of those custom fields. In another entry, it properly shows the password and the custom fields - and puts those custom fields into a section named as I had specified in windows. So it seems to be inconsistent. But my suspicion now is that the non-display-of-the-Password-field has to with the length of the entry in the Password field (what I have there is very short - on purpose - it's not really a password).

    ref: HTM-13716-527

  • Megan
    Megan
    1Password Alumni
    edited August 2015

    Hi @mrgjlgx,

    Thanks for getting back to us with that additional information! Those conflict fields will show up whenever 1Password can't determine which edits to an entry should be given priority. For example: if you edit your entry on your PC, and then edit that same entry on iOS before syncing, the app might not be able to tell which of those edits are meant to be kept. In that case, 1Password is careful to ensure that it does not overwrite information that you want to keep.

    In any case, it does sound like something odd is going on. Let's take a closer look at your system.

    I'd like to ask you to create some Diagnostics Reports, one from each of your devices.

    —iOS—
    https://support.1password.com/diagnostics/ios.html

    —Windows—
    https://support.1password.com/diagnostics/win.html

    Attach the Diagnostics Report to an email message addressed to support+forum@agilebits.com.

    Please do not post your Diagnostics Report in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your Diagnostics Report in our inbox.

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here so we can track down the report and ensure that it is dealt with quickly. :)

    Once we see the report we should be able to better assist you. Thanks very much!

    ref: HTM-13716-527

  • mrgjlgx
    mrgjlgx
    Community Member

    It appears that the problem of the hidden password field (the normal 1Password "Password" field, not custom) no longer happens with new login entries that are added from scratch. Somehow this happened to some prior items I put in - perhaps it was a bug that was there when I first entered these items. I can't get around this problem for the existing items - the regular password field still does not show up with very short password entries. Since this bug appears to have been fixed for NEW items, then I will drop the issue. Thanks to Agile Support for following up with me on this.

  • Drew_AG
    Drew_AG
    1Password Alumni

    Hi @mrgjlgx,

    Thanks for following up to let us know about all that! It sounds like this was indeed an old bug which apparently has been fixed, if it isn't happening with new items.

    Hopefully you're all set, but if you have more questions or need anything else, just let us know - we're always happy to help! :)

    ref: HTM-13716-527

This discussion has been closed.