Forum Discussion

IainMcc's avatar
IainMcc
New Contributor
2 months ago

Sending <NumLockState> messages

I'm working on a web app, and leave my browser pointed at its login page while I'm up to the elbows in the Java code. Or JavaScript, as the case may be.

After a while, I start seeing `Sending <NumLockState to native core <`_string of digits_`>. Duration xxms` messages in the console every few seconds. Each one followed by a message about receiving the numlock state from the native core.

I've traced this down to the 1Password extension.

It is also trying to reach https://my.1password.com/api/v2/overview and getting HTTP401s. And https://my.1password.om/api/v1/session/touch and others.

Can anyone explain WTH is going on? It's also attempting to access wss:// urls.

Is the extension getting into some kind of wacky user-not-clicking-me-omg-gonna-flip-out-now loop?

 

browser extension

2 Replies

  • IainMcc's avatar
    IainMcc
    New Contributor
    2 months ago

    I've noticed no issues with 1Password functionality.

    Just that after I leave the browser alone to work on code in the IDE, background.js erupts with errors and warnings and those numlockstate messages every second. Right now, I'm looking at nearly 200 errors about BrowserStorage, unchecked runtime receiving end does not exist, deprecated parameters, etc. After leaving it alone for 5 minutes.

    I think I'll just create a Chrome profile without the 1Password extension so I can test in peace, and only use a profile with 1Password to test pages in the app that deal with password managers and autofill.

  • 1P_SimonH's avatar
    1P_SimonH
    Icon for Community Manager rankCommunity Manager
    2 months ago

    Hi IainMcc,

    Good questions!

    The NumLockState message is the browser extension checking in with the 1Password app to make sure their locked states are in sync. If the extension discovers the app is locked, it will also lock itself.


    The attempts to reach my.1password.com are to validate the session, in order to sync any changes across devices.


    All that is to say, there's nothing unexpected happening with those items. For the HTTP 401 message, have you noticed any issues with saving items in 1Password?