Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
1Password iOS Doesn't Recognize myHyundai App
I searched the forums but don't see a post regarding this app, so potentially I'm the only one having issues due to some odd setting or the like. Or maybe there's just not that many owners out there...
ChrisC1P
Moderator
ModeratorHi Mousit thanks for reaching out!
1Password integrates with iOS Password AutoFill in order to fill into apps on your iPhone. iOS is responsible for identifying fillable fields and for doing the actual filling, while 1Password provides the data that is to be filled.
When you find that 1Password isn't able to suggest a login item for an app, this will usually be because the “website” field of the login item doesn’t match the app’s “associated domain”. The associated domain is the website address which is claimed by that app for autofill purposes and is passed to iOS Password AutoFill when you tap the "🔑 Passwords” button. Here’s what to try:
1. Open the app in question.
2. Tap the Password field, then the “🔑 Passwords” button on the keyboard.
3. Check the Suggestions that appear in the pop-up.
If the “Passwords For” header also includes a website address, that’s the associated domain, and you should make sure that the “website” field of the Login matches this. If you search for the matching login, you'll see Always Allow alongside the option to Allow Once. Choosing Always Allow will add the app's associated domain to a website field in your saved login item, so it will be suggested next time.
If the “Passwords For” header just says “Suggested Items” with no address, then the app developers haven’t set an associated domain, and you’ll have to search for it each time, because neither iOS nor 1Password will know what to suggest. That would be something that only the app developers can fix, as it’s part of how the app is written. In that case, I’d advise contacting them through the “App Support” link in their App Store listing to give them your feedback.
Let me know how you get on with the above and I'll be here to help if you have any questions.
-Chris
Hi ChrisC1P, appreciate the reply. Though I'd note I already addressed your suggestion in my initial post. :)
I'd already determined that the app was not providing a website/domain of any kind, and even a "create new entry" in 1P based on the app didn't capture any identifiers, so the app clearly isn't providing a website/domain. I suppose my question primarily was whether 1P was able to make use of any other types of app identifiers beyond the website address (for example, the App Store App ID), but your reply addresses this as no. So sounds like there's not really anything to be done, other than poke at Hyundai which I doubt is going to get far but worth a shot.
Ah well, it's a small annoyance and yes, I can still autofill with manual search.
I suppose that might be a feature suggestion for the 1P devs. Perhaps if 1P could use other app identifiers (stored in the Login entry as another field) beyond just website domain, that might be handy. If that's even doable or secure, of course. I have no idea how mutable or copyable things like App Store App IDs are, for example, so maybe that's not a secure option.
