[Timelock order(Binance)] Error: msg should not be nil

[roy1210]

Hi @hewigovens @catenocrypt

Describe the bug
Fails broadcasting timelock_order.
Error: msg should not be nil will return after run sendRawTransaction:

          const request = context.wallet.walletconnect._formatRequest({
            method: "trust_signTransaction",
            params: [
              {
                network: NETWORK_ID,
                transaction: JSON.stringify(tx),
              },
            ],
          });
          window.mywall = context.wallet.walletconnect
          context.wallet.walletconnect
            ._sendCallRequest(request)
            .then((result) => {
              window.result = result;
              console.log('Successfully signed timeLock msg:', result);
             
             // Error: msg should not be nil 
              binance.bnbClient.sendRawTransaction(result, true)
                .then((response) => {
                  console.log('Response', response);
                  setSending(false);
                  setVisible(false);
                  getBalances();
                })

As per successfully running freeze_order reported in this issue, sendRawTransaction(result, true) should return the result of POST transaction to the Binance chain. The problem is returning Error: msg should not be nil when I sent timelock_order.
Kindly please help to investigate why such an error returns since created tx (JSON format's) based on WalletCore's proto messages.

Thank you for your support !! :D

To Reproduce
Please feel free to clone this branch. Timelock logic is in here

demo: https://beptool-fork-fm856hstj.vercel.app/

Expected behavior
binance.bnbClient.sendRawTransaction(result, true) returns 200.

Screenshots
tx values, request, and error message.

Additional context
I'm using @walletconnect/client:^1.3.1 as per guideline in the latest Docs

[hewigovens]

let's track this issue here: trustwallet/developer#148