Clément Creusot

Results 9 comments of Clément Creusot

Hi after long time of execution (4-5 hours maybe) i have the same problem than @bcfsunali ``` SECRET_PATH/node_modules/node-binance-api/node-binance-api.js:924 const queryParams = streams.join( '/' ); ^ TypeError: Cannot read property 'join'...

``` const pry = require('pryjs'); const Binance = require('node-binance-api'); dotenv.config(); const binance = new Binance().options({ APIKEY: process.env.APIKEY, APISECRET: process.env.APISECRET, test: true, reconnect: true }); async function main() { const newMarginSignal...

after 2 hours of execution i have this: ``` node websocketStayConnected.js rZqPps4xfHY0xBikrz1BL4UQSSGWbgm... [Function: userFutureDataHandler] { reconnect: [Function: reconnect] } rZqPps4xfHY0xBikrz1BL4UQSSGWbgm... [ 'Unexpected userFutureData: listenKeyExpired' ] [ 'Unexpected userFutureData: listenKeyExpired' ]...

@maxah Hi, This is a very occasional error, i have not find why `streams` is undefined. But I am still looking for a solution on this bug, I will keep...

@maxah Look my last PR. I make my reconnection manually, it's fix the error on `streams.join`.

The error of `streams.join` comes from here (if we have an error): https://github.com/jaggedsoft/node-binance-api/blob/7cbe4276c66519f55e228b84c8951a966310b92e/node-binance-api.js#L5224 @jaggedsoft what we can do ? `if (error) reconnect();` is good ?

And i think this line are false: https://github.com/jaggedsoft/node-binance-api/blob/7cbe4276c66519f55e228b84c8951a966310b92e/node-binance-api.js#L5228 It should be `url` instead of `fapi`, right?

I have made my own library now, but if i remember the probleme was here for `userFutureData`. https://github.com/jaggedsoft/node-binance-api/blob/8bad385c70e4a3f9252fc203f5500c1976d0c9ea/node-binance-api.js#L5277 https://github.com/jaggedsoft/node-binance-api/blob/8bad385c70e4a3f9252fc203f5500c1976d0c9ea/node-binance-api.js#L5292 `Binance.options.listenFutureKey` is the `stream` var and is undefined

https://github.com/jaggedsoft/node-binance-api/blob/8bad385c70e4a3f9252fc203f5500c1976d0c9ea/node-binance-api.js#L5276 Yes is that the error in apiRequest is not catch you need to catch it when append and rerty after few seconds