-
Notifications
You must be signed in to change notification settings - Fork 504
Login issue - Unable to log in with provided credentials #555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This should help: |
I called and complained all day. There working on it now at robinhood they screwd up mfa and they have to re code it now my account got bricked into device access req. Witch messed up Robinstocks. They have to allow you to remove it I said it bricked one of my accounts. In the documentation from there ai chat bot. Says. You have to remove the phone attached to the account to reset the system |
Looks like they made some changes back at robinhood is it working yet ? |
So it's still not working. Till we have a workaround it seems robinhood has other ideas. We can't build on non reliability I've started moving to ibkr broker there the best I heard I will program my system with there api also and have a choice so we still retain robinhood if they make a better script some day. What jerks |
To revert the problem you need to have robinhood remove the phone number from the account. Then restart the process over donot enable device aprovals |
it appears that SMS Authentication is now being redirected to Device Approval method. 😡 and what is with all the spam in our Issue tracker over the past few days. 😩 |
Hi all,
My access token must have expired today and the 'robin_stocks' module will no longer let me log in, despite being able to on to the website and iOS app with the very same credentials.
I've tried the latest package and have also tried with a TOTP set up, to no avail, as well as workarounds that others have posted.
I'm assuming something has changed on the server side.
Has anyone else had this issue and have been able to get around it?
The text was updated successfully, but these errors were encountered: