- ago
In build 33 this error appears still
Is it related to the Dataset and list of symbols?
Does it affect the Live trading via Strategy Monitor?

0
373
10 Replies

Reply

Bookmark

Sort
- ago
#1
Is your order placement error rectified in WL8 B33?
What build of Binance extension are you running?
0
- ago
#2
I have just started the AUTO PLACE button, there are no signals from strategy yet.
Although, The order is being manually placed correctly in B33.

Binance extension is the last 1.44.0
0
- ago
#3
Not sure what you mean by "1.44.0", I'm asking about the WL Binance extension version. You can check it in the Home Page tool in WL8.
0
- ago
#4
Got the last one Build 19 )

Sorry,
I confused Binance application with extension for the WL soft)
0
Cone8
 ( 23.78% )
- ago
#5
Sync to internet time and try again.
If that doesn't help, it looks like there was fix applied recently to Binance.Net that we need to pull in.
0
- ago
#6
Done.

But message appears still

25.03.2023 15:01:18:406
Binance
Error calling Keep Alive: Illegal characters found in parameter 'listenKey'; legal range is '^[a-zA-Z0-9]{1,60}$'.
InvalidOperationException
Illegal characters found in parameter 'listenKey'; legal range is '^[a-zA-Z0-9]{1,60}$'.
at WealthLab.Binance.BinanceBroker.DestroyAutowireMapping()
0
Cone8
 ( 23.78% )
- ago
#7
Oddly, I'm not getting this error, but if Glitch is so inclined, we could push out Binance Build 20 and Kraken Build 16 (they share a component).
0
Glitch8
 ( 10.92% )
- ago
#8
Is the error interfering with any actual operations? But yes we can upgrade those components for the next release cycle.
0
- ago
#9
QUOTE:
Oddly, I'm not getting this error, but if Glitch is so inclined, we could push out Binance Build 20 and Kraken Build 16 (they share a component).


It would be great)
Thx
0
- ago
#10
this error exists still..
So please try to resolve it in the next build
0

Reply

Bookmark

Sort