-
Notifications
You must be signed in to change notification settings - Fork 85
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
Backwards Compatibility - Failed to get Transaction Result #666
Comments
Hi @austinkline. the SDK uses CCF encoded events, so your update to use json backwards compatibility mode is not registered. We're looking into how to address this for CCF. As a temporary workaround, you could use grpc directly to get the tx result, and leave the encoding version flag as its default (jsoncdc) |
Would there maybe be a way to switch to using JSON encoding instead of ccf temporarily? I'm not in control of that I don't think and am just using standard sdk methods |
it's currently not configurable. it's a simple change to switch it to jsoncdc if you wanted to try creating a custom build as a temporary workaround. just need to remove this line |
@austinkline I just tagged you can add the following to your client setup opts = append(opts, flowGrpc.WithEventEncoding(flow.EventEncodingVersionJSONCDC)) give that a try and let me know how it goes. |
Amazing! I'll give it a try tomorrow and report back |
Problem
Getting a failure while trying to parse transactions results using the crescendo preview build's backwards compatibility option
Steps to Reproduce
This gist reproduces the failure
Acceptance Criteria
This transaction should decode correctly
The text was updated successfully, but these errors were encountered: