Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
1P 8 does not work with Fidelity Android app
The fidelity investment app produces a version of gboard with no top bar where 1password would typically go. I am also not prompted to autofill username or password when I have "display autofill prom...
Hey Dunecat 👋
I want to note that Fidelity recently posted in their subreddit that it's an issue on their end that they're working to resolve, that said, I'll still add you to our list of affected customers in case there's anything we can do on our end.
Same issue with Fidelity app and Bank of America app using the latest production version of the 1passwd 8 app on my Google Pixel 7 running latest Android OS and all app updates. No special custom stuff on my phone. Using standard keyboard that came with my pixel. Tried uninstalling both apps and reinstalling them. All my other apps seem to work fine so far. They both detect 1passwd when on the password field and autofill it, but the login field doesn't autofill. When I click on the login field and choose autofill nothing gets filled in.
patrick
1Password Team
1Password TeamHi! Android developer here. We're definitely aware of these issues and we want to do a better job at targeting these popular apps that don't fill quite right.
I've got a band-aid fix for the Bank of America issue that will be present in Android stable release ~January 20th. And I will see about getting something out for Fidelity in the near future.
The issue with both of these login screens is that they're missing data that we key in on to identify fields. For some reason this happens a lot with banking/financial apps.
For Bank of America, they clearly identify their password field, but they offer no hints for their username field. In order to work around that, a developer has to manually parse the autofill request and figure out some other way to identify a username field, and then add custom logic for just that app, and also must be sure that the fix doesn't generate a bunch of false positives after the user has logged in (you don't want an autofill suggestion when you're trying to operate a search bar or something).
The band-aid solutions are brittle and there's no guarantee that Bank of America won't ship an update the next day that breaks autofill again, and there are some apps that simply can't be bandaged because there's just nothing to grab on to when we're parsing a screen and looking for the right fields to fill. But there's definitely room for improvement in targeting these popular apps that have in some cases been broken for years.
Hey Patrick,
Thanks for replying. It makes sense that these fields are ever changing - with so many things that could go wrong, the job of info sec becomes increasingly difficult. The idea is to make it much harder for bad things to happen, but that sometimes hinders the good things that could happen.These aren't the only apps I have trouble with - a lot of fields in my browser won't fill either. I use Brave, so that might be part of the issue, but I do have an idea for a solution.
When clicking a field that could be populated by 1Password, the options generally show up right above the keyboard. You can select which credential you would like to use - which is very convenient. If you long press one of the options, the app comes up, but for me, nothing loads - it's just a blank 1Password app... so I have to exit and retry. It might be cool if you could make a setting in 1Password, where if you long press the option, the password is copied to the clipboard. Then you can simply paste the password. I think the username is often easy enough to type.
Perhaps this is already possible and I simply haven't found it. If it is, please let me know! And if you need further clarification on my idea, feel free to reach out. I love developing things and would be delighted to help.
