You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android only tells us that the password is for "com.android.settings", which is such a vague identifier that we have to ignore the autofill request entirely.
We could try removing that application ID from the permanent exclusion list and adding it to a new list of vague IDs. Applications on that vague list could be autofilled by a Kee Vault user but only temporarily - they will have to search for the desired password every time rather than us remember their preference in future like we do for most apps and websites.
The text was updated successfully, but these errors were encountered:
We could also see whether the Android settings app supplies the new autofill hint AUTOFILL_HINT_WIFI_PASSWORD = "wifiPassword"; and find a way to ignore all autofill requests for that app unless a field with that hint value is present. We'd probably have to supply some additional metadata to the entries containing that password though, so that the password can be supplied to more apps than just that one Android settings app.
First step will be to inspect whether Android even uses this documented hint value in their settings app.
Android only tells us that the password is for "com.android.settings", which is such a vague identifier that we have to ignore the autofill request entirely.
We could try removing that application ID from the permanent exclusion list and adding it to a new list of vague IDs. Applications on that vague list could be autofilled by a Kee Vault user but only temporarily - they will have to search for the desired password every time rather than us remember their preference in future like we do for most apps and websites.
The text was updated successfully, but these errors were encountered: