Why does 1P opens a new browser tab prompting login...

I'm sorry for the ongoing trouble @bobkoh.

Can you send over the details as requested above so we can try to get to the bottom of things?

Thank you in advance.

1. I don't know where the 1P Diagnostic Report is. There isn't a Settings after the "three dot ellipses".
2. Also, your upload dialog wouldn't allow me to upload a .log or a .txt! Keeps coming back with "File format is not allowed". Pasting the latest console content here.....

16:12:24.950 background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
16:12:25.110 background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.
16:12:25.247 background.js:2 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
at y (background.js:2:9045)
y @ background.js:2
await in y (async)
gke @ background.js:2
(anonymous) @ background.js:2
listener @ background.js:2
broadcastState @ background.js:2
updateState @ background.js:2
connectWithDesktopApp @ background.js:2
await in connectWithDesktopApp (async)
reconnectWithDesktop @ background.js:2
(anonymous) @ background.js:2
setTimeout (async)
Sge @ background.js:2
oge @ background.js:2
get-frame-manager-configuration @ background.js:2
await in get-frame-manager-configuration (async)
yde @ background.js:2
r @ background.js:2
16:12:25.253 background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
16:12:25.254 background.js:2 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
at y (background.js:2:9045)
y @ background.js:2
await in y (async)
gke @ background.js:2
(anonymous) @ background.js:2
listener @ background.js:2
broadcastState @ background.js:2
updateState @ background.js:2
connectWithDesktopApp @ background.js:2
await in connectWithDesktopApp (async)
reconnectWithDesktop @ background.js:2
(anonymous) @ background.js:2
setTimeout (async)
Sge @ background.js:2
oge @ background.js:2
get-frame-manager-configuration @ background.js:2
await in get-frame-manager-configuration (async)
yde @ background.js:2
r @ background.js:2
16:12:25.255 background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
16:12:25.692 background.js:2 💫 Looking for desktop app com.1password.1password
16:12:25.693 background.js:2 📤 Sending message to native core <1365804665>
16:12:25.910 background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.
16:12:25.911 background.js:2 💫 Looking for desktop app com.1password.1password7
16:12:25.913 background.js:2 📤 Sending message to native core <2321611446>
16:12:25.915 background.js:2 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
at y (background.js:2:9045)
y @ background.js:2
await in y (async)
gke @ background.js:2
(anonymous) @ background.js:2
listener @ background.js:2
broadcastState @ background.js:2
updateState @ background.js:2
connectWithDesktopApp @ background.js:2
reconnectWithDesktop @ background.js:2
(anonymous) @ background.js:2
setTimeout (async)
Sge @ background.js:2
oge @ background.js:2
get-frame-manager-configuration @ background.js:2
await in get-frame-manager-configuration (async)
yde @ background.js:2
r @ background.js:2
16:12:25.916 background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
16:12:25.918 background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.
16:12:25.994 background.js:2 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
at y (background.js:2:9045)
y @ background.js:2
await in y (async)
gke @ background.js:2
(anonymous) @ background.js:2
listener @ background.js:2
broadcastState @ background.js:2
updateState @ background.js:2
connectWithDesktopApp @ background.js:2
await in connectWithDesktopApp (async)
reconnectWithDesktop @ background.js:2
(anonymous) @ background.js:2
setTimeout (async)
Sge @ background.js:2
oge @ background.js:2
get-frame-manager-configuration @ background.js:2
await in get-frame-manager-configuration (async)
yde @ background.js:2
r @ background.js:2
16:12:25.994 background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
16:12:25.995 background.js:2 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
at y (background.js:2:9045)
y @ background.js:2
await in y (async)
gke @ background.js:2
(anonymous) @ background.js:2
listener @ background.js:2
broadcastState @ background.js:2
updateState @ background.js:2
connectWithDesktopApp @ background.js:2
await in connectWithDesktopApp (async)
reconnectWithDesktop @ background.js:2
(anonymous) @ background.js:2
setTimeout (async)
Sge @ background.js:2
oge @ background.js:2
get-frame-manager-configuration @ background.js:2
await in get-frame-manager-configuration (async)
yde @ background.js:2
r @ background.js:2
16:12:25.995 background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

Hey @bobkoh,

Thanks for getting back to me.

The instructions to grab the diagnostics report are for the 1Password desktop app not 1Password in your browser. Can you let me know if you are able to follow them here?

In addition, can you attach both reports to an email addressed to support+forum@1password.com with a link to this thread.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

So I suspect that the annoynance I have been experiencing is because I did not have the 1P8 app for Windows installed. SSO appears to be jiving now that I have the desktop app instead of just juggling between the browser extension and the 1P website.

Thanks for getting back to me @bobkoh, you should be able to use 1Password in your browser independently but I'm glad things are now working better for you.

Let us know if there's anything else we can help with.

I agree that the extension ought to work independently. I'm just glad that the desktop app is able to provide what was lacking. Thank you for your support, Steph!

@bobkoh on behalf of Steph, you are welcome! If you want to troubleshoot things with just the extension running by itself, let us know and we can help look into it. We're always happy to help.

I appreciate the help, Joy! I prefer the more robust app anyway.

@bobkoh glad to hear that, I also use both the app and extension. Having both just works better for me.

Agreed! I find the extension to be a quick 'easy reach', while the app is more robust for overall maintenance.