-
Notifications
You must be signed in to change notification settings - Fork 159
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
Call getAsset from TrustlineCreatedEffectResponse class #396
Labels
Comments
@przemyslawcelinski , thanks for report, yes, it looks like similar issue of mapping liquidity pools as asset from json into an sdk class, in this case TrustLineCUDResponse didn't map liquidity pool id and pass it to asset creation, I'm going through the effects and operations classes overall to get them all consistent. |
sreuland
added a commit
to sreuland/java-stellar-sdk
that referenced
this issue
Jan 6, 2022
…r all asset types(native, alpha4, alpha12, pool share). Fixed TrustlineCreatedEffectReponse marshaling to work when asset is of pool share type.
sreuland
added a commit
to sreuland/java-stellar-sdk
that referenced
this issue
Jan 6, 2022
sreuland
added a commit
to sreuland/java-stellar-sdk
that referenced
this issue
Jan 6, 2022
…ctor from TrustlineCUDResponse.
sreuland
added a commit
that referenced
this issue
Jan 10, 2022
…#398) Fixes TrustlineCreatedEffectResponse.getAsset() to work when asset is of pool share type.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version are you using?
Version 0.30.0
What did you do?
Call method
from
TrustlineCreatedEffectResponse
classOperation "change_trust" in block 38115883 with effect
trustline_created
https://horizon.stellar.org/transactions/a0a65ac4d71e44fc2be2bb071645a16a577efe6258e610214ab5dc60309c9798/effects which has
"asset_type": "liquidity_pool_shares" but assetCode and assetIssuer are null. So in Asset.createNonNativeAsset(assetCode, assetIssuer); is thrown NullPointerException
I added comment to closed issue: #374 (comment)
The text was updated successfully, but these errors were encountered: