Egregius Posted June 13 Report Share Posted June 13 Since I've updated my Macbook to Mac OS 15 Sequoia developer beta 1 the Enpass extension doesn't work anymore in both Safari and Chrome. Link to comment Share on other sites More sharing options...
Amandeep Kumar Posted June 17 Report Share Posted June 17 I understand that you've encountered some challenges, and committed to resolving them for you. If you're currently experiencing the reported issue, please ensure the following steps on your PC: Verify that your browser does not have a verification code signature by re-downloading it from its legitimate source and trying again. Ensure that you are not using any VPN connection. Confirm that the Enpass application is running on your PC. Make sure the latest version of Enpass is installed on your PC. Check if the browser has been blocked from making connections to the Enpass app. To unblock the browser, open Enpass, go to Settings > Browser > Browser Authentication, and click "Review Browser." Find your browser and click "Remove." Link to comment Share on other sites More sharing options...
Egregius Posted June 17 Author Report Share Posted June 17 I already did all these steps before posting. Did them again but the problem remains. Link to comment Share on other sites More sharing options...
meinname Posted June 19 Report Share Posted June 19 (edited) On 6/17/2024 at 2:13 PM, Amandeep Kumar said: I understand that you've encountered some challenges, and committed to resolving them for you. If you're currently experiencing the reported issue, please ensure the following steps on your PC: Verify that your browser does not have a verification code signature by re-downloading it from its legitimate source and trying again. Ensure that you are not using any VPN connection. Confirm that the Enpass application is running on your PC. Make sure the latest version of Enpass is installed on your PC. Check if the browser has been blocked from making connections to the Enpass app. To unblock the browser, open Enpass, go to Settings > Browser > Browser Authentication, and click "Review Browser." Find your browser and click "Remove." In case you haven't heard it by now. This problem is not a problem of a single user. This was noticed by many users on reddit and other forums. That's why Enpass extensions are on several lists with incompatible or non-working with Sequoia like here on MacRumors: https://forums.macrumors.com/threads/macos-sequoia-working-and-non-working-apps.2428673/ Edited June 19 by meinname Link to comment Share on other sites More sharing options...
Egregius Posted June 20 Author Report Share Posted June 20 And that's why I posted here. The developers aren't supposed to follow all forums etc. Now they know it and they can start looking for fixing it before the release of Sequoia. If a beta comes available to test I will be more than happy to test it. Ones you are used to the ease of use with Enpass you miss it a lot when it's gone! Link to comment Share on other sites More sharing options...
Amandeep Kumar Posted June 20 Report Share Posted June 20 I've reported this issue to the Enpass technical team. They are currently investigating it, and I will reach out to you with updates as soon as I receive them. #SI-3857 2 Link to comment Share on other sites More sharing options...
PixelNik Posted June 23 Report Share Posted June 23 On 6/20/2024 at 11:24 AM, Amandeep Kumar said: I've reported this issue to the Enpass technical team. They are currently investigating it, and I will reach out to you with updates as soon as I receive them. Thank you very much, as I also have this problem, I am grateful to you for taking the initiative and hopefully we can get a solution to the problem quickly. Link to comment Share on other sites More sharing options...
Kevbert Posted June 25 Report Share Posted June 25 Problem with Beta 2 still persists. Reinstallation of Enpass and browser extensions unsuccessful. Link to comment Share on other sites More sharing options...
Egregius Posted June 25 Author Report Share Posted June 25 Indeed, same here. Link to comment Share on other sites More sharing options...
Amandeep Kumar Posted June 26 Report Share Posted June 26 Our technical team has acknowledged the issue and is actively working on a solution. Fixing this bug may take some time, and the resolution will be included in the upcoming updates of the application. 1 Link to comment Share on other sites More sharing options...
Kevbert Posted July 4 Report Share Posted July 4 Any news on this? Is there a roadmap when any beta in TestFlight will be available? Link to comment Share on other sites More sharing options...
Amandeep Kumar Posted July 9 Report Share Posted July 9 Please DM me your email address so that I can add you to our TestFlight. This way, you will be notified whenever we release a beta version. Link to comment Share on other sites More sharing options...
Egregius Posted July 9 Author Report Share Posted July 9 You're not gonna publish on https://www.enpass.io/beta/? Link to comment Share on other sites More sharing options...
Kevbert Posted July 10 Report Share Posted July 10 22 hours ago, Amandeep Kumar said: Please DM me your email address so that I can add you to our TestFlight. This way, you will be notified whenever we release a beta version. Thanks, being already part of beta in TestFlight. But latest version is 6.11.0 (1676) with the bug still active. Link to comment Share on other sites More sharing options...
Amandeep Kumar Posted July 16 Report Share Posted July 16 I've already escalated the matter to our technical team for investigation, and they are currently working on resolving it. I'll keep you updated as it progresses. Link to comment Share on other sites More sharing options...
longtom Posted July 18 Report Share Posted July 18 Yes, please do it faster. I am now using the password-app of macOS in the meantime. Also checking other Managers. So, the chance is high to loose customers to other Password Managers... Link to comment Share on other sites More sharing options...
Kevbert Posted July 19 Report Share Posted July 19 21 hours ago, longtom said: Yes, please do it faster. I am now using the password-app of macOS in the meantime. Also checking other Managers. So, the chance is high to loose customers to other Password Managers... Calm down and keep in mind that we use a highly beta version. The developers need some time to implement every new code. Hardly any customers will switch as a result. 1 Link to comment Share on other sites More sharing options...
meinname Posted July 19 Report Share Posted July 19 Highly beta is not correct anymore since public beta is out. This is used by a lot of users. I would compare it to say: Firefox is highly beta. Only Firefox ESR is fully supported. On hardly any customer will switch: i am also really thinking about it, if a fix takes another 1 or 2 or more weeks. (and i basically have Pro as a long time user for free) The situation is similar in a german community that I follow. In a survey, 28 out of 94 Enpass users have already switched or are about to do so. 1 Link to comment Share on other sites More sharing options...
longtom Posted July 20 Report Share Posted July 20 I switched now to Strongbox, goodbye Enpass. 1 Link to comment Share on other sites More sharing options...
Kevbert Posted July 21 Report Share Posted July 21 On 7/19/2024 at 3:40 PM, meinname said: Highly beta is not correct anymore since public beta is out. The word "public beta" has even "beta" in it, so it is still a beta. I think in such security relevant features as a password manager, it could take longer to work efficiently . 1 1 Link to comment Share on other sites More sharing options...
meinname Posted July 24 Report Share Posted July 24 (edited) Nevertheless, the “highly” was wrong. And yes. It is a beta. But no matter how you look at it, since Apple has been releasing public betas, a large proportion of private customers have also been using these betas. It is therefore strongly recommended that software manufacturers pay attention to problems with existing features during the first two developer betas and fix them with beta 3 at the latest. As this beta will then become the public beta. And the subsequent betas are then there to evaluate new things. Of course, you can be so snooty that you think it's only necessary to have it fixed until the final version, or some manufacturers didn't even start until then. But many of those who thought so no longer exist. In the end, it's what the customers want and think that counts, not “that's how it should be” Edited July 24 by meinname 1 Link to comment Share on other sites More sharing options...
longtom Posted July 24 Report Share Posted July 24 For me it is also a sign how important the support (of any company) is for the customers. Anyway it was a good choice for me to change. Link to comment Share on other sites More sharing options...
sunny-ww Posted July 29 Report Share Posted July 29 When can we expect an update? Some of the major, relevant competitors have already been active and work with the current public beta without any problems. I would hate to switch, but I am somewhat surprised that there has been no reaction at all. 1 Link to comment Share on other sites More sharing options...
Kevbert Posted July 29 Report Share Posted July 29 I have also already prepared a self-hosted Bitwarden instance. The waiting and sitting out is getting annoying. 1 Link to comment Share on other sites More sharing options...
Amandeep Kumar Posted July 30 Report Share Posted July 30 I am glad to inform you that, we have created a fix for the issue you were facing, which will be included in the upcoming update. We appreciate your patience in the meantime. Link to comment Share on other sites More sharing options...
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