Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
1P_justin
1Password Team
1Password TeamBeta Release: New MSIX Installer for 1Password for Windows
Hello 1Password Community!
We are excited to announce the beta launch of the MSIX installer for 1Password for Windows. The MSIX installer combines the benefits of our existing EXE and MSI installer...
Not sure what's the current state of this issue, but I just stumbled upon this exact issue. I wasn't able to get the Chrome extension to connect to the app as well as using the recently announced Passkey feature for Windows.
I got similar logs to the ones above, which reminded me that I recently moved (possibly by uninstalling and reinstalling) the app from drive C: to D:. I tried moving the app back to drive C:, and this issue magically disappeared.
In case if you still need any help, I'm happy to provide additional debugging information. Please let me know.
It looks like the version of the installed msix package is part of the installation path.
The following ends up in my .gitconfig when configuring commit signing:
[gpg "ssh"]
program = C:\\Program Files\\WindowsApps\\Agilebits.1Password_8.10.78.39_x64__gh85et3mt782r\\1Password\\app\\8\\op-ssh-sign.exe
Basically this means that you'd have to reconfigure commit signing after every update, which is far from ideal.
Note that there will be a linked executable in the userprofile. i.e. %localappdata%\Microsoft\WindowsApps\op-ssh-sign.exe. It will probably be on the path by default. The automatic process of editing the .gitconfig file should act accordingly.
- 1P_justin
Appreciate you sharing this with us. Will have our developers take a closer look!
