Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getResult is always false #138

Closed
bai-xuan opened this issue Sep 22, 2024 · 7 comments
Closed

getResult is always false #138

bai-xuan opened this issue Sep 22, 2024 · 7 comments

Comments

@bai-xuan
Copy link

use :

apiWrapper.freezeBalanceV2

The return is normal, but getResult is always false:

transactionExtention.getResult().getResult()

@angrynurd
Copy link
Contributor

use :

apiWrapper.freezeBalanceV2

The return is normal, but getResult is always false:

transactionExtention.getResult().getResult()

hi, @bai-xuan
could you check what the response_code it return?
usually, when the field 'result' is true,the field 'response_code' will be SUCCESS.
but when getResult() is false,getResonseCode() will be like ‘OTHER_ERROR’ or other error codes.
below is the codes of this function in the server side.
image

@bai-xuan
Copy link
Author

image

@angrynurd
Copy link
Contributor

@bai-xuan
I just walked through the codes of apiWrapper.freezeBalanceV2.in trident(client side), the most important thing function freezeBalanceV2() only does is to construct the transaction;
so, when invoking function freezeBalanceV2, the result field represents whether the transaction was constructed successfully or not.
Obviously, It is a bug here.
btw,if you invoke apiWrapper.freezeBalanceV2 and does not throw any exceptions , it means the tx construct is successful and you can broadcast the tx to the chain;

@bai-xuan
Copy link
Author

As you can see, no exceptions were thrown, so I conclude that this is a bug.

@bai-xuan
Copy link
Author

bai-xuan commented Sep 23, 2024

The returned data can be broadcast normally and successfully, but getResult is always false:

@angrynurd angrynurd mentioned this issue Oct 9, 2024
@angrynurd
Copy link
Contributor

fixed in version 0.9.1.

@bai-xuan
Copy link
Author

Received, currently reviewing. Thank you for handling it. If there are any follow-up issues, we will communicate again.

@lvs007 lvs007 closed this as completed Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants