quadrigacx fetchBalance error

quadrigacx fetchBalance method error

• OS: MacOS
• Programming Language: Node 8.4.0
• CCXT version: 1.10.456
• Exchange: quadrigacx
• Method: fetchBalance

await quadrigacx.fetchBalance()


(node:59361) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'id' of undefined
(node:59361) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[ChenLi0830]

Hi @kroitor Thank you for the detailed answer! It turns out the error message I saw came from not handling a caught error properly as shown below.

const handleError = (e, exchange) => {
  console.error(e, exchange.id) <--- trying to access id of this string...
    ...
}

(async () => {
  let exchange = 'quadrigacx'
  try {
//    await fetchAll()
    await fetchBalance(exchange)
  } catch (e) {
    api.handleError(e, exchange)
  }
}) ()

I wasn’t even thinking about this part, that’s why I totally missed it and didn’t paste it into the snippet. Anyway, I am really glad for your help. Merry Christmas!

[kroitor]

Is there an easy way to tell what is required when initiating the exchanges?

Yes. There’s a .requiredCredentials property on each exchange, you can see what is required and what is not.

But, in fact, there’s also the .checkRequiredCredentials() function. Those two things are parts of a mechanism that was implemented as a layer of protection against signing with empty credentials or against forgetting to set them properly, so, I don’t really understand, how you managed to get around that protection…

That .checkRequiredCredentials() function gets called internally and it throws an exception when you forget to set any of required credentials. The commands and the results are shown on the screenshot below:

As you can see from the above screenshot, it literally throws an exception, if you forget to set the uid. But because you did not paste the entire code to reproduce the problem, it’s hard to tell, why the above protection layer didn’t work for you as designed.

Please, never paste one line of code. And don’t paste more than 20. You should paste the minimal snippet that I can copy and launch without wasting too much time to recreate your setup. If you put a snippet of 5-10 lines, a full short program, that demonstrates your problem from the very instantiation, up to the breaking point, and if it can be launched right away – you will get your help and answers 10x faster, believe me. If you do that, most often you will find the problem yourself very quickly and will not need any help. The code snippet should only reproduce the problem and should not have anything unnecessary. However, it should be complete. So, if you want somebody to help you, make it easy for them to help you 😉 Cheers!