Command + \ fills password, but doesn't submit. Also opens password generator in 1Password mini

leithl

I have the chrome extension installed as well as the mac app via the app store.

If I use Command + \ it does fill in the password (good) but doesn't submit, despite the option in preferences being checked. Also oddly, it opens 1Password mini with the password generator selected...

I just want it to fill the password and submit the form.

littlebobbytables

Hi @leithl‌

Can you confirm a couple of things for me please.

• Versions of OS X, 1Password, Chrome and the 1Password Chrome extension.
• What your keyboard shortcuts in 1Password are set to (1Password > Preferences... > General tab)

Certainly that's an odd one.

leithl

Hi @littlebobbytables‌ (love the name!)

Versions:

• OS X: 10.10.1
• 1Password: 5.0.2 (502006) (from mac app store)
• Chrome: 39.0.2171.95 (64-bit)
• 1Password chrome extension: 4.2.5.90

Keyboard shortcuts are all defaults I believe:

rickfillion

Hi @leithl,

Did this ever work for you? Auto-Submit with the Mac App Store version of 1Password requires an external component to work. The AgileBits store version of the app automatically installs that for you so that if ever you switch from that to the Mac App Store version this would be present. I recommend downloading and installing this package will will install the AutoSubmit script for the app and it should be able to autosubmit from then on:

Autosubmit Script Installer

Let us know know this works out for you.

Rick

leithl

I did switch from the non-mac app store version to the mac app store version (for iCloud syncing.)

I installed the autosubmit installer. Uninstalled the chrome extension, restarted chrome, installed the chrome extension again. I had some inconsistent behavior immediately after, but it returned to the above within 3 or 4 Command + \'s.

So we're back where we were... any ideas?

rickfillion

Hi @leithl,

Sounds like something may be interfering with the execution of that applescript. Could you check to see if anything is logged in the console when you invoke cmd-\? To do this:

• Launch Console from /Applications/Utilities
• Make sure that 'All Messages' is selected in the left side bar
• Search for 'agilebits' in the top right search field which will filter all messages to only show those from 1Password
• Invoke cmd-\ in your browser
• See if there's any logging statements that correspond to the timestamp of when you invoked cmd-\

If there are any logging statements, please paste them here (they shouldn't contain any private information, but you'll want to double check and read through them before hand to make sure you're OK with that info being on a public forum).

Rick

leithl

Hi @rickfillion‌ ... looks like there is an event:

  12/23/14 11:20:10.007 AM 2BUA8C4S2C.com.agilebits.onepassword-osx-helper[4733]: 502006 [EXT:0x7ff553e0f520:<OP4ExtensionClient: 0x7ff553e3b680>] E findExtensionProcessForPort: | Failed to find extension process for 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:56827', my PID: 4733, invalid output: '4733
    ', apps found: (
    )

Does that help?

rickfillion

Hi @leithl,

OK if that's getting logged then that means that the keyboard shortcut is being captured and we're trying and failing to communicate with the extension. That rules out a few things.

Are there any messages before that message about the chrome-extension disconnecting? If not, then we may have to get a Diagnostics Report which would have more logging, to get an idea of what's going on here. Looking at the code, it looks to me like we log the connections/disconnections at a level that wouldn't show up in Console.

Can you create a Diagnostics Report and email it into support+forum@agilebits.com. Include a link to this thread so that we can connect the dots and know what to look for.

Rick

leithl

Thanks @rickfillion‌, just send the report in.

littlebobbytables

Hi @leithl‌

I've found your diagnostic report so hopefully @rickfillion‌ will be able to discover the issue at hand. Certainly I'll be interested in what he finds too as that was an odd problem you had.

ref: SME-43165-549

rickfillion

Hi @leithl‌,

Looking at your Diagnostics Report now... and I'm seeing things in there that make me wonder. Looks like you're using Fast User Switching to switch between user accounts. Is that right? We try our best to support that situation, but we've seen issues there. The problem there is that Chrome in one user account can accidentally connect to the mini on the other account. Ideally you'd make sure that only 1 instance of 1Password is running at once. Which would require that you either fully log out or that you manually Quit 1Password and the Mini before switching accounts. Obviously not an ideal scenario.

