Recently, something appears to have changed in the latest version of Chrome for Android that causes all users who try to log in from an icon on their home screen (that was added using the ‘add to home screen’ functionality) to receive an ‘Oops, something went wrong error’. The logs don’t give me anything specific besides that it’s probably a cookie error. Has anyone experienced anything simular? The app is built using the passport-auth0 demo code for nodejs, using lock 9.1. It has worked flawlessly up until about a month ago. Everything still works if going to the apps url directly from Chrome for Android (as well as on a desktop pc, etc).
I’m getting the same error. Last week I would get the same error when using IE11 through BrowserStack, but that seems to work now.