Major issues: "1Password can't verify that Google Chrome...," followed by wrong password autofill

tambo

Those sneaky developers look like they may have made some initial headway into locating this. Now don't get your hopes up just yet. It may be entirely dependent on another fix being implemented or a myriad of other blockers. What it does mean is they have an idea, and they are working on getting it into the code base. From there, it will hit our nightly first. Provided all goes well, it will progress to our beta. Once again, provided all goes well it will make it to the production channel. * It could also be sent back to the start if it's not just right or perhaps causes an unforeseen problem somewhere else. Then the process repeats as needed.

tl;dr Hang in there. We have not forgotten about you. 🙂 Sometimes, a fix may take a period of time to get right. We'll continue to work towards a resolution for this problem.