The next thing I'm seeing is multiple instances of Chrome connecting at once. I see...

User Switch:

Wed Dec 24 15:09:15 2014| 502006 [HELPER:0x7ff551711000:<OPHelperAppDelegate: 0x7ff551600380>] S workspaceDidBecomeActive: | workspaceDidBecomeActive

Mini is starting the extension server:
Wed Dec 24 15:09:15 2014| 502006 [EXT:0x7ff551711000:<OP4ExtensionServer: 0x7ff55155eb20>] M start | [ES4] Starting JSE server on port 6263 Wed Dec 24 15:09:15 2014| 502006 [EXT:0x7ff551711000:<OP3ExtensionServer: 0x7ff55144e310>] M start | [ES3] Starting JSE server on port 6258

3 Chrome Instances connecting:
Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff5542730f0:<OP4ExtensionHTTPConnection: 0x7ff5542708a0>] M webSocketForURI: | [ES4] Extension connected Chrome-Extension 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk / (null)' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff553e5b520:<OP4ExtensionClient: 0x7ff554284a20>] S didOpen | [ES4 0x7ff554284a20] Connected 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51393' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff5514b9a90:<OP4ExtensionHTTPConnection: 0x7ff554266ca0>] M webSocketForURI: | [ES4] Extension connected Chrome-Extension 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk / (null)' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff554114510:<OP4ExtensionClient: 0x7ff5541293a0>] S didOpen | [ES4 0x7ff5541293a0] Connected 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51396' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff554103460:<OP4ExtensionHTTPConnection: 0x7ff5541139a0>] M webSocketForURI: | [ES4] Extension connected Chrome-Extension 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk / (null)'

Then I see 2 Chrome Instances properly connect, and 1 fail to connect:
Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff553e5b520:<OP4ExtensionClient: 0x7ff554284a20>] S handleHello: | Welcoming version 4.2.5.90 of Chrome-Extension. Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff553e5b520:<OP4ExtensionClient: 0x7ff554284a20>] S sendAction:payload: | [ES4 0x7ff554284a20] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'welcome' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff554102e30:<OP4ExtensionClient: 0x7ff5541293a0>] S handleHello: | Welcoming version 4.2.5.90 of Chrome-Extension. Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff554102e30:<OP4ExtensionClient: 0x7ff5541293a0>] S sendAction:payload: | [ES4 0x7ff5541293a0] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'welcome' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff553e5ac70:<OP4ExtensionClient: 0x7ff55427f0a0>] S handleHello: | Welcoming version 4.2.5.90 of Chrome-Extension. Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff553e5ac70:<OP4ExtensionClient: 0x7ff55427f0a0>] S sendAction:payload: | [ES4 0x7ff55427f0a0] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'welcome' Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff5542730f0:<OP4ExtensionClient: 0x7ff554284a20>] E findExtensionProcessForPort: | Failed to find extension process for 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51393', my PID: 4733, invalid output: '4733 ', apps found: ( ) Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff554103460:<OP4ExtensionClient: 0x7ff55427f0a0>] S findExtensionProcessForPort: | [ES4 0x7ff55427f0a0] Connected chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51397: <NSRunningApplication: 0x7ff5542666f0 (com.google.Chrome - 4756)> Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff5514b9a90:<OP4ExtensionClient: 0x7ff5541293a0>] S findExtensionProcessForPort: | [ES4 0x7ff5541293a0] Connected chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51396: <NSRunningApplication: 0x7ff55428cfd0 (com.google.Chrome - 4756)> Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff5514b9a90:<OP4ExtensionClient: 0x7ff5541293a0>] S verifyClient:satisfiesRequirement: | Extension client 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk' (<NSRunningApplication: 0x7ff55428cfd0 (com.google.Chrome - 4756)>) passed validation Wed Dec 24 15:09:16 2014| 502006 [EXT:0x7ff554103460:<OP4ExtensionClient: 0x7ff55427f0a0>] S verifyClient:satisfiesRequirement: | Extension client 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk' (<NSRunningApplication: 0x7ff5542666f0 (com.google.Chrome - 4756)>) passed validation

