1Password extension on second instance of Chrome working weird

Hey jinux_go, to unlock the extension with Touch ID, the app integration feature has to be working. For the app integration feature to work, both the 1Password app and your browser have to be installed in the /Applications folder. If either the 1Password app or your browser are installed outside of the /Applications folder, our communication protocols won't be able to properly verify the browser's code signature. You'd still be able to use the app and extension, but they will not communicate or connect.

It sounds like one instance of Chrome is installed in /Applications, and Touch ID can be used to unlock the extension from there. That said, it also sounds like the second instance of Chrome is installed in a separate directory, and Touch ID does not work to unlock the extension from there. If that is truly the case, then this would be expected behavior.

I would recommend moving the second instance of Chrome into the /Applications folder if you can. Alternatively, if you do not want to use a separate profile in Chrome, you can use another browser with 1Password. You will be able to unlock the extension in that browser with Touch ID as long as that browser is installed in the /Applications folder.

I hope this helps. If I've misunderstood the situation, please let me know.