macOS 26 beta 2 , browser extension can not connect to Enpass desktop

[qtwrk]

Hi, 

 

I know it might be silly to seek support on beta OS ,  but this really annoys , so kind of want to try it anyway 

tried uninstall reinstall ,  both  downloaded version and app store version , no good 

 

firefox, chrome , safari ,  all no good  

pretty much all the guide I found online didn't work out ,    disable/re-enable browser extension  ....etc 

 

it looks like the desktop app never receives the linking request from browser extension though.

any help is greatly appreciated.

 

best regards,

 

[Syd]

ditto - macos 26 beta 2 has broken enpass on macOS.

(just saw this post after posting mine - sorry for duplicate)

Edited June 24 by Syd

[Tarun Singh Rawat]

Our technical team is informed and is currently investigating the issue. We’ll update you as soon as we receive an update from them.


#SI-4410

[qtwrk]

On 6/25/2025 at 11:33 AM, Tarun Singh Rawat said:

Our technical team is informed and is currently investigating the issue. We’ll update you as soon as we receive an update from them.


#SI-4410

thank you 

I just pick up my retired Intel 2019 Macbook ,  also upgraded to macOS 26 beta 2 ,  all clean OS ,   just to rule out if any other software I have installed on my main laptop that may interfere ,  but seems it's not , clean OS doesn't work on Safari/Chrome either.

[tom99]

Hi,

In relation to this problem, it also seems to fit that in the MacOS settings there is also no option to select Enpass as the password management program (see attached Screenshot (sorry German))

Maybe this is the root cause?

Tom

[qtwrk]

Just now, tom99 said:

Hi,

In relation to this problem, it also seems to fit that in the MacOS settings there is also no option to select Enpass as the password management program (see attached Screenshot (sorry German))

Maybe this is the root cause?

Tom

 

on my test, at least from extension log ,  it was trying to connect to one port , but from `netstat` command  , the enpass was binding to a different port 

[Syd]

On 6/25/2025 at 7:33 PM, Tarun Singh Rawat said:

Our technical team is informed and is currently investigating the issue. We’ll update you as soon as we receive an update from them.
#SI-4410

Enpass - is there an update on this? Do you have a beta that we can try/test out?

[qtwrk]

On 6/25/2025 at 11:33 AM, Tarun Singh Rawat said:

Our technical team is informed and is currently investigating the issue. We’ll update you as soon as we receive an update from them.


#SI-4410

I know it's bad manner to ask , but it's been like 2 weeks already , any update on this ?  

[Tarun Singh Rawat]

We totally understand the follow up. Our technical team still do not have an ETA for this, but we’ll keep you posted as soon as there are any developments. Thanks for understanding! 

[meinname]

It’s the same every year: almost every app works without an update or gets one within a few days after the first macOS beta is released.
Only Enpass isn’t ready even after at least two public betas.
So don’t be surprised if it’s the same this year.

[qtwrk]

1 minute ago, meinname said:

It’s the same every year: almost every app works without an update or gets one within a few days after the first macOS beta is released.
Only Enpass isn’t ready even after at least two public betas.
So don’t be surprised if it’s the same this year.

lol ,  it actually worked on preview 1 , then broken on preview 2 

[Syd]

Just updated to macOS Tahoe Beta 3 and enpass desktop doesn't work with this version either.

Same symptoms and issues as Beta 2.

[meinname]

On 7/4/2025 at 6:04 PM, qtwrk said:

lol ,  it actually worked on preview 1 , then broken on preview 2 

Are you sure?
As far as i know it was already with Developer Beta 1 broken. At least for Chrome and Safari.
At least for new Authentications - Maybe an old one was still valid for you if it still worked on your System at Beta 1
But anyway. Still broken on 3rd Beta
 

Edited 12 hours ago by meinname

[qtwrk]

18 minutes ago, meinname said:

Are you sure?
As far as i know it was already with Developer Beta 1 broken. At least for Chrome and Safari.
At least for new Authentications - Maybe an old one was still valid for you if it still worked on your System at Beta 1
But anyway. Still broken on 3rd Beta
 

yeah ... I am certain it was working on beta 1 ,  start to break on beta 2 and continue to break on b3...