I am seeing the email connection across multiple auth0 accounts suddenly return a “We’re sorry, something went wrong when attempting to sign in” to Lock Passwordless.
The Chrome console is showing a couple of warnings and a CORB blocked file:
Failed to load https://buro9.eu.auth0.com/user/geoloc/country: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.lfgss.com' is therefore not allowed access. VM763:1 Cross-Origin Read Blocking (CORB) blocked cross-origin response https://buro9.eu.auth0.com/user/geoloc/country with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details. (anonymous) @ VM763:1 getRequest @ lock-passwordless.min.js:9 init @ lock-passwordless.min.js:9 Reqwest @ lock-passwordless.min.js:9 reqwest @ lock-passwordless.min.js:9 a.getUserCountry @ lock-passwordless.min.js:14 f @ lock-passwordless.min.js:13 a @ lock-passwordless.min.js:13 auth0signin @ (index):1104 authSignin @ (index):1108 onclick @ (index):80 (index):1 Failed to load https://buro9.eu.auth0.com/passwordless/verify: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.lfgss.com' is therefore not allowed access.
But I do not believe that is the root cause.
The network tab shows that the
start request worked fine and return JSON, but that the verify request returned
text/plain and a body of
Is this an update in the email connection that the old version of lock passwordless then fails on… a regression of sorts?
And if so, has lock finally been made passwordless friendly?
And is anyone else seeing this or knows how to resolve it?