Chrome Extension showing "No matching items found"
These are the steps I took to migrate to the Windows beta on my work PC, running Windows 7:
- Uninstall 1Password 4 under Add/Remove Programs
- Installed 1Password 6 following these instructions https://discussions.agilebits.com/discussion/64591/help-us-welcome-1password-6-to-our-windows-family (I had to reboot as part of this)
- Removed extension in Chrome
- Added the extension in Chrome after selecting Enable Betas https://agilebits.com/onepassword/extensions
However even when the beta app is unlocked, the extension can't find anything. I'm assuming this is a combination of (a) all of my items having been migrated to my Family vaults or (b) some stale stuff from 1Password 4 floating around, but I'm not sure how to diagnose further.
1Password Version: 2016.6.802d
Extension Version: 4.5.7.2
OS Version: Windows 7
Sync Type: Family
Comments
-
Hi @UltraNurd,
There is no need to uninstall 1Password 4, in fact, we strongly do not recommend this at all. 1Password 6 beta is a beta app with the beta risks, you must not rely on it for anything. In fact, we may require you to migrate your data again later when 1Password 6 comes out.
No matching items foundmeans the extension is connected but there's a bug where the URL must be 100% perfectly the same between the browser's address bar and the Login's saved URL.For now, switch to the 1Password 6 beta app, select the Login item you want to use and click on Browse on top right. It should then open the site in your browser and it should then fill.
0 -
Thanks, I'll try that.
This isn't my primary machine, so it's more that I was hoping for a bit more integration than the web app for Family. (I had migrated my vaults before realizing that the Windows version didn't yet support Teams/Family.) Normally I only remote into this machine from my Mac running 1Password 6, so I just copy/paste logins from there.
0 -
Hi @UltraNurd,
That's great. Do let us know if you can get it to work with the Browse option for now.
We are working on an update to fix the URL matching issue but it will take a bit of a time.
0 -
@MikeT I don't seem to have a browse option. I confirmed that for websites where the item URL matches exactly (e.g. amazon), I do see the login items I expect. In terms of URL matching, http vs. https matters, yes?
Somewhat related issue: there's no UI feedback from the extension that the main app is locked, it just seems like clicking does nothing.
0 -
Hi @UltraNurd,
It's on the top right of the details view for the Login items:
In terms of URL matching, http vs. https matters, yes?
Yes, including the subdomains and the directory paths. It should be flexible with the subdomains and ignore the paths but it is not doing that yet.
Somewhat related issue: there's no UI feedback from the extension that the main app is locked, it just seems like clicking does nothing.
Correct, the extension is really basic at the moment as we're in the process of building a new extension view for the browsers. Right now, all it does is fill, present a menu of Login items when there are more than one to fill and to inform there's nothing found for the site.
0 -
@UltraNurd there was a little update few moments ago, from now on when app is locked and you are trying to use it from browser - it will pop on top to unlock it. One little step toward better future :) Thanks for the suggestion
0 -
@SergeyTheAgile nice to feature :D Can't wait to see more from the new Browser Integration :dizzy:
0 -
We can't wait either, a lot of stuff we have coming for you guys.
0 -
@SergeyTheAgile - I've tried clicking on the browser extension when the app isn't running, and that still brings up the looking for 1Password helper dialog in the browser. I wonder if you can confirm that the new unlock feature only works if you have the 1Password app running?
Also, I'm having a bit of trouble getting this feature to work perfectly - it sometimes takes multiple clicks on the browser extension before the 1Password beta app comes to the top. I'm using 1Password beta 2016.6.901d with Firefox 47.
0 -
@pbryanw yes, that fix was a small one, basically "request Windows to put locked 1Password window in front". It doesn't start app (yet) and it's far from perfect, because we can only request to bring window in front, Windows has a dozen rules to deny that request (we have some ideas how to overrule Windows on that).
0 -
@SergeyTheAgile - Thanks for getting back to me and I appreciate your explanation - sounds like this feature will only get better in the future.
0 -
Yep, it will get much better soon. We've only implemented the smallest piece needed to start the browser integration for limited Login filling support. There are a lot of pieces still left to implement and once it is all implemented, it should be identical to the full 1Password mini (OS X) experience everyone wants to see.
0 -
@MikeT Going back the the Login feature. Where to you put the URL? When I edit the login, I only have the option to fill in the following data fields: , , . My 'Browse' button is greyed out. Am I missing something?
0 -
Sorry, I didn't realize the field was set for html.... the data fields I was referring to were: Name of Login, username, and password. No field for website or URL.
0 -
Nevermind, I seen a post from @brenty that explained it was removed to update the item editor.
0 -
Hi @dixie_tech,
Yep, we are working on a new item editor that will restore the URL editing soon. We've disabled it in the current editor because we found a bug related to the URL field and we're working on fixing it in the new editor that's coming out soon.
0 -
Just in case anyone comes across this thread I'll note that doing what OP did (uninstall 4, install 6, extension broken) isn't fixed by installing v4 again. I get nothing but the error message " no matching items found, click to open 1password".
0 -
Hi @Dan1121,
It's not an error message as mentioned in the follow-up post.
No matching items found message means the 1Password 6 Beta cannot find any Login items in your 1Password database that matches the URL in the browser tab you're on.
There are a few reasons:
- First, we are working on improving the URL algorithms but if your saved URL doesn't match the same subdomain as the login's page in the browser, it won't match, thus the message No matching items found. A future update is coming to make sure subdomains are included in the search and ranked properly.
- Many folks have imported their data for the first time in 1Password 6 and we found that some of the Logins did not have a URL field saved, which explains why 1Password cannot find it. Once the Login item is edited to have the URL, it works fine.
- 1Password 6 Beta does not yet have a full extension view, which means clicking on the 1Password icon when you're not on the site's login page such as the empty tab or search page will result into the No matching items found message. There is no extension menu to see all of your data yet, this is coming in a future update.
0
