Everytime I login in 1P version 8 I get an email

Just tried V8 again, and again I get ongoing email notification that I use a New Browser

on my 1Password Profile it is full of "authorized devices" showing that I am using Safari Macos 10.15.7
which is not accurate, I am using Safari on macOS 11.5.2

However my MBA shows with the right MacOs

and as said everytime I log in 1P I get an email

Something must be wiping out the Safari local storage that is used by the 1Password extension. Do you have any apps/utilities that might be doing it?

@Gilles I was hoping to see the logs from the Console tab. Something like this:


[Debug] crypto tests: 8.200ms (background.js, line 2)
[Log] 👋 Initializing 1Password (background.js, line 2)
[Info] channel: stable (background.js, line 2)
version: 2.0.6
build: 20170 (15.0)
browser: Safari (15.0)
os: MacOSX (10.15.7)
[Info] 👍 Finished initializing 1Password (background.js, line 2)
[Info] 💫 Looking for desktop app com.1password.1password (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <4049140050> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <4049140050> (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <2983938448> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <2983938448> (background.js, line 2)
[Info] We successfully unlocked 0 account(s) from a Desktop app with 0 unlocked and 3 locked account(s). (background.js, line 2)
[Info] Received <AppQuit> from the native core (background.js, line 2, x2)


@roustem

Something must be wiping out the Safari local storage that is used by the 1Password extension. Do you have any apps/utilities that might be doing it?

"Cookie" app from SweetP production maybe

From the "Console Tab", can you sprecify where I find this, so I can provide next time I give a try

@roustem

I disable "Cookie" app and the problem remains

from the Console Tab

[Debug] crypto tests: 6.631ms (background.js, line 2)
[Log] 👋 Initializing 1Password (background.js, line 2)
[Info] channel: stable (background.js, line 2)
version: 2.0.6
build: 20170 (15.0)
browser: Safari (15.0)
os: MacOSX (10.15.7)
[Info] Upgrading database from version 0 to 10. – Proxy (background.js, line 2)
Proxy
[Info] 👍 Finished initializing 1Password (background.js, line 2)
[Info] 💫 Looking for desktop app com.1password.1password (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <3138226852> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <3138226852> (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <2989676884> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <2989676884> (background.js, line 2)
[Info] [LM] Started Safari Lock Monitor at 1630932053670 (minutes=10, lock on sleep=true). (background.js, line 2)
[Info] Hooray!; Unlocked account MM24RGMW5JFVNETXSAUNKBAR4A with MUK; 🎉 (background.js, line 2)
[Info] We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)


NOTE THAT SYSTEM Macos IS SHOWING 10.15.7, my MacOs is 11.5.2 on a MBA M1

@Gilles looking at the Cookie.app and it seems that something that could certainly delete the local database used by the extension. I am surprised that it doesn't have any options to selectively delete the data.

@roustem

Ok disabling totally Cookie.app solved the problem with 1password version 8

Thank you

Note: not too pleased with disabling Cookie.app

I received the a similar email in the morning and was panicked a bit, but looks like it's a bug.

Hey @sarath — have you experienced this again at all? I'd love to hear more about what leads to these emails, if you're still encountering this.

I’ve not observed this of late. @ag_michaelc