I'm curious to know where these 3 instances of Chrome are coming from. In theory this shouldn't be a problem. We've had issues in the past with multiple Chrome Profiles running at once, but I believe that those were at least mostly addressed in 5.0.2. Do you have any idea where that could be coming from? I'm just looking to eliminate variables in order to determine what the real cause of the problem is here.

Rick

leithl

Hi @rickfillion‌, I am running fast user switching between 2 users, each with one chrome session each. That would explain 2 chrome sessions, but not the third... I did open the Activity Monitor and found there were two Google Chrome root processes (and many helper processors) but again, no third one.

So correct thesis on your part, but still not sure how there is a third, failing, chrome instance... Anything else I can try?

littlebobbytables

Let's find out if @rickfillion‌ can bring any genius insight to this :smile:

leithl

@rickfillion‌ ... any updates? :)

rickfillion

Hi @leithl,

Can we start by taking Fast User Switching out of the equation? Once we have things working consistently we can look at re-introducing that and trying to get it working correctly. It might help us determine where the third instance is coming into play. Could you avoid having more than 1 instance of 1Password running at once for the next few days to see how that works out?

Rick

leithl

Hi @rickfillion‌, I did try that actually, the other day. I rebooted and just logged in with one user, the second user was never logged in (thus chrome/1password wasn't launched.) Same behavior.

rickfillion

Hi @leithl,

I'm not sure if that makes me happy or not. :smile: OK... could you get us another Diagnostics Report when you're running it in this configuration (no Fast User Switching) when it doesn't work? One thing that you should make sure to be conscious of when testing is that there's sometimes a ~30 second period between when the browser extension first starts up and connects to 1Password, to when it actually works correctly. During the first 30 seconds or so 1Password is usually stuck verifying the authenticity of the browser. I doubt that this is what you're running into, but just want to make sure that we're taking that out of the equation. So start things up and let it sit for 30 seconds before running any tests. (I'm hoping to get that time reduced somehow in a future release)

Rick

Jan Michael

Hello I have a similar issue. On a couple of Web sites auto-submit works reliably, but on some not.
I'm using OS X 10.10.1 (14B25) and Chrome Version 39.0.2171.95 (64-bit) as well as Safari, but on

• www.xing.com

I can't get the auto submit feature working.
The console output is as follows.

10.01.15 12:18:37,665 2BUA8C4S2C.com.agilebits.onepassword4-helper[664]: 510028 [EXT:0x7faa69c08d20:<OP4ExtensionClient: 0x7faa6e84d5a0>] S sendAction:payload: | [ES4 0x7faa6e84d5a0] chrome-extension://phicbbndgmmpogmijjkbmdhpioaieaha sendAction: 'getActiveURL'

One hint. When I let 1password 5 (1Password 5, Version 5.1.BETA-28 (510028)) fill out login credentials it does not auto submit. But when I afterwards hit "Enter" the credentials get submitted.

The AutoSubmitScript is in place:

[jan@marvin:Pictures]$ cat ~/Library/Application\ Scripts/2BUA8C4S2C.com.agilebits.onepassword-osx-helper/1Password_Autosubmit.scpt tell application "System Events" to keystroke return

Can you please help?

littlebobbytables

Hi @Jan Michael‌

What version of the 1Password extension are you running (beta or stable)?

Does the problem persist if you run 1Password 5.0.2 (the stable version) along with the stable version of the browser extension, assuming you aren't already.

Basically I want to discover if it's a beta issue or we're looking at a blip in your system.

Jan Michael

Thanks @littlebobbytables‌

... for taking care of the issue.

I've used the beta extension version 4.3.0.6. But now I've reverted to 1Password 5.0.2 from your home page and stable Chrome extension 4.2.5.90. I've restarted 1Password and the browser, but the behaviour is still the same.

rickfillion

Hi @Jan Michael‌,

The version of 1Password from our website does not rely on the 1Password_Autosubmit.scpt. That applescript is only required for the Mac App Store version to get around a sandboxing restriction Apple imposes on our app.

As for xing.com... I just tried here and was able to have it auto-submit for me, so it doesn't look like it's anything about the page that's interfering with the app or extension. If you're consistently unable to auto-submit with xing.com, I recommend that you try following the instructions to Manually Save the login on xing.com to see if maybe it's because the page has changed since you originally created the login item.

I hope this helps. Let us know how it goes.

Rick

leithl

Hi @rickfillion‌, diagnostic report sent per post #17.

Let me know what you find!

Jan Michael

Hi @rickfillion‌,

Long story short: A manual save of the new login helped to make auto submit happen. The old login was from 2008.
Thanks for analysis and help.

Kind Regards.
Jan.

rickfillion

@Jan Michael‌ : that's great to hear.

@leithl : Looking at your Diagnostics Report....

I see

Mon Jan 12 11:57:37 2015| 502006 [HELPER:0x7fba70403480:<OPHelperAppDelegate: 0x7fba7050f610>] M applicationDidFinishLaunching: | Starting 1Password mini 5.0.2 #502006 built Oct 29 2014 14:14:22

So at 11:57:37 the mini started.

Then I see two chrome extensions connect to it.

Mon Jan 12 11:57:46 2015| 502006 [EXT:0x7fba70758b80:<OP4ExtensionClient: 0x7fba7046b840>] S sendAction:payload: | [ES4 0x7fba7046b840] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'welcome'
...
Mon Jan 12 11:57:53 2015| 502006 [EXT:0x7fba706a9450:<OP4ExtensionClient: 0x7fba7056a430>] S sendAction:payload: | [ES4 0x7fba7056a430] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'welcome'

Both of them seem to connect fine:

Mon Jan 12 11:57:46 2015| 502006 [EXT:0x7fba70723970:<OP4ExtensionClient: 0x7fba7046b840>] S verifyClient:satisfiesRequirement: | Extension client 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk' (<NSRunningApplication: 0x7fba70449b00 (com.google.Chrome - 463)>) passed validation
...
Mon Jan 12 11:57:53 2015| 502006 [EXT:0x7fba70441cb0:<OP4ExtensionClient: 0x7fba7056a430>] S verifyClient:satisfiesRequirement: | Extension client 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk' (<NSRunningApplication: 0x7fba706b2360 (com.google.Chrome - 463)>) passed validation

Past that I see no communication going on at all between the Chrome extension and the mini.

Looks like you have 3 chrome profiles. That would explain the multiple extensions. One should load per extension. I don't think that's what's causing us issues here, but it may be worth trying to make sure that only 1 chrome profile is open at once. Looks like both profile 1 and profile 2 have the extension installed and 3 does not.

The Diagnostics Report says that you have AdBlock installed. Could you try uninstalling that? In some cases this can interfere with the extensions.

Let's see if either of those helps, and if not we'll have to dig further.

Thank you for your patience.

Rick

leithl

Hi @rickfillion‌

It seems that the problem is multiple profiles. I uninstalled adblock and diabled the second profile which had 1Password installed. Everything works fine. Re-installed adblock and it still works fine. I even tried fast user switching with both users only having one chrome profile open--still worked!

Any idea how to make this work for two profiles?

rickfillion

Hi @leithl,

Thanks for the update. Are you using both chrome profiles at once? I have multiple profiles, but only use one at a time and it works fine. I know that we had a bug open about issues with multiple profiles, but no one here was able to reproduce the issue at all. The only reason I have multiple profiles is because of the testing I did for that bug, it's not a feature I actually need.

Would you mind taking the time to try creating a new user account and setting up multiple chrome profiles there to see if it reproduces that easily for you?

Rick