Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
private links not working correctly outside of the browser
While clicking on a private link in the browser (or copy pasting the URL into a browser) seems to work fine, when I click on that same link from somewhere else, it does open the 1password app but does not bring me to the correct item.
I tried clicking on the link from several other apps - VSCode, Terminal, Notion and this seemed to be consistent.
I can't be sure if this is a mac-only issue, but I am on a mac.
Hello theozero! 👋
I'm sorry that links to items aren't opening correctly from non-browser apps. I can reproduce the same issue here on my end and I've filed a report with our development team so that they can look into this further.
Hopefully the issue can be fixed in a future update soon. 🙂
-Dave
ref: dev/core/core#30391
18 Replies
1P_Dave Is there any ETA for this bug being fixed? This has been a bug since the introduction of 1Password 8 with no sign of any effort towards a fix. To re-iterate currently private links have to be opened twice on IOS. First opens the 1Password app but does not open the item from the link. Only once the app is unlocked with Face ID or master password and has not timed out to another lock of the app, a second opening of the link then directs to the correct item. This is a simple yet highly impactful bug. This breaks all of our QR codes in our office for sharing common passwords and is a bare minimum functionality offered by all of your competitors. Can we please get some indication of when this will be remediated?
This has been broken for a while. I experience the same thing on MacOS, whereas it seems to work fine in iOS. It worked in MacOS up until recently, because I make use of private links on the Mac all of the time and never noticed a problem until a few weeks ago.
- 1P_Dave
Moderator
Hello theozero! 👋
I'm sorry that links to items aren't opening correctly from non-browser apps. I can reproduce the same issue here on my end and I've filed a report with our development team so that they can look into this further.
Hopefully the issue can be fixed in a future update soon. 🙂
-Dave
ref: dev/core/core#30391
