"code signature could not be verified" message in Chrome

Megan

This discussion was created from comments split from: Autofill works only from the browser extension but not from the main app in Chrome for Mac.

markfitter

Same issue. 1Password 5.0.2 from Mac App store installed 11/10/14. Chrome 38.0.2125.111 Yosemite 10.10 on 2008 iMac. Extension 4.2.5.90. Message on screen: "Google Chrome is connected but its code signature could not be verified. Filling and other features are disabled until this configuration issue is resolved. This usually happens if Google Chrome is in the middle of an update. Please try to restart Google Chrome to fix this issue. Try moving Google Chrome to your /Applications folder to satisfy the Mac App Store sandbox requirements." I took those steps, then followed all recommendations in the troubleshooting guide, including disabling browser signature verification.

Megan

Hi @markfitter‌

I've split your comment into a separate post, since it seems that the issue you describe is different than that described by the original poster.

Thanks so much for including all your version numbers in your original post, it gives us a much better place to start. When you restarted Google Chrome and moved it to the /Applications folder, did you also restart your computer? Sometimes this can give things the kickstart they need.

If you've already tried this, please let me know and we'll investigate further. :)

markfitter

Closed all applications and rebooted computer. Disabled Dashlane extension in Chrome, and tried using 1Password to access my Amex account. Same issue occurred. No autofill.

Megan

Hi @markfitter,

Thanks for confirming that! We'll need to take a closer look at your system to figure out where things are getting tangled up.

I'd like to ask you to create a Diagnostics Report from your Mac:
https://guides.agilebits.com/kb/1password4/en/topic/diagnostics-report#mac4

Then attach the entire file to an email to us: support+forum@agilebits.com

Please do not post your Diagnostics Report in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your Diagnostics Report in our inbox.

A short note here once you've sent the Report in will help us to keep an eye out for it. :)

Once we see the report we should be able to better assist you. Thanks in advance!

markfitter

I emailed a diagnostics report yesterday. I apologize for the duplication here. I'll go ahead and do it again per your instructions above.

Jasper

Hi @markfitter,

Thanks for sending in the report! Could you let me know your email ticket ID please?

markfitter

There were two diagnostics sent: #WSK-76595-168 #CPV-96965-692

Megan

Hi @markfitter,

We've received your Diagnostics Report - thanks for sending it in! I've updated the email thread with the necessary details from this forum discussion so that it is easier for our support team to get up to speed with the issue. Someone from the support team will get back to you as soon as possible with some further information. We'll keep the conversation going directly via email to avoid complicating things between here and there. :)

ref: CPV-96965-692

michaelg04

wouldn't it be better to keep the information here for others like myself with the exact same issue can see the resolution?

Megan

Hi @michaelg04,

Whenever we get to the point of requesting Diagnostics Reports, it's likely that the fix is specific to the user they are written for, and we don't want to post instructions that might not work for other users.

If you provide a bit more detail about what you're seeing (including the version numbers of 1Password, your browsers and operating system), we'd be happy to find a solution for you!

head4heights

I have a similar problem but a bit different. OS X Mavericks 10.9.5, Chrome 41.0.2272.89. Filling in CC details on a payment form used to work. I can't remember the last time I used it, but it'll have been less than a week ago. Same error message mind you - different circumstances.

littlebobbytables

Hi @head4heights,

So full disclosure, Chrome isn't my day to day browser, for me that's Safari but there are a couple of things we can check.

1. If you visit chrome://help does it say you're up to date or does it say there is an update pending. I've seen it postulated that when Chrome is in the middle of an update that it stops behaving as expected. So if it says it has an update to install try rebooting and seeing if that improves matters.
2. What version of our 1Password Browser Extension are you running? the latest is now v4.3.1.
3. By default Verify browser code signature in the Advanced tab of 1Password's preferences is enabled, if you disable this does it behave any better?

If you can let us know the answers to those and we'll see if we can narrow down the cause :smile:

head4heights

Well I'll be... Chrome was 'out of date' because I'd not launched recently enough. Spot on guys :)
I appear to be on 1Password 4 Version 4.4.3 which is a little futuristic of me.

Thanks again.

littlebobbytables

@head4heights unfortunately you haven't inadvertently stumbled upon time travel :wink: 4.4.3 represents the latest version of 1Password 4 but the version of the extension is separate from that of the application and coincidentally is catching up with it. So there is a good chance you're running 4.4.3 of 1Password 4 for Mac and 4.3.1 for the 1Password Chrome extension.

Either way, great to hear a reboot resolved this issue and it helps confirm that this is something that can stop the extension confirming the signature so thank you :smile: