It was ultimately an issue with the SDK, which is now fixed. @dev.tringuyen @mazzocchitomi @sudarsangp can you try again?