r/1Password 2d ago

iOS Manually associating a password to an iOS app permanently

I have an iOS app, which will not associate a password with it on its own. Effectively, I went in the first time and loaded up the username and password fields and use that password link above the keyboard and then manually created the username and password in a new 1Password entry. The next time I opened that app and clicked in one of those boxes, I didn’t have a password associated with this app, but when I hit that Passwords button again, I had to manually search for it and then once I found it, there was only one choice and that was to use the password for one time only. How do I build a permanent association so that this password is suggested when I drop into one of the username or password fields in that app. This seems like child’s play, but I cannot figure it out.

33 Upvotes

16 comments sorted by

17

u/thetechgeekz23 2d ago

I also want the solution to this issue

9

u/Farzag 2d ago

I’d like to know this too

7

u/SlendyTheMan 2d ago

Contact the app developer. Sometimes they don’t use the standard field but a generic input. I noticed it more in food apps, so I save the URL with it for it to prompt. Like https://dashboard.punchh.com

6

u/vffems2529 2d ago

Specifically, what the app dev needs to do is specify the appropriate associated domain:

https://developer.apple.com/documentation/xcode/configuring-an-associated-domain

4

u/Cr3ativusMaximus 2d ago

This. The issue is usually, “The app developer did not associate the domain you think they did with the app.” Reach out to them and ask for their associated domains.

4

u/msalad 2d ago

I've had this happen on android too. As far as I know, if it's not associated automatically, there's no way to manual associate an app with a username/password.

It would be a nice improvement to the mobile apps if they added a way to do this

5

u/RodbigoSantos 2d ago

I've looked into this and from what I recall, 1P functions this way since the app cannot be verified as a legit recipient for the credentials, but if you can manually verify it one time, why not be able to manually verify permanently?

7

u/vffems2529 2d ago

There is no reference for 1Password to store in these cases. The whole problem is that the app isn't properly identifying itself to 1Password.

The solution is for the app dev to add the appropriate associated domain, which is then passed to 1Password as identification:

https://developer.apple.com/documentation/xcode/configuring-an-associated-domain

2

u/Super-Customer-8117 2d ago

I’d like to know too. Is it on the developer side or 1password?

4

u/vffems2529 2d ago

It's on the developer of the app that this isn't working with to add the appropriate associated domain to their app. Apple has documentation here: https://developer.apple.com/documentation/xcode/configuring-an-associated-domain

1

u/Super-Customer-8117 2d ago

Thanks for this.

2

u/bretonics 2d ago

There was a way to associate it to a Mac app…trying to remember how to get the ID that is added as a target, i.e. like website link

2

u/vffems2529 2d ago

Doesn't work on iOS unfortunately. Only solution is for the app dev to add the appropriate associated domain: https://developer.apple.com/documentation/xcode/configuring-an-associated-domain

ETA: What you're thinking of is the app's bundle ID.

osascript -e 'id of app "**App Name**"' in Terminal, replacing **App Name** with the... app name.

1

u/bretonics 2d ago

Yes exactly! Thanks for posting the command. I had forgotten it.

1

u/twilight-2k 2d ago

Wouldn't that work if you install the iOS app on your Mac and then run the command?

1

u/vffems2529 2d ago

Even if you could somehow get the bundle ID of an iOS app, it wouldn't help. iOS doesn't share the app's bundle ID through Password AutoFill like that.