Closed klepsydra closed 5 years ago
I have done this in my private copy. I am still trying to figure out how to refresh the token. https://github.com/Jamonek/Robinhood/issues/180
The changes are in the save
branch. It doesn't refresh the token
I have fixed the issue :)
Following our discussions in #22 and https://github.com/anilshanbhag/RobinhoodShell/commit/b9ec538890e7e2c760fa9c28c1eb45ac9d716081#commitcomment-33584861
we have a functioning solution for automation again. However, it generates tons of email. For every single invocation of shell.py, even to do no more than lookup my account balances--which I might do many times per day--it goes through time-delaying stages of generating yet another verification code, followed by a second mail "We’re emailing to confirm your recent login to Robinhood."
I was thinking, again in Robinhood/Robinhood.py, maybe around the lines
What parts of the
data
structure are essential to keep the login session alive (for the ~24hrs at least)?How about saving/exporting that into a .json or xml file,
Finally, attempting to read and import that file if exists next time RobinhoodShell is run, failing over to the regular existing login routine which regenerates a valid session?
I might try to hack it up, but it won't be pretty; I tend to resort to subshells and languages I'm more familiar with.