Sounds good. Let's continue the conversation via email so we can get the diagnostics Ben and I requested to do any additional account-related investigation if the problem persists, without duplication of effort between multiple channels/people at once.
I have the same issue and it is very annoying. A lot of people in the company have this issue but they just gave up and do not use 1Password on their phone. It is a major blocker for us. Essentially, this issue makes the IPhone app unusable with Duo. If you do not prioritize that with top priority, I suggest updating the documentation about it.
Sorry about this @ibratoev, but thank you for the feedback. I have let our developers know that you are also experiencing this, so hopefully they will have a fix soon
Yes, this is a super-frustrating bug. It used to work but hasn’t worked on my iPhone for a while. I’m running iOS 14.5.1 and 1Password 7.7.5 and Duo won’t work because I have to switch away from 1PW to Duo to authorize. I get other Duo notifications on my Apple Watch, but not the one from 1PW.
I seem to have found a workaround for this.
1.) When you receive “1Password” wants to use “1Password.com” to sign in, you click Continue
2.) On the Duo screen, you click “Send Me a Push”
3.) As long as you have push notifications enabled, you will receive the Duo Mobile Login Request at top of screen. Instead of single clicking (which takes you out of 1Password app and into Duo), click and hold the Push Notification to display an Approve / Deny selection. Click Approve and you will be dropped back onto the 1Password app without the continuous looping.
This has been working successfully for me recently, hope this helps.
Sorry about the frustration @bgreiner. I have let the developers know that you are also encountering this, and hopefully they will have an update soon
Thank you for sharing what is working for you @grumpygraeme69, hopefully other users will find this useful in the meantime while our developers continue to investigate.
Thank you, @grumpygraeme69 — excellent solution!
I know this discussion is old, but I still see this issue. I also seem to be able to authenticate with a code vs a push. Is this going to be fixed? Also if 2fa is active to re-authenticate a device and is canceled the local password respiratory should be locked until 2fa is passed again, otherwise this defeats the purpose.
I understand the frustration, I have let the developers know that you have also encountered this. Hopefully they will be able to come up with a fix in one of the next updates.
This is affecting a number of iPhone users at our company too. I'll suggest the push and hold on notifications to the to see if this helps, it would be preferable if the issue was simply fixed though.
Agreed @MarkS_UK, sorry about the inconvenience and thank you for your patience while our developers look into this.