Am I right that some iOS apps will never play nice with 1Password?

Hi there @AntonioM

We do hear about iOS apps that don't work well with autofilling, and this is usually because:

• the app doesn't have an "Associated Domain", such as twitter.com for the Twitter app, and as such, neither iOS nor 1Password know what items to suggest, or
• the app actively blocks autofilling into its fields, or
• the app actively blocks copy/pasting into its fields, or
• similar anti-autofill measures, or a combination of the above.

If you find that apps are behaving like this, it's usually best to provide that feedback directly to their developers through their App Store listing, letting them know that their app isn't compatible with autofill. In particular, they should be following Apple's guidelines for iOS developers, found here:

☞ Password AutoFill | Apple Developer Documentation

Apps which don't follow those guidelines will usually not allow autofill, so in those cases you may have to copy and fill passwords into apps that don't work with 1Password.

Unfortunately, it is quite often banking and other financial apps which are the most reluctant to follow these guidelines, and as a result, cause the most difficulties in using autofill. We wrote An open letter to banks some time ago, and its main points are still relevant today.

We're optimistic about the future in this regard, and we'd like to think that banks and other financial institutions will see the benefit in not preventing their customers from autofilling strong random passwords. There's still resistance to it in places, but I'm personally hopeful we see a change in approach in the near future. :)

— Grey