Nothing showing.

prime

So Firefox 1Password was on 1.8.0 no issues. Chrome was on 1.8.1 and when I click on the icon, it’s blank, and I can’t see my vault. It’s a white blank window. 1Password x just updated to 1.8.1 just now on Firefox, I have the same issue as chrome. This is my work computer running Windows 10 and both browsers are on the current ones. Firefox 61.0.1 and chrome 67.0.3396.99. When the issue started with Chrome (on Monday) no settings were changed at all. This morning Firefox was on 1.8.0 and I was working on something, it updated to 1.8.1, and now the icon is blank when I click on it to show my vault :(

Monday I uninstalled it from Chrome, cleared all my history and cookies, reinstalled it, and nothing. I didn’t say anything because I wasn’t done troubleshooting yet, and I had a back up (key word, had ;) ) Now it happened to Firefox (my back up that I had.... again the key word :lol:), it seems like the issue was when it updated to 1.8.1

I’ll try and take photos, but it is a work computer....

dalton

Thank you very much for letting us know you're running into this issue, @prime. I tried to reproduce this behavior in Chrome/Firefox on macOS/Windows 10 but haven't had any luck so far. There wasn't a whole lot changed between 1.8 and 1.8.1 so I'm curious what exactly is going on here and why a fresh reinstall of 1Password X didn't work for you. Would you be willing to capture some logs from 1Password X and share them with me? Here's how to do that in Chrome:

1. Open Chrome and go to the following page: chrome://extensions
2. Switch "Developer mode" on by toggling the switch in the top right-hand corner of the page.
3. Find 1Password X and click the link named "background page". It should be colored blue.
4. A new window should appear after clicking the link. Select the Console tab.
5. Reproduce the issue. I'm assuming opening/closing the popup should be sufficient.
6. Either take a screenshot of the logs or copy/paste in your reply.

I'm hoping one of the messages from the logs will tell us more about what's happening.

prime

This? I removed my email and account name

crypto tests: 40.85400390625ms
background.js:1 PBES2g-HS256(100000): 57.808837890625ms
background.js:1 [LM] @startMonitoring (autolock=500)
background.js:1 [action/Session#verify] Error: Please authenticate with MFA
at new t (background.js:1)
at background.js:1
P.e.(anonymous function) @ background.js:1
background.js:1 [action/auth#signInWithEmailAndPassword] Error: Please authenticate with MFA
at new t (background.js:1)
at background.js:1
P.e.(anonymous function) @ background.js:1
background.js:1 PBES2g-HS256(100000): 85.160888671875ms
background.js:1 Signed in sucessfully to I TOOK OUT MY EMAIL @ MY ACCOUT with MFA and loaded account details. Elapse time 1342ms.
background.js:1 account info was up-to-date for account
background.js:1 keysets were up-to-date for account
background.js:1 vaults were up-to-date for account
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 start
background.js:1 🏁 end
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 start
background.js:1 🏁 end
background.js:1 account info was up-to-date for account
background.js:1 keysets were up-to-date for account
background.js:1 updated vaults for account
background.js:1 account info was up-to-date for account
background.js:1 keysets were up-to-date for account
background.js:1 vaults were up-to-date for account
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 Notifier not available
P.e.(anonymous function) @ background.js:1
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 Uncaught (in promise) TypeError: Cannot set property '10' of undefined
at Jk (background.js:1)
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap
background.js:1 🚩 ap
background.js:1 🏁 ap

prime

But this works:

prime

More info: this is a guest account. I keep forgetting this and not sure if this info will help.

AGAlumB

@prime: Sorry fo the sudden troubles. This is an odd one. Just to clarify, this is on Windows 10? Have you tried rebooting? The next thing I'd do is sign out of any accounts in 1Password X and then sign back in. Not sure if you've done that already in the process of troubleshooting. Either way, let me know.

The weird thing to me is that it's happening in both browsers, and only after updating to 1.8.1. I don't believe a guest account should make any difference, but I'll nuke and do some testing of my own here to see if I can reproduce this at all.

AGAlumB

@prime: So, I just went through and created a guest account to setup 1Password X in a Windows 10 VM...and I'm getting the same result you are. It does look like we broke something, possibly related to the changes we've made for supporting the new password history feature (but that's just a hunch). We'll figure out what's going on and get this fixed so you're not stuck using the web interface. Again, I'm sorry for the trouble this is causing, and I appreciate you bringing it to our attention. :blush:

AGAlumB

@prime: It looks like there's another issue with this in the beta as well, but I'd be curious if you see the same thing. If you install 1Password X beta in Chrome, are you able to sign in and use your account there?

ref: b5x-518

prime

Woohoo @brenty as long as you we able to get this too. Yes, I am running Windows 10 and I uninstalled this, cleared history, cleared cookies, restarted the computer, reinstalled it, and still the same issues. I’ll try the beta later if I get a chance and let you know.

demoniac

I'm seeing the same issue, just a blank white screen when I click on 1Password X. For me this works when I start Chrome but randomly or even as I'm typing to search it will just go blank. Running Windows 10, Build 1803. Have not tried any beta yet.

Also, like above the inline password filling works fine during this problem.

AGAlumB

@prime: Don't get your hopes up, because it's definitely not working for me in the beta either; and I believe we've identified what's breaking this for guest accounts. We'll get it fixed. :blush:

AGAlumB

@demoniac: Are you also using a guest account? I'd rather not assume you're experiencing the same issue, since this is happening to prime in not just Chrome but Firefox as well.

AGAlumB

@prime: The current beta — 1.9 — has this same issue. But we've got a fix that should be in the next beta before too long, so if you install it now you should get that as soon as it's available, hopefully to confirm that it resolves the issue for you.

prime

@brenty, I can’t thank you enough for taking the time helping with me on this! Much appreciated! I did install the beta 1.9 on Chrome and confirmed the same issue. The fact you guys know about it, I know a fix will come soon. I probably should have said something when I 1st saw the issue on Chrome, but you know work gets :lol:

Mitch

Hi @prime,

The issue with guest accounts has been fixed in version 1.8.2 and 1.9.2 beta, both released this afternoon. Thank you for helping us troubleshoot this issue so we could nail it down so quickly. :)

Mitch

prime

@Mitch thank! I’ll update tomorrow when I get to work. Thank you so much for the quick fix! Anytime to help too, I worked with @brenty on a few things and he’s always on top of it helping me out.

prime

@Mitch I can confirm it works on Firefox, but I got kicked off the work VPN and change check Chrome. I’m sure all is fine. Thanks again guys!

AGAlumB

@prime: Hey, thanks for bringing it to our attention, and confirming the fix. If you run into any other issues, just let us know. :chuffed: :+1:

demoniac

I guess I'm having a different problem as I'm still having this issue. I have a individual 1password account. I have multiple vaults but no guest access. At random times or when I am searching for an item in 1Password X the 1Password X window will go blank (white). I've seen this happen when typing in my search multiple times. Here's my info:

OS: Windows 10 1709 (work) and Windows 10 1803 (home)
Browser: Vivaldi 1.15.1147.52 (Stable channel) (32-bit)
1Password X 1.8.2 (I believe this started with the 1.8 branch).

In all cases once this happens I can close my browser and upon re-open everything works fine for awhile. I am not able to replicate this problem on demand. I'd guess it has happened 4-5 times over the last week or two. When experiencing this problem I can still use the inline features of 1Password X okay.

Please let me know what other info I can provide.

beyer

Hey @domoniac,

I greatly apologize for not getting back to you sooner. That's a troubling issue you're having, especially if it's happening while searching the popup.

The next time you see it happen, could you please follow the steps @DaltonD listed above? I speculate you'll see some sort of error logged in the background console. Could you right click the white popup, select inspect, and then click the console tab and lets us know if there are any errors (in red) there?

That should hopefully help us narrow down what's happening. Thanks! 🙌

-Beyer