You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DryRunApi.dryRunCall doesn't know what version to use when reporting the XCM objects back to the client.
The common implementation in pallet-xcm uses the latest one. If a client is not ready to interpret the newest version, it won't be able to read the output. I ran into this when testing locally.
All client-facing APIs should use versions that a client can understand (similar to the xcmPaymentApi.queryAcceptablePaymentAssets) so that clients won't break immediately if a chain upgrades.
The same might go for the dryRunXcm.
The text was updated successfully, but these errors were encountered:
The
DryRunApi.dryRunCalldoesn't know what version to use when reporting the XCM objects back to the client.The common implementation in pallet-xcm uses the latest one. If a client is not ready to interpret the newest version, it won't be able to read the output. I ran into this when testing locally.
All client-facing APIs should use versions that a client can understand (similar to the
xcmPaymentApi.queryAcceptablePaymentAssets) so that clients won't break immediately if a chain upgrades.The same might go for the
dryRunXcm.The text was updated successfully, but these errors were encountered: