Blog

Metamask WalletConnect Issue: Pre-Transaction Validation Error

As a developer, you are probably familiar with Metamask and its role in wallet management. In this article, we will explore an issue that can occur when connecting a DAAP (Delegated Access Application Provider) through Wallet Connect on mobile devices.

Topic:

When a user initiates a transaction on their mobile device using Wallet Connect, the browser sends a transaction request to the Metamask RPC server. Unfortunately, this transaction is not always validated correctly, resulting in errors such as an internal JSON-RPC error.

Error Message:

The error message provided indicates that there was a problem with the transaction validation process. The exact wording may vary depending on your experience:

“Internal JSON-RPC error”

or

“Transaction validation failed”

Troubleshooting steps:

To resolve this issue:

1. Check Wallet Connect configurations

Make sure that the DAAP configurations are configured correctly in the Wallet Connect settings:

• Confirm that you have enabled Wallet Connect in your DAAP.

• Check the “walletconnect.json” file to ensure that it matches the DAAP configurations.

2. Check transaction validation**

Make sure that transaction validation is working as expected:

• In Metamask, go to
  Settings >
  Wallets & Accessories

  

  .

• Select the DAAP you are using in Wallet Connect.

• Check the
  Validation Rules in the
  Transaction Handling section.

• If necessary, modify or add validation rules to ensure that only valid transactions are received.

3. Review transaction responses

When reviewing transaction responses, look for possible clues to the issue:

• Review the transactions response in the Events tab of your browser’s DevTools.

• Make sure the transaction is properly formatted and contains all required properties (e.g. “type”, “transactionId”, etc.).

4. Validate API calls

To ensure that transactions are being sent correctly, validate your API calls:

• Review the DAAP RPC server logs to identify any issues with transaction validation.

• If you are using a local developer test node, run your API tests in a separate environment to isolate this issue.

Additional Tips:

• Keep your Metamask and DAAP versions up to date as newer versions may contain fixes for this issue.

• Consider implementing additional logging or monitoring tools to identify the root cause of the issue.

By following these steps, you should be able to resolve the internal JSON-RPC error and ensure a smooth Wallet Connect experience on your mobile device.

FUTURE FUTURE REGTECH INFLUENCE