Forum Discussion
Why does 1P opens a new browser tab prompting login...
...immediately upon successful login to the Edge browser extension? How do I stop this unnecessary tab from opening? It doesn't serve any purpose, other than having to close this tab every time!
1Password Version: Not Provided
Extension Version: 2.8.0
OS Version: Windows 10
Browser:_ Edge
Referrer: forum-search:https://1password.community/search?Search=Why%20does%201P%20opens%20a%20new%20browser%20tab%20prompting%20login%2C%20after%20logging%20in%20to%20the%20Edge%20extension%3F
23 Replies
- steph_giles
1Password Team
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!
- bobkohOccasional Contributor
- I don't know where the 1P Diagnostic Report is. There isn't a Settings after the "three dot ellipses".
- 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 📤 Sendingmessage 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 📤 Sendingmessage 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.
- steph_giles
1Password Team
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.
- bobkohOccasional Contributor
I'm about to give up on 1Password. The repetitive prompts are killing me! a new tab opens prompting for the same master password AFTER signing in through the browser extension! Ugh!
- steph_giles
1Password Team
Apologies again for the trouble, I have removed the screenshot.
Please let us know if there is anything else we can help with at all.
- bobkohOccasional Contributor
I'll endure it for now -- it's just a matter of closing the extraneous browser tab. Will wait to see if a future release will rectify this behavior.
Would you please DELETE my second screen-print above showing my email and parts of my secret key?
Thank you for your attention.
Bob - steph_giles
1Password Team
Hey bobkoh,
I'm sorry for the ongoing trouble.
I think at this point it would be useful if we could take a closer look at some logs and what may be going wrong.
I'd like to ask you to send over a console log from your browser as well as a diagnostics report:
Please attach the reports to an email message 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!
- bobkohOccasional Contributor
- steph_giles
1Password Team
Thanks for getting back to me bobkoh, I'm sorry for the trouble.
Can you check the version of 1Password in your browser that you have installed? The behaviour you are running into is an issue which I believe to be fixed in the latest updates.
- bobkohOccasional Contributor
It's doing it again! I sign-in through the browser extension. A browser tab opens prompting for log-in (again). Please see attached screen-prints in the that order.