chrome browser not filling

auludag
auludag
Community Member
in 1Password in the Browser

hi,

using 1password the latest version. 6.6.4 and using Chrome Version 57.0.2987.133 (64-bit)

and OS X 10.11.6

On Chrome i have issues. For example on facebook, login data isn't filled though everything seems normal.

if i restart chrome or drastically if i restart the mac, it fills the login. but for a password filling, restarting things is silly.

so i was looking if it is related to something in URL.

for example not filled URL was

https://www.facebook.com/login/?next=https://www.intern.facebook.com/ads/manager/pixel

was this link in current scenario.

it was filled with other browser without problem.

so what should i check?

1Password Version: 6.6.4
Extension Version: 4.6.4.90
OS Version: 10.11.6
Sync Type: icloud
Referrer: forum-search:chrome browser not filling

Comments

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @auludag,

    Here is what I would like you to do for us please.

    1. Download our diagnostic report tool from For 1Password on your Mac so it will be immediately available later.
    2. Wait for the issue to reappear.
    3. Create the diagnostic report.
    4. Restart Chrome and confirm this results in the extension working again on the exact same page it wasn't filling in step 2.
    5. Send us the diagnostic report using the steps detailed below.

    Please do not post your Diagnostics Report in the forums

    The email address you will want to use is support+extension@agilebits.com.

    Once you've sent the report please post the ticket ID here. The ticket ID should be in the automated reply you receive after sending the email. Once we've located the email we'll review the diagnostic report and see what we can find out.

  • auludag
    auludag
    Community Member

    hi,

    VUQ-96951-517

  • jxpx777
    jxpx777
    1Password Alumni

    Hi, @auludag. Thanks for sending the report. I do see that 1Password was able to successfully connect from Chrome to 1Password mini. Here's what I see:

    Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8656006220):<OP4ExtensionHTTPConnection: 0x7f8655309950>] M webSocketForURI: | [ES4] Extension connected Chrome-Extension 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk / (null)'
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8656006220):<OP4ExtensionClient: 0x7f8656b0a660>] S didOpen | [ES4 0x7f8656b0a660] Connected 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:65086'
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8652dc2120):<OP4ExtensionClient: 0x7f8656b0a660>] S findExtensionProcessForPort: | [ES4 0x7f8656b0a660] Connected chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:65086: <NSRunningApplication: 0x7f8656ac5070 (com.google.Chrome - 9015)> launched 2017-04-26 20:19:29 +0000
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8652dc2120):<OP4ExtensionClient: 0x7f8656b0a660>] S verifyClient:satisfiesRequirement: | Extension client 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk' (<NSRunningApplication: 0x7f8656ac5070 (com.google.Chrome - 9015)>) passed validation
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8652dc2120):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'authBegin'
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8655321fe0):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'authContinue'
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8656006220):<OP4ExtensionClientHandler: 0x7f8656ace770>] S sendWelcome | Welcoming version 4.6.4.90 of Chrome-Extension.
Wed Apr 26 23:19:33 2017| 664001 [EXT:(Secondary Thread 0x7f8656006220):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'welcome'
Wed Apr 26 23:19:48 2017| 664001 [EXT:(Main Thread):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'collectDocuments'
Wed Apr 26 23:19:48 2017| 664001 [EXT:(Secondary Thread 0x7f86560fbc30):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'executeFillScript'
Wed Apr 26 23:19:48 2017| 664001 [EXT:(Secondary Thread 0x7f8656006a60):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'executeFillScript'
Wed Apr 26 23:19:48 2017| 664001 [EXT:(Secondary Thread 0x7f8656006a60):<OP4ExtensionClient: 0x7f8656b0a660>] S sendAction:payload: | [ES4 0x7f8656b0a660] chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk sendAction: 'executeFillScript'

    So, it looks like 1Password did indeed attempt to fill. At this point, I think we'll need a little more detail about the behavior you're seeing:

    1. Are you having this problem on every site or just a few? If it's just a few, can you send us the URLs?
    2. Do you still have the problem on this site if you save a new Login manually?
    3. Could you try creating a new Chrome profile with just 1Password's extension installed and see if it behaves better?

    If you're still having trouble, could you describe in as much detail as possible what steps you're taking and what's happening? For instance, "I attempt to sign in" is not as descriptive as, "I click the 1Password button in Chrome's toolbar and select the first Login in the list". Sometimes there is a subtlety to how you're interacting with 1Password that is the key to understanding and solving the problem.

    Thanks!

    --
    Jamie Phelps
    Code Wrangler @ AgileBits
    Fort Worth, Texas

    ref: VUQ-96951-517

This discussion has been closed.