private links not working correctly outside of the browser

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

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

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.

I'm having the same issue. I copy the private link into Bear notes. Clicking the link focuses 1password but doesn't load the item. Only works when pasting the url in the browser and it opens 1password.

My workaround is to manually replace https://start.1password.com/open/i? with onepassword://open/i? in the private link. Then it just opens in the app like it should.

ntents

The issue still open in our developer's backlog to get fixed in the future, I'm sorry for the inconvenience.

Regarding iOS, I'm not able to reproduce the issue. Can you tell me the following:

1. Are you pasting the private link directly into the browser iOS? If so then which browser?
2. If you're not pasting the link into a browser then are you tapping on the link from inside of another app? If so then which app? Can you reproduce the issue with Apple Notes?
3. On the first attempt, what does 1Password for iOS open to after you unlock it? A random item? Or a different screen?

-Dave

ref: dev/core/core#24708
ref: dev/core/core#18260

I check to see if this is fixed with every new MacOS release, and it's still not. Also, what DaBarkle said about having to click on it twice for iOS (the first time to unlock 1Password, the second to get to the item) is a problem I'm experiencing. I don't know how long that's been happening on iOS.

This is something that used to work without fail on MacOS, and it's a big problem, at least for me.

lpuerto

I don't have an ETA that I can share but I've let the team know that this is affecting your workflow as well.

PS/ I, in particular, use Things as a task manager, and it would be great that I dan interact with it also.

Just to clarify, are you putting the private link into Things and then clicking on it from inside of Things? I want to make sure that I communicate your use case accurately to the team. 🙂

-Dave

ref: dev/core/core#30391

I'm experiencing the same issue and I can tell you that on iOS works.

do you have any ETA to fix this? I think it's not a killer feature, but it's really nice si you need to link with task related to items on 1password.

Thanks!

PS/ I, in particular, use Things as a task manager, and it would be great that I dan interact with it also.

DaBarkle

I'm sorry for the impact that the issue is causing. The bug being discussed in this thread should only affect 1Password on macOS, not iOS. Can you confirm that you're seeing the issue on iOS as well?

If you are seeing the issue on iOS then can you tell me the version of both 1Password and iOS you're using? And can you post reproduction steps that I can follow to reproduce the issue on my own device?

-Dave

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?