Mikey2233 Posted May 30, 2020 Report Posted May 30, 2020 I've come across yet another issue in the Mac version of Enpass. I've Reset Enpass and completely deleted it from my system and then reinstalled it from the App Store and still have the same issue. I open one of of the entries in my vault. I click the Copy icon next to the username, password, or website. The "Copied to Clipboard" toast type notification is displayed. I try to paste the result to a browser, notepad, or any other app. Nothing is pasted. I go into Edit mode for the entry. I click the Copy icon next to the password. I try to paste it into a browser field, notepad, etc. Nothing is pasted. I change the password field, so it's viewable and try to select the password I'm unable to drag and select with the mouse or hit CMD-A to select the text in the field. If I try this enough times eventually the fields may copy. But it will likely only happen once. The browser extension works for populating those passwords on websites, but some of mine passwords I have to copy from Enpass directly to paste into another application's sign on screen. At this time it seems I'm left to type the long complex password from my vault each time, since copy doesn't work. Enpass version 6.4.2 (668) MacOS Catalina 10.15.4 Is it possible to get a build from earlier this year that works? These recent releases have just been one headache after another.
Garima Singh Posted June 1, 2020 Report Posted June 1, 2020 Hi @Mikey2233 We are sorry for the inconvenience caused to you. Could you please try to do the same after increasing Clipboard Timing from Enpass security settings if you haven't tried it yet. If the problem persists, please revert to us. Thanks!
Mikey2233 Posted June 5, 2020 Author Report Posted June 5, 2020 I've increased the clipboard timing from 30 seconds to 45 seconds. I'll give that a try. In my issue above I had copied and tried to paste within 5 seconds, so unless there's an issue with the way the app handles the timing it should have worked.
Garima Singh Posted June 5, 2020 Report Posted June 5, 2020 Hey @Mikey2233 Thanks for reporting this issue. I have noted down this issue and notified the QA team to look into it. Will get back to you once we receive any update from the team or in case of any other info is required. Thanks for your cooperation.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now