Metamask: walletconnect and metmask on mobile pre transaction confirmation eventError

Metamask Walletconnect Problem: Slips after the transition

As a delay, you are true, do not explode Metamask and its roles in Koshkami management. In this state, we will survive the problem, which can lead to the connection of your DAAP (Post -Potential with Delegated Access) Connect Connect on mobile devices.

Problem:

When the policy starts the transaction on its mobile device, it is used to connect Carol, the browser sees the inviting “coat” in the Metamask RPC -Server. For soot, this is not always confirmed correctly that it is brought to the spoon, which is a little that you are claiming with a JSON-RPC.

Combining Obuzhka:

Oblast presentation indicates that the problem with the transaction process. Current formulation may vary in the exposure of your concrete experience:

“Intrathine json-rpc”

or

“Witting Sobiti was unsuccessful”

shooting Nepotaja Shagov:

To solve this problem, follow this step, to shoot Nepot and prove the problem:

1. Check the Koshka configuration connection

Receive that your DAAP configuration is correctly configured in the Koshka connection:

• Receive that you have included a Koshka connection to your DAAP.

• Press the Walletconnect.json file that you can meet the configuration of your DAAP.

2. Check the registration jacket **

Receive that workers' work inspection, as was it:

• In different metamask K
  Settings >
  Kovielki and axis .

• Choose fromap you use to connect Carole.

• In section
  Sobyti Imperial Pierce
  Validation .

• Attachment for Rellyglate or add the proverbs to allow only the number.

3. Osmotte out in the coat

At the same time, labor centers are described by the question:

• Check the answer "Sobitia" in devtools browuzer in "Sobytia".

• The revenge that it is correctly covered and coincided with all the unusual property (for example,type, transactionid` etc.).

4. API API API

To ensure that the work is right -check your API:

• Check the RPC RPC magazines that you will rinse any problems with the prefas.

• If you use the local dust for dev, start your test API in the separation medium to allocate this problem.

Adovolitical Coves:

• Take your metamask and DAAP version from relevant, so that new versions can be provided for this concrete problem.

• Demolish the possibility of rehydration of ADD -Daily or monitoring instruments to help the basic tailor of the problem.

Next, a shagh is presented, you are able to grind JSON-RPC Intracelling and make the smooth experience of connecting the carnote to your mobile phone.

bitcoin custom without