Metamask: walletconnect and metmask on mobile pre transaction confirmation eventError

Metamask Waletconnect Problem: Pre-TRANSection Confirmation Error

As a developer, you are unlikely to be a stranger to Metamask and its role in handling your wallet. In this article, we will go into a problem that may arise if the DAAP (delegated access application service provider) is connected to mobile devices via Wallet Connect.

The question:

When the user initiates a transaction on the mobile device using Wallet Connect, the browser sends a “event” request to the Metamask RPC server. Unfortunately, this event is not always proven properly, resulting in errors such as the internal JSON-RPC error.

Error message:

The specified error message indicates a problem with the transaction confirmation process. The exact wording may vary depending on your own experience:

“Internal json-rpc error”

or

“Event validation failed”

Troubleshooting steps:

To solve this problem, follow these steps to troubleshoot and solve the problem:

1. Check your Wallet Connect configuration

Make sure the DAAP configuration is correctly set in the Wallet connection settings:

• Check that you have enabled the wallet connection on DAAP.

• Review the WalletConnect.json file to make sure that it is appropriate for the DAAP configuration.

2. Check your event validation **

Check that the event validation works as expected:

• In Metamask, go to
  settings

  >
  wallets and accesses .

• Select the DAAP used to use Wallet Connect.

• In the
  event management section check
  validation rules .

• If necessary, set or add the enforcement rules to ensure only valid events.

3. Check the event response

When checking the event response, find the question:

• Check the “Events” response in the browser Devtools under the “Event” tab.

• Check that the event is properly formatted and contains all the necessary properties (such as type,` transaction “, etc.).

4. Validate API calls

To ensure that the events are sent correctly, check your API calls:

• Check the DAAP RPC server logs to identify problems related to the enforcement of events.

• If you use a local DEV test node, run the API tests in a separate environment to distinguish this problem.

More tips:

• Keep the Metamask and DAAP versions up to date as new versions can introduce repairs to the question.

• Consider the realization of further logging or observation tools to identify the cause of the problem.

By following these steps, you must be able to solve the internal JSON-RPC error and ensure the smooth wallet connection experience on your mobile device.

Token Sale Transaction Speed Elrond