1Password 6 - iPad also has a Notes editing glitch

abernathy
abernathy
Community Member
in iOS

Different issue than the "2-line" iPhone editing problem. On my iPad if I edit a longish note, the part I'm editing scrolls up out of view and I can't scroll back down far enough to see it. I CAN edit it, but I'm doing it blind.

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

Comments

  • MrRooni
    MrRooni

    Hello @abernathy. Thanks for taking the time to write in here. We are aware of this problem with secure notes on iPad and we are working on a fix.

    Let me know if there are other issues that you run into.

  • mosca
    mosca
    Community Member

    I confirm the same problem with editing of the Note field in IOS 9 and IPhone 5 as well.
    As the Note field is an important one and frequently used in this app I suggest to test the new release of the app better than you use to.
    This kind of bug of a new release isn't acceptable. It's the second time that it's happens.

  • MikeT
    MikeT

    Hi @mosca,

    It's a UI issue affecting all devices, we will get it fixed.

    We do apologize that we didn't see the UI issue early and for the second time but it's high on our list to fix soon.

  • mosca
    mosca
    Community Member

    Hi MikeT,
    We're still waiting for release with the UI bug fixed.
    How much longer do we have to wait?
    It has been almost half a month since my first post. Don't you think it has been too long for a bug that prevents from note field editing?

    Regards
    Mosca

  • Ben
    Ben

    Hi Mosca ( @mosca ),

    I understand the frustration caused by this bug. Unfortunately we cannot share any sort of an ETA (on any feature requests / bug fixes). What I can say is that because this is a regression and that it affects all 1Password users it is very high on our priorities list. That doesn't change the fact that when a bug is reported we have to:

    1) Confirm / reproduce the issue
    2) Free up development resources to work on finding the source of the issue
    3) Find the code that is causing the issue
    4) Write code to fix the problem, without creating other problems
    5) Review and test the proposed fix internally
    6) Push an update to our external beta testers for further testing
    7) Receive enough feedback that we're confident that not only have we fixed the reported issue but that we haven't caused any other issues
    8) Push an update to Apple
    9) Wait in Apple's review queue
    10) Publish the update to the App Store

    All of these steps take time, and most of them are essential (cannot be skipped). Some are outside of our control. I don't say this to sidestep the issue -- as I mentioned it is definitely one of our top priorities, but to give some explanation for the delay you experience between updates. The process frankly cannot happen overnight.

    I know none of this gets notes working properly for you but I hope it provides some insight into the process. We're not simply sitting on our hands. :)

    Thanks!

    Ben

This discussion has been closed.