-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
OKEX, OKX, getting 50113:Invalid Sign #4946
Comments
Hello. @arass What is the relationship of XChange library to this error? |
I am using xchange library to communicate. |
ok. |
Hi. I don't have the IP to post the code. Just letting you know of this bug. Thanks. |
Looks like related to #4779 |
Hi.
Getting a lot of
Caused by: 50113:Invalid Sign
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
at com.fasterxml.jackson.databind.introspect.AnnotatedConstructor.call(AnnotatedConstructor.java:128)
at com.fasterxml.jackson.databind.deser.std.StdValueInstantiator.createFromObjectWith(StdValueInstantiator.java:291)
Some stuff goes through. Other stuff dies like that ^^^.
This is how their API signs:
https://github.com/jane-cloud/Open-API-SDK-V5/blob/main/okex-java-sdk-api-v5/src/main/java/com/okex/open/api/client/APIHttpClient.java
Yes, I synchronized the server's clock with an atomic clock. Don't know if THEY have though.
The text was updated successfully, but these errors were encountered: