-
Notifications
You must be signed in to change notification settings - Fork 5
Error on login - "Device requesting login is not supported. Please try again from a secure context." #31
Comments
Thank you for bringing this to our attention @kumarpalsinh25, we are aware of the issue and are working to resolve it asap. |
Thanks @Ariflo for the quick response. Hopefully it will be resolved quickly as our production app users are facing difficulties in accessing app. |
@kumarpalsinh25 we've just pushed out a patch, give it a look and let us know if you're still seeing the issue. |
@Ariflo Thanks for quick resolution! |
Hi, I encountered the same error in the Flutter application by using loginWithSMS and loginWithEmailOTP method. I used it two hours ago. May I know any solution I could make to let my login success? |
@WeiJun0507 We are currently unable to reproduce the error described here as it has been resolved. For sanity check; have you tried force closing your flutter app, trying again? |
Yes, I did try several times. I only get the dependencies last Friday and I am sure that everything is correct because I could sign in with google provider. But I kept getting this prompt when I try to login with SMS or email |
@WeiJun0507, we can turn the device check off. Please contact our support via the widget in the bottom-right corner of our homepage on https://magic.link/ ? Thank you! |
sure, will do. Thank you |
We are facing this on a web app being accessed from different devices including Mobile and Laptops |
@sebastiantf You should be able to turn this security offering off on your Magic dashboard > Settings > Device Registration. Otherwise, please contact our support team via the widget in the bottom-right corner of our homepage on https://magic.link/ and we'll do our best to resolve your concern in a timely manner. |
I'm not able to log in with email OTP from my Flutter app. It is giving the below error.
I'm facing this error for the last 2 days, it was working fine before that. The code is the same.
The text was updated successfully, but these errors were encountered: