private links not working correctly outside of the browser

I confirm both issues
- on iOS, if 1Password is previously ✱not✱ opened (or locked), then click on a private link would open 1Password, without taking you to the item referenced on the link. You'd have to go back to wherever the link is, click on it again, and only then 1Password would display the item.

- on macOS, it just doesn't work: even if 1Password is opened and unlocked, clicking on a private link just bring back 1Password application in the foreground, but that's it.

These are not critical bugs, but it's annoying.

@1P_DaveThis bug was reported almost a year ago and is STILL not fixed?

@jtreitz, @tavril, @james_w 

The issues remain open in our developer's backlog and I've added your reports to the internal tracking items open for the issues. I'm sorry for the continued inconvenience. 

-Dave

Guys 2 years and no fix? Not sure how this thread is marked as solved when there is no solution or even workaround? To be clear this affects any OS/Device running 1Password 8 and has been an issue since the introduction of 1Password 8. It's a pretty simple bug that has some pretty severe impacts depending on the workflow. Please give us more than this has been passed onto the devs because it's been 2 years and nothing has changed. Keenly await your reply. 

The "Copy Private Link" button will create a link, but that link does absolutely nothing useful. 
This has been a complained about issue for a couple years now, no resolution, no priority.

I have 1P for Business, Family, and Personal. All of them extensively use "use private links" in documentation, or "where is that credential" requests. All of that is broken. 

Other people have complained that "this isn't critical, just annoying". No, it's critical for the ongoing utility of 1Password in these environments. Teams rely on being able to reference a specific secret directly. I am having to type out "go to the XXX vault, sort by most recent, it has YYYYYY in the title/tags you can search". I sound like a chump, and critical "do this in case things are going bad" runbook documents that were written when private links worked (or under the assumption that it was a brief bug) now need to be re-written with instructions on how to find that secret. 

op:// reference values are not clickable by a human end user, and while i love them for automations, it shouldn't be an either-or thing. 

The expectation is and should be: 
- copy private link button exists
- it generate a link that will only resolve if you have secret access
- someone with secret access clicks that link, and is taken to that secret (in every native application)
- someone without secret access clicks that link and is rejected or confronted with a login screen (whatever is appropriate) 

The behavior is: 
- copy private link button exists
- that link brings the 1Password application to the foreground
- no deep link between the URL (that goes to a specific secret) and that secret
- no vault change, no going to that specific value. 
- cry that my push for 1Password being the "single pane of glass for humans to interact with secrets" was undermined by 1Password acting like Microsoft (derogatory). 

private links not working correctly outside of the browser | 1Password Community

Most users are, per your recommendations, running the 1Password desktop applications on macOS/windows. Though i've heard "the link isn't working" from iOS, android, and web users as well. 

The fact that we can't deeplink from our internal pages like:

onepassword://{our-organization}.1password.com/vaults/{vault-id-number}

but we can via:

https://{our-organization}.1password.com/vaults/{vault-id-number}

Is a bit infuriating.