"Welcome to 1Password" tab, over and over

dlaidlaw
dlaidlaw
Community Member
edited January 16 in 1Password in the Browser

This is basically the same issue as https://1password.community/discussion/149391/welcome-to-1password-keeps-appearing-in-my-browerq but that one is closed.

1Password for Mac 8.10.56 (81056028)
macOS Sequoia Version 15.2 (24C101)
1Password for Safari extension: 8.10.56.28

This is a new machine, with a fresh install of 1Password.

At least hourly, two tabs pop into Safari. The first one is:

And the second one is:

I have gone through the process to get the extension ready. Yet this keeps happening. How do I get it to stop?


1Password Version: 8.10.56
Extension Version: 8.10.56.28
OS Version: macOS 15.2
Browser: Safari

Comments

  • Hello, @dlaidlaw. Thank you for reaching out.

    I'm sorry about the trouble you're encountering. Do you manually clear Safari's history or use third-party programs or extensions to clear the history in the browser?

    -Evon

  • dlaidlaw
    dlaidlaw
    Community Member
    edited January 17

    No, I may occasionally clear history, but this is a brand new machine, and I have not done so as yet. The only extension installed in Safari is the 1Password extension, so nothing else should be clearing history.

  • @dlaidlaw

    Could you please send us a diagnostics report to support+forum@1Password.com? With your email, please include the following:

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here, and I will be able to locate your message and ensure it has reached the right place. Thank you!

    -Evon

  • sandinak
    sandinak
    Community Member

    I am getting this problem as well... on both Firefox on my Mac .. and on my iPhone. Very frustrating.

  • Hello, @sandinak.

    May I ask if you're running Safari 18.3? If so, previous iOS/macOS 18.3 versions had issues where the browser extension storage used by 1Password for Safari would be cleared unexpectedly. This issue should now be resolved with beta 3.

    Can you please share additional details when this problem occurs in Firefox?

    -Evon