Browser extension never opens, just hangs

safercracker823456
safercracker823456
Community Member
edited June 25 in 1Password in the Browser

It doesn't open, it just hangs, for about two weeks now.


1Password Version: 8.10.35
Extension Version: 2.24.2
OS Version: Windows 10 Pro
Browser: Chrome/Firefox

Comments

  • typerlc
    typerlc
    Community Member

    Yes. I thought it was just me. Same problem here.

    1Password Version: 1Password for Mac 8.10.36 (81036010, on BETA channel)
    Extension Version: 2.25.1
    OS Version: Mac OS Monterey 12.7.5 (21H1222)
    Browser: Chrome Version 128.0.6535.2 (Official Build) dev (x86_64)

    This started a few weeks back. I don't have anything more specific to add. In between then and now, there has been at least 1 update in 1password and 1 update of the browser.

    When the problem happens, restarting 1password and browser tends to fix it. But some time later, it will happen again. Not sure what is the trigger.

  • Hello @safercracker823456, @typerlc! Thank you for writing in. I am sorry about the problem you are experiencing with the 1Password extension.

    So that I can take a closer look at the issue you are experiencing, I would like to request that you send us some information to support+forum@1Password.com.

    With your email, please include the following:

    1. First, please recreate the issue you are experiencing.
    2. Then save a console log for 1Password in the browser using the steps here -> Save a console log for 1Password in your browser.
    3. Attach the file to your email.

    After emailing in, you will 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 and make sure it’s gotten to the right place.

    I look forward to assisting both of you. 🙂

    -Evon

  • typerlc
    typerlc
    Community Member

    Thanks for your response Evon. Since I posted my report, the browser has auto-updated to Chrome Version 128.0.6559.0 (Official Build) dev (x86_64), and after restarting the browser, I haven't experienced the problem again. Of course, it may still be there, just not triggered yet. I'll send a support email if the problem returns.

  • You're very welcome @typerlc. I'm glad to hear that resolved the issue.

    Sounds good! Let me know if there's anything else I can assist you with. 🙂

    -Evon