Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
awholelattelove
4 years agoOccasional Contributor
Archive Confirmation is Relentless
Hey ya'll! Choosing ␡asks for me to confirm archiving an item, which is great, but even choosing "Archive and Don't Ask Again", the confirmation continues appearing. Not the end of the world but felt like a bug worth mentioning!
All the best. :)
1Password Version: 80500108
Extension Version: Not Provided
OS Version: macOS 12.2
10 Replies
- 1P_Ben
1Password Team
Happy to help. 🙂
Ben
- awholelatteloveOccasional Contributor
- 1P_Ben
1Password Team
Thanks for following up mfisher911. I was also able to reproduce this behavior, when using the keyboard shortcut, using that same version. I've filed a note with engineering. 🤞 For what it's worth, if I use the context menu, it doesn't prompt (as expected).
Ben
ref: dev/core/core#9779
- mfisher911Occasional Contributor
The feature where "Archive and Don't Ask Again" doesn't actually suppress future asking is still happening for me. 1Password for Mac 8.6.0 (80600039/NIGHTLY).
- 1P_PeterG
Community Manager
Thanks rctneil and awholelattelove - good news all around! Should this recur, though, feel free to let us know here and we'll look into it for you. 👍
- awholelatteloveOccasional Contributor
- rctneilSuper Contributor
I am now running the newest version as of today but have ONLY just installed it. I have hardly opened the app so can't comment on if it's still occuring in this version. On the previous beta I did experience it.
- rctneilSuper Contributor
I too have experienced this. However, when I went to add this to a bug report comment on here two days later I couldn't replicate it. I haven't tried recently but just wanted to chime in to say I have experienced this and it's very annoying, especially when the button explicitly states "Don't Ask Again".
- 1P_PeterG
Community Manager
Hi awholelattelove, thanks for surfacing this issue for us! While I haven't been able to reproduce it, I'll be taking it to other team members to see if we can re-create the conditions that might trigger this. If you have any additional (non-sensitive) info you'd like to share, we of course welcome it - and we'll do what we can to track this down from our end. Thank you again for bringing it up!