Sign and send transaction to MyNearWallet loses Promise<FinalExecutionOutcome>

[PierreLeGuen]

Describe the bug

SignAndSendTransaction for MyNearWallet redirects to MyNearWallet app causing the currently running app to lose state/memory of the wallet selector. This is causing issues when you want to act based on the promise result.

Steps To Reproduceå

Steps to reproduce the behavior:

1. SignAndSend any transaction to MNW
2. await on the promise
3. console.log(...) after the promise. The console log will never be triggered.

Error description

Expected behavior

Keep state and resolve the promise.

[kujtimprenkuSQA]

Hi @PierreLeGuen thank you for raising this issue.

This is the default behavior of browser wallets for transactions that attach any deposit or non-function-call actions because these transactions can not be signed with a limited access key and need to be signed with the full-access-key on the wallet.

[PierreLeGuen]

Understood, but how are we supposed to handle transaction approval after redirect on app side?

[PierreLeGuen]

Maybe you could open the sign page in an other tab/window and poll rpc for transaction status?

[kujtimprenkuSQA]

The wallet will add the transactionHashes query param into the callbackUrl of signAndSendTransaction(s):

For example something like this:
https://near.github.io/wallet-selector/?transactionHashes=6EgAkd1iKTzEdyx8E8cn7Kocv6Go24SCG6hED6BgBSii

In your dApp you could check the txStatus:

const provider = new providers.JsonRpcProvider({ url: network.nodeUrl });
const txHash = "6EgAkd1iKTzEdyx8E8cn7Kocv6Go24SCG6hED6BgBSii";
const accountId = "kujtimp.testnet";
const result = await provider.txStatus(txHash, accountId);
console.log("Execution Outcome Result: ", result);

[kujtimprenkuSQA]

@PierreLeGuen we're closing the issue for now, if you have any other questions feel free to re-open the issue.