Chrome Extension Completely Malfunctioning

jrodl3r

Many issues so far w/ new extension:

1. Chrome Toolbar Menu-click/hover engagement is very buggy. Looses focus too easily, sometimes completely unprovoked.

2. If I click Edit on any item nothing happens. (Even w/ the statusbar mini menu)

3. Hotkey autofill doesn't work anymore. It used to not work w/ the last version as well, but only if I had another Chrome Canary window open on another space/screen (not sure why that was never fixed last release btw) - And now, it flat-out doesn't work at all.

I have to say I love the product, but I bit my tongue on the raised price tag, and zero upgrade options from the last release... So what's the deal? Are you guys ignoring Chrome? Is browser extension support not a huge concern or priority for the dev team?

Either way, just want to know what to expect, as this functionality is obviously quite important.

Cheers,
John

jrodl3r

bump.. can anyone from support please provide some brief explanation? THX

MikeT

Hi John,

1. Can you tell us more about this? If you can reproduce this, can you tell us the steps, so we can try and then work on improvements for it.
2. This should be improved in the latest update but if it is still a problem, can you open the main 1Password app, close it but don't quit it. Would editing from 1Password mini now work?
3. Are you using multiple profiles in Chrome, or is it just separate Chrome Windows with the same profile? Chrome Canary is working fine for me here, multiple Windows and hotkey is working in all of them. The multiple profile does interfere and can break the hotkey in some cases, we're investigating this one.

Can you narrow the cause down by trying everything in this article and see if you can find it for us.

zero upgrade options from the last release...

All MAS customers and all folks who bought 1Password this year (2013) at our website gets a free upgrade to 1Password 4. Folks who bought before 2013 can buy an upgrade for $25.

Are you guys ignoring Chrome? Is browser extension support not a huge concern or priority for the dev team?

No, we're not ignoring our extensions, it's one of our most important features. We are working to improve them but we have to be able to reproduce the issue. So far, majority of the reported issues are related to that article I linked you to, third party software, configuration issues, and version mismatching. We already released an update to the Firefox extension last week to fix the reported issue with Go and Fill.

jrodl3r

I have multiple profiles "enabled" on Chrome (current stable) however, only 1 is active/in-use/logged-in (no multiple windows with varying unique profiles, they all share the same logged-in profile). Canary, as it turns out, is now functioning properly (same profile config)... as of the latest update.

I will keep posting more info as I continue testing. I'm much more hopeful after seeing Canary up and running properly.

On a lighter note, I have no problem spending $40 on the new release + $8 on the new iPhone/iPad app. It's just a pain after I've already spent similar amounts on the last versions roughly 1 year ago... (Total of about $15 + $10 + $40 + 8 = $73 + TAX + news of iCloud Keychain support.... == Ugh..) And, this stuff (the discount you mentioned) isn't apparent in the AppStore, where I purchased these upgrades, which leads to you saying something like "Sorry, the AppStore is troublesome for refunds or discounts. Better luck next time."

Thx for responding, I appreciate the effort and the quality software.

Respectfully,
John Rodler

MikeT

Hi John,

Canary has a a separate profile from Chrome, only the beta/dev channels reuses the stable profile. We actually ask customers to try Canary to see if 1Password works better there when their Chrome profile is expected to be a problem.

Sorry about the timing of the new upgrades. 1Password 3 for iOS/OS X was released 2-4 years ago, and we released over 100 of free updates since then. Expect the same thing here, 1Password 4 to get a lot of free updates over the next year, providing more value of your investment in us.

jrodl3r

No worry on the 2nd part. That's just how it works out sometimes, nobody's fault.

The 1st part though, are you suggesting that I use Canary (full-time) until this gets resolved on Chrome (public)? If that's the case, I'm not 100% sure that will work for me. I'm a developer and Canary is thus, used primarily for my dev workflow. I focus a lot on performance, and mixing the two would be chaotic for me, personally.

Hopefully, that's not what you meant..?

MikeT

Hi @jrodly3r,

The 1st part though, are you suggesting that I use Canary (full-time) until this gets resolved on Chrome (public)?

No, it's the debugging process to pinpoint where the problem is, the specific Chrome profile or the extension. Since it does work in Canary, it suggests a corruption in the Chrome profile somewhere. We'd then suggest the user to backup their info in Chrome such as bookmarks, extension list, and so on before they create a new profile for Chrome in this article to test 1Password there. 80% of the times, the new profile did help and the user can restore the data back in there.

That's what I'd recommend next for your case, try a new Chrome profile.

jrodl3r

Ya, tried and failed (multiple times)... Also, no luck after I did the appstore update either - and now I get this: http://cl.ly/SIBh

jrodl3r

Ok dude... It was Sophos! (DAMMIT!) ; )

Megan

Hi @jrodl3r,

Thanks for letting us know you got it all sorted out :)