Suggestion: Better matching of app to login name
So on Android, when you are in an app and use the 1Password keyboard and you open the dialog to search for a login, it prefills the search with the app name and that almost never finds any results since Android app names are (usually) in the format of com.vendor.appname. It would be nice if 1Password could detect that format and prefill the search with only the appname instead of the full com.vendor.appname string, as this has the highest chance of finding a corresponding website login that you can use in the app.
1Password Version: 6.5.3.BETA-3
Extension Version: Not Provided
OS Version: Android O
Sync Type: Dropbox
Comments
-
Hey @Stanzilla. Thanks for the feedback regarding filling. The way we detect URLs for filling in apps is to reverse the app name and match it to something in your vault. This works when app vendors use package URLs similar to those on their websites. For instance, if you have a Login item saved with the URL https://twitter.com, we'll reverse that when trying to fill in an app. This means we're looking for com.twitter, which works in this case, as the Twitter app is com.twitter.android.
Some apps have package names that don't match up so in those cases, we won't be able to match and autofill. You can find a bit more on that, and how to create Logins for specific apps in my comment here:
https://discussions.agilebits.com/discussion/comment/313775#Comment_313775That said, we do understand that this method is imperfect. The good news is that we're currently reworking filling on Android, and should have some major improvements in that area soon. :)
0 -
Well the current solution just does not work well then. Here is an example:
app name is com.discord, 1Password does not find anything: https://i.imgur.com/YscTOoB.jpg
manually search for "disco", entry gets found: https://i.imgur.com/GBZGccE.jpg0 -
Indeed, since the website isn't named "discord.com", it doesn't match their "com.discord" app identifier. That's where "Browser Logins" comes in handy. Cheers! :)
0 -
Yeah that's why I suggested fuzzy matching. But I guess this will all be irrelevant come O anyway.
0 -
@Stanzilla: Indeed. It won't be a total win overnight, but certainly it will go a long way in time since it's supported by Google and the OS itself. Definitely check out my post here for an overview of where we're headed:
Beta for Android O and autofill?
0
