This issue was brought up in another thread a few days ago. Luckily, there's a fix on the way. In the meantime, as mentioned in that thread, you can disable integration to stop this from happening.
Didn't see that post on reddit but I saw a post on the forums a few months ago describing the same issue, thanks for clarifying. At least it's a known problem not just something specific to me as I'm sure that would be a pain to fix. The workaround in the post you linked has worked but obviously not an ideal solution. Is there a timeframe for the update which rectifies this issue?
Unfortunately not. Testing isn't something that I'm involved in personally, and even beyond that, promising a date for a yet-to-be-released version of 1Password would be difficult without knowing the roadblocks that may prevent that release.
With that said, from what I can see in that other thread, I can't imagine that it'll be that long of a wait.
No worries then, I will try turning the feature back on when the next update releases but other than that, thank you for the clarification and the workaround, all seems a-ok for now
I have updated the 1Password for Safari and reenabled it after I saw the update notes saying this issue has been fixed however it is still occurring with the same frequency
Have you updated 1Password for Mac, as well? There’s been a new release since this post was made. If so, I’d suggest writing in to [email protected] for some diagnosis on this issue. We can do a deeper dive that way.
This issue was brought up in another thread a few days ago. Luckily, there's a fix on the way. In the meantime, as mentioned in that thread, you can disable integration to stop this from happening.
Didn't see that post on reddit but I saw a post on the forums a few months ago describing the same issue, thanks for clarifying. At least it's a known problem not just something specific to me as I'm sure that would be a pain to fix. The workaround in the post you linked has worked but obviously not an ideal solution. Is there a timeframe for the update which rectifies this issue?
Thanks
Unfortunately not. Testing isn't something that I'm involved in personally, and even beyond that, promising a date for a yet-to-be-released version of 1Password would be difficult without knowing the roadblocks that may prevent that release.
With that said, from what I can see in that other thread, I can't imagine that it'll be that long of a wait.
No worries then, I will try turning the feature back on when the next update releases but other than that, thank you for the clarification and the workaround, all seems a-ok for now
Hi there
I have updated the 1Password for Safari and reenabled it after I saw the update notes saying this issue has been fixed however it is still occurring with the same frequency
Have you updated 1Password for Mac, as well? There’s been a new release since this post was made. If so, I’d suggest writing in to [email protected] for some diagnosis on this issue. We can do a deeper dive that way.