-
Notifications
You must be signed in to change notification settings - Fork 10
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
JSON deserialization of on-chain-metadata fails for array types #3
Comments
I just encountered the same issue so I had a look and grabbed the Json for that asset on the mainnet Here it is:
The error comes from the
The value for the "files" field does not fit in there. As far as I can tell, there is no integration test for it. The only one I can find has no onchainMetadata. If someone could give us the policy/name of an asset on the testnet with such a non-String filed that would be great. Or create one. |
Indeed |
@sourcelib-stack Possible to create a PR for this issue ? Otherwise, I will try to fix this. |
@satran004 @sourcelib-stack I can have a try, I found some assets on the testnet that I can use to make an IT for it along with the fix |
@satran004 I have it ready on a branch locally, I don't have the rights to push it. |
@bentaye Did you try to fork the repo and create the PR ? By default, PR permission should be there for a fork. |
@satran004 oh I see! PR is open now |
Can this be closed? |
Double check with @satran004 but AFAIAC I would say yes. And this one too #2 as it seems to me that it is the same problem |
This is already part of 0.1.1. |
Hi,
For some assets there are properties represented as arrays, example "images".
For those the assetService.getAsset(assetName); fails with this error:
Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type
java.lang.Stringfrom Array value (token
JsonToken.START_ARRAY)
Example call: assetService.getAsset("4c9f7d6c24ba8e2b12f3269ac38d706025e39a50a524afe6eaf79d955665676769656d6174653036323031");
The text was updated successfully, but these errors were encountered: