Describe the bug
When calling getTransactionsWithPageInfo() without any of the optionnal parameters and incorrect credentials (for example privateKey set to "-----BEGIN PRIVATE KEY-----"), no error is thrown and the response is an empty list.
To Reproduce
Steps to reproduce the behavior:
const fireblocks = new FireblocksSDK("-----BEGIN PRIVATE KEY-----", "test");
result is { transactions: [], pageDetails: { prevPage: '', nextPage: '' } }
Reproduced on Sandbox account credentials so url set to https://sandbox-api.fireblocks.io
Expected behavior
the usual error message would be secretOrPrivateKey must be an asymmetric key when using RS256 expected
Ideally if the credentials are incorrect, an error would be thrown directly at step 1 when creation to fireblocks instance.
Describe the bug When calling
getTransactionsWithPageInfo()
without any of the optionnal parameters and incorrect credentials (for exampleprivateKey
set to"-----BEGIN PRIVATE KEY-----"
), no error is thrown and the response is an empty list.To Reproduce Steps to reproduce the behavior:
const fireblocks = new FireblocksSDK("-----BEGIN PRIVATE KEY-----", "test");
const tx = fireblocks.getTransactionsWithPageInfo()
{ transactions: [], pageDetails: { prevPage: '', nextPage: '' } }
Reproduced on Sandbox account credentials so url set to
https://sandbox-api.fireblocks.io
Expected behavior the usual error message would be
secretOrPrivateKey must be an asymmetric key when using RS256
expected Ideally if the credentials are incorrect, an error would be thrown directly at step 1 when creation to fireblocks instance.Version:
fireblocks-sdk
version:4.1.0