Flutter ReownAppKitModal: Trust Wallet crashes when trying to connect and make signature request

[usdtbanc]

SDK Affected

I am reown_appkit: ^1.5.0

Describe the bug

When trying to connect and making signature request using Trust Wallet, as soon as I click "Sign", the app crashes.
If I just connect, the connect pop up appears and it gets connected without any issue but when trying to connect with signing request at the same time, the app crashes.
I think it's because the connect popup window gets hidden by signature request popup hence causing the app to crash.

To Reproduce

Just try to connect Trust Wallet using SIWE config so that the signature request can also be made

Expected behavior

First, connect popup should show and once connected successfully, signature request popup should come.
It works fine with metamask and this is how it works (connect request, go back, click sign, signature request, session created)

Reproducible code

final appKitModal = ReownAppKitModal(
        // ignore: use_build_context_synchronously
        context: context!,
        disconnectOnDispose: false,
        projectId: web3WalletSetting?.ownAppKitProjectId,
        includedWalletIds: web3WalletSetting?.wallets!
            .map((item) => item.walletAddress)
            .toSet(),
        featuredWalletIds: web3WalletSetting?.wallets!
            .map((item) => item.walletAddress)
            .toSet(),
        metadata: PairingMetadata(
          name: web3WalletSetting!.metadataName,
          description: web3WalletSetting!.metadataDescp,
          url: web3WalletSetting!.metadataURL,
          icons: [web3WalletSetting!.metadataIcons],
        ),
        siweConfig: SIWEConfig(
            signOutOnDisconnect: true,
            signOutOnAccountChange: true,
            signOutOnNetworkChange: true,
            signOut: () async {
              return true;
            },
            getNonce: () async {
              try {
                await getWeb3Nonce();
                if (fetchWeb3NonceModel?.nonce != null) {
                  return (fetchWeb3NonceModel?.nonce ?? '');
                }
              } catch (e) {
                Utils.showLog("Connect Wallet error: $e");
                Utils.showToast("Connect wallet failed. Please try again.");
              }
              return '';
            },
            getMessageParams: () async {
              return SIWEMessageArgs(
                domain: Uri.parse(web3WalletSetting!.signDomain).authority,
                uri: web3WalletSetting!.signDomain,
                statement: web3WalletSetting?.signStatement,
                methods: web3WalletSetting?.signMethods!
                    .map((item) => item.name)
                    .toList(),
              );
            },
            createMessage: (SIWECreateMessageArgs args) {
              return SIWEUtils.formatMessage(args);
            },
            verifyMessage: (SIWEVerifyMessageArgs args) async {
              final chainId = SIWEUtils.getChainIdFromMessage(args.message);
              final address = SIWEUtils.getAddressFromMessage(args.message);
              final cacaoSignature = args.cacao != null
                  ? args.cacao!.s
                  : CacaoSignature(
                      t: CacaoSignature.EIP191,
                      s: args.signature,
                    );

              String projId = web3WalletSetting?.ownAppKitProjectId ?? "";
              bool valid = await SIWEUtils.verifySignature(
                address,
                args.message,
                cacaoSignature,
                chainId,
                projId,
              );

              if (valid) {
                await verifyWeb3Signature(
                    address, chainId, fetchWeb3NonceModel?.nonce);

                if (verifyWeb3SignatureModel?.isValidMessage != null) {
                  return (verifyWeb3SignatureModel?.isValidMessage ?? false);
                }
              }

              return false;
},
            getSession: () async {
              try {
                await getWeb3Session();

                if (fetchWeb3SessionModel?.address != null) {
                  return SIWESession(
                      address: fetchWeb3SessionModel!.address,
                      chains: [fetchWeb3SessionModel!.chainid]);
                }
              } catch (e) {
                Utils.showLog("Connect Wallet error: $e");
                Utils.showToast("Connect wallet failed. Please try again.");
              }
              return const SIWESession(address: "0x123", chains: ["1"]);
            }),
      );

      await appKitModal.init();

Smartphone (please complete the following information):

• Device: Android
• API Version: 35+

[linear]

APKTN-703

[usdtbanc]

Nobody is facing this issue? Works fine with Metamask but Trust Wallet crashes,
I am thinking to revert to old version (WalletConnect) package where I believe I might get some support

[ignaciosantise]

hey @usdtbanc sorry for the delay, if it works well on MetaMask but not on Trust, its probably an issue on Trust Wallet, not on the SDK. Are you using the latest version of Trust? Does it crash on iOS and Android versions?

[usdtbanc]

Hi, thanks for your response. Yes it works fine on the Metamask.
And I am using the latest version of Trust Wallet as well. I believe, in trust wallet, the connect pop-up is being overwritten by signing request pop-up and since it's not connected yet but the signature is sent for approval, it crashes.
In Metamask,

1. Metamask asks to connect
2. I go back to the app
3. the sign button appears, I click it again
4. Metamask asks to sign
5. I go back and I am now connected, with signature, session etc.

[usdtbanc]

The purpose to write here is even if that's an issue with Trust Wallet itself, there might be a workaround where I can ask the user to connect first, and upon connecting successfully, I prompt for the signature.
Simple connecting is not an issue by the way.

Any help would be highly appreciated, thanks

[ignaciosantise]

@usdtbanc that's how the flow works now. We first send the connection request, and after the user connected, we sent the sign one

[usdtbanc]

yes this is it is exactly when using Metamask

When the same is called for Trust Wallet, the trust wallet app crashes as soon I click sign
That's why I think the app shows both (connect and sign) window on each other
and one signing, the app crashes since its not yet connected

[usdtbanc]

@ignaciosantise but that throws error when connecting to trust wallet. can you please check once at your end?
thanks

[usdtbanc]

@ignaciosantise can we fix it? still haven't found any work around
thanks!