@kaltenf@pododesk-operations Would it be possible to provide a snippet of code from your authentication request (remove any sensitive information)? And is this on Lock v11.9.1 ?
Hey Kim, thanks for you offer to support. As I am not a developer I would need to ask you for some support on how to gather what you asked for
Thanks, Jens
Hi!
I have same problem with auth0js. Autofill is not working on iOS (both Chrome and Safari) and my customer isn’t happy about that.
This is my code:
Since I have to customize “Login With Facebook/Google account” buttons, I used Auth0.js (v9) instead of Lock. I changed my code to use Lock as your suggestion this morning, but autofill is still not working.
This is my code:
Hi!
I think i’ve got the same issue since we upgrade auth0 lock from 11.0.1 to 11.12.1.
We use splash to emulate client navigation and use javascript to fill login and password.
On submit all field are reseted.
Hey,
I have added the allowAutocomplete: true to our lock configuration but still the credentials are always wiped out from the iput fields when submitting or switching from email to password.
Sorry for such delay in response but it’s quite busy out here and we have limited bandwidth as of now. Terribly sorry and thanks for understanding!
I did some research and it seems like there were also other users having problem with this when updating their Lock version. I pinged repo maintainers about that and they asked me if you can open appropriate issue in the repo so they can get into this.
Sorry for such a long delay in response. Have you guys tried this option from Lock?
- allowPasswordAutocomplete {Boolean}: Determines whether the password field will allow autocomplete; setting this to true is required for password manager support and to avoid many cases of adverse behavior. Defaults to false.