Can't unlock 1Password on iPhone 6 if has been backgrounded

antipole
antipole
Community Member
edited December 2014 in iOS

Suddenly seeing a new problem - cannot see any other reports.

I have iPassword set to

  • lock on exit
  • auto-lock after 5 minutes
  • use Touch ID
  • Background App Refresh

I am finding that if I leave the app by switching to another, when I return to 1Password (even after a few seconds) it shows the keyhole 1/3rd down the screen, but I have no way of unlocking it. TouchID does not work and tapping on the keyhole does not allow me to enter my master password.

Only way out is to kill the app and re-launch, whereupon all is well.

This problem has only existed recently. Anyone else?

Tony

  • iPhone 6
  • iOS 8.1.1
  • 1Password 5.1.2

Comments

  • Winnie
    Winnie
    1Password Alumni

    Hi @antipole‌

    I am terribly sorry for your troubles. This should not happen. As I haven't seen this happening myself I would be very eager to see your Diagnostic Report. I hope that unveils more details why this is happening.

    Here is how to send us your Diagnostics Report from your iOS device:
    https://guides.agilebits.com/kb/1password4/en/topic/diagnostics-report#ios4

    Then attach the entire file to an email to us: 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.

    A short note here once you've sent the Report in will help us to keep an eye out for it. :simple_smile:

    Once we see the report we should be able to better assist you. Thanks in advance!

  • antipole
    antipole
    Community Member

    Hi... problem seems to have gone away. Not sure why, but I have updated to latest iOS and, of course, restarted during that process. Anyhow, all is well now. Thanks for your concern.

  • Drew_AG
    Drew_AG
    1Password Alumni

    Hi @antipole,

    I'm very happy to hear it's working! It sounds like it might have been an iOS-related issue that was fixed in the update, but I don't know for sure. The important thing is that it works correctly for you now. :smiley:

    If you need anything else, please let us know!

This discussion has been closed.