Wrong content is appearing in search results

Hello @TomWolsky! 👋

I'm sorry that search isn't opening the correct item. To help me better understand the situation, and attempt to reproduce the issue on my end, I'd like to ask you to take a screen recording of what you're seeing:

• How to record the screen on your Mac - Apple Support (CA)

Send an email with a link to this thread to support+forum@1Password.com. After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to locate your message send you a secure upload link for the screen recording.

-Dave

Thanks Dave. Unfortunately, or maybe fortunately, the problem is not reproducing. I remember seeing this a couple of years ago I think. These are both secure notes. The contents swap but the header name remains correct for the searched item.

@TomWolsky

I'm glad that you're not currently seeing the issue, I can't reproduce it on my end either. If you do encounter the issue again in the future then let me know and try to take a screen recording.

-Dave

Will do. Thanks Dave.

The team will keep an eye out if you do encounter the issue again. 🙂

-Dave

Has anyone else seen this. I had it again about a ago, but I couldn't stop to work on the problem.

@TomWolsky

I'm sorry that you saw the issue again. The team has identified an issue that sounds like what you might have experienced and a fix is included in the latest beta version of 1Password:

We’ve fixed an issue where you’d see unrelated notes when you opened an item from a search result.

If you're able to, let me know if you can still reproduce the issue when using the latest beta version. Once testing is complete, the fix will be included in the stable version as soon as possible.

-Dave

ref: dev/core/core#29883

Thanks Dave. I've been trying it over the last couple of days, and damn, I can't break it. It seems to be working fine.

@TomWolsky

I'm happy that your item content is displaying properly now. 🙂

-Dave