Wallet does not recognize sponsored transaction with @stacks/connect 8.x (works with Leather Wallet)

[ronoel]

Bug Description

When using the Xverse wallet (Android v1.54.1 and Chrome extension v1.6.0) with @stacks/connect 8.x, sponsored transactions are not recognized by the wallet. The same dApp works correctly with the Leather Wallet, which properly recognizes and processes sponsored transactions.

Steps to Reproduce

1. Integrate @stacks/connect 8.x in your dApp with sponsored transaction logic.
2. Attempt to send a sponsored transaction using Xverse wallet (Android or Chrome extension).
3. Observe that the transaction is not recognized or processed correctly.
4. Try the same flow with Leather Wallet and observe that it works as expected.

Expected Behavior

Sponsored transactions should be recognized and processed by Xverse wallet when using @stacks/connect 8.x, similar to the behavior with Leather Wallet.

Environment

• Xverse Wallet Android: v1.54.1
• Xverse Wallet Chrome Extension: v1.6.0
• @stacks/connect: 8.x
• dApp: https://boltproto.org/wallet

Additional Notes

• The issue does not occur with Leather Wallet.
• This appears to be specific to Xverse wallet with the current version of @stacks/connect.

---

If you need further details or sample code, let me know.

[m-aboelenein]

Hi @ronoel , to help us investigate further, please include a code snippet demonstrating which method from @stacks/connect is being used and how it's called

[ronoel]

Sure, here’s the exact code I’m using. The wallet doesn’t seem to recognize it as a sponsored transaction.

      const response = await request( 'stx_callContract', {
        contract: `${this.contractAddress}.${this.contractName}`,
        functionName: functionName,
        functionArgs: hexEncodedArgs,
        network: environment.network,
        postConditionMode: postConditionModeName,
        postConditions: postConditions,
        sponsored: true, // Indicate that this is a sponsored transaction
      });