METAMASK -Portonnect problem: confirmation error before transaction
As a developer, they are probably not foreign and their role in portfolio management. In this article we deal with a problem that can occur during the DAAP connection (provider of the Post -Access application) via the briefcase connection on mobile devices.
Problem:
When the user initiates a transaction on his mobile device using Wallet Connect, the browser sends an “event” to the Metamas -RPC server. Unfortunately, this event is not always properly approved, which leads to errors, such as those that you experience with the internal JSON RPC error.
Error message:
The specified error message indicates that there is a problem with the transaction confirmation process. A precise wording can vary depending on the specific experience:
“Internal JSON RPC error”
Or
“The validation of events failed”
Problem solution:
To solve this problem, carry out the following steps to solve the problem and solve the problem:
1. Check the configuration of the portfolio connection
Make sure that the DAAP configuration in the Connect portfolio is correctly configured:
- Confirm that you have activated the Connect portfolio in your DAAP.
- Check the “ValletConnect.json” file to ensure that it matches the DAAP configuration.
2. Check the correctness of the event **
Check whether the incident validation works as expected:
- In Metamask you go to
Settings >
wallet and accessories .
- Select used DAAP for the wallet.
3 .. In section
Events Check
Rules to check the correctness .
- Adjust validation rules if necessary or make sure that only correct events have been preserved.
3. Check the answers of the event
When checking answers to events, search for tips on this problem:
1
- Check whether the event is properly formatted and contains all the necessary properties (e.g. “type”, ‘transactionide’ etc.).
4. Check the API calls
To ensure that the events are sent correctly, check the API interface connections:
1
- If you use the local development node, start API tests in a separate environment to isolate this problem.
Additional tips:
- Keep the metamask and DAAP versions regularly because recent versions can make corrections to this special problem.
- Remember to implement additional tools for recording or monitoring to identify the basic cause of the problem.
If you follow these steps, you should be able to solve the internal JSON RPC error and offer a smooth experience from the portfolio on a mobile device.