Update request headers passed to the latest versions about robinhood-node HOT 9 CLOSED

I used a debugging proxy to intercept the network calls being made by the app from my iOS device. Here is what the user-agent looked like:

User-Agent: Robinhood/5.32.0 (com.robinhood.release.Robinhood; build:3814; iOS 10.3.3) Alamofire/4.2.0 user:<my user hash?>

I will test this then make a PR if it works

from robinhood-node.

If you can intercept network calls that would be the best way to check the API version.

As I mentioned in other issues I moved to the UK and they still don't operate here so I can't check any further..

from robinhood-node.

@nodesocket

Hey looking for input and opinions on a similar npm module I just published that takes a reactive approach.
Let me know what you think.

from robinhood-node.

When I asked support about why some of my orders never get out of the placed state, they said they thought I was using an old version of the app. I can see that this header references iOS 7 and build 823 of the app. I think we need to somehow get the latest build number and reference iOS 10.3.

Here is what is currently referenced in the wrapper:

'User-Agent': 'Robinhood/823 (iPhone; iOS 7.1.2; Scale/2.00)'

from robinhood-node.

@swimclan Hope you get this working!

from robinhood-node.

@qrpike I think he already did, as he submitted the PR and I've merged it. Give it a go with the latest version v1.0.0

from robinhood-node.

Are these headers necessary? I've been testing by creating limit orders in after hours (-9am & +6pm) and was able to go from unconfirmed to queued and then cancelling afterwards.

from robinhood-node.

I was attempting to send requests without the api version number and was getting an error. But this may have changed since then.

from robinhood-node.

Yeah it has, I created a test limit order and it filled just fine without these headers.

from robinhood-node.