Forum Discussion

eFlat7's avatar
eFlat7
New Contributor
5 months ago

Browser Relaunch Breaks Autofill via Shortcut (until....)

Since I usually get response from devs or 1P reps, I'm pretty much just writing this to them. Although, certainly anyone else is welcome to chime in! (It is a community after all, and I'd love to know whether I'm the only one this is happening to.)

I've been experiencing an issue for a while now – longer than I should have let go by without reporting. The fact that I haven't found anyone else that has reported the same issue as me, probably means it's something on my end, I'm sure. But anyway, here's the situation.

Every time I quit and relaunch the browser (This is true, at least, of both Chrome and Edge on MacOS), the autofill via the hotkey no longer works. It DOES still work via the extension icon in the toolbar and via the icon in the fields themselves, just, not the autofill via hotkey. When you hit the cmd+\ you simply get the 1Password search box with no results. Normal expected behavior should be to either (1) autofill the fields, or (2) if multiple matches exist, populate those matches in the popup box for you to choose one.

This is reproducible and predictable on my end. It happens every time. It has been occurring for multiple versions of 1P, multiple versions of the browsers, multiple versions of the extension. I do not recall having this problem before upgrading to Sequoia, but beyond that, I cannot identify exactly when this began, only that it has been occurring for a while now.

Why have I drug my feet in reporting it? Well, frankly, because I am convinced it must be on my end if nobody else is having the problem... but also, because it's relatively easy to correct. You see, when you hit the cmd+\ shortcut and get that empty 1P box, just type in anything... Anything at all will do. Usually, I just choose the website I'm trying to autofill, but you literally can choose any login entry whatsoever at all to attempt to autofill. You'll get the popup that says: "1Password can't verify that Google Chrome should have access to your "1Password Account" item. Do you want to fill it anyway?" and Allow Once, Allow Always, or Cancel. I ALWAYS choose cancel because I don't want to create app links to my logins for browsers (that's bananakers!) But as soon as I do that..... it all works from that moment forward. No issues whatsoever. No problems. None.

It's almost like some link is not getting finished connecting when the browser launches, and it needs that extra kick to finish that bridge connection, and as soon as it gets it – even by clicking "Cancel" – it all works from that moment on (at least.... until I have to relaunch the browser again for an update or a reboot, etc.). Fortunately, I go weeks without relaunching my browser, so I don't have to do it but maybe once or twice a month on average, but like I said, it is predictable. 

I did take a screen recording to show you exactly what happens. I can send that via Dropbox or email or however you'd like to receive it (if you even want it).

Normally I put my OS and Browser and App and Extension version here, but, honestly, it's irrelevant. This issue has persisted and I am currently up to date on all of the above and it continues to persist. Cannot wait to hear what simple solution I've overlooked (as is often the case) or what toggle switch I've accidentally switched off (more often the case) hahaha! Thanks 1P team!

2 Replies

  • Hello eFlat7​! 👋

    I'm sorry for the delay in responding! We had some more folks away for some summer time off here and there over the last month but hopefully things will get back to their normal speed now. 

    I'm happy that my colleague over on the email side was able to help identify the issue. It does sound like you're running into a known issue with Universal Autofill and Chromium-based browsers like Google Chrome. Our team is investigating. 

    For the time being, filling your login in Chrome using the browser extension's suggestions on the page instead of Universal Autofill (Command-Backslash) is the best workaround. Let me know if there are any other questions that I can help with for now. 

    -Dave

    #37118

  • eFlat7's avatar
    eFlat7
    New Contributor

    Alrighty, well..... since it's crickets here..... I reached out to official support channels. Just wanted to drop an update to others who may be experiencing the same issue as me because.....

    Ta'da!!! Turns out, it's not me after all!!  The response I received from support said:

    "After reviewing the information you've provided and watching your screen recording, I can confirm that you're experiencing a known issue our development team is investigating."

    "The issue is related to the Quick Access feature, which doesn't provide suggestions correctly in Chromium-based browser."

    So, on the one hand, I'm happy to know I'm not alone, I'm not crazy (well, at least this issue isn't proof of me being crazy, I'll say), and it wasn't on my end this time. On the other, I'm really surprised not to see anyone else reporting this on the community forum. Perhaps I'm just a dinosaur who thinks these things are still more active than they are? Haha. I dunno! 

    Anyway, they're aware, there just isn't a fix right now. So, what I described works (choosing something from the search box and hitting cancel) and support also said choosing "Allow Once" would also work, but agreed that choosing "Always Allow" would be the incorrect choice in that situation.