Stuck on sign transaction

[dappnodedev]

Hey! It looks like the app freezes right after clicking on sign transaction:

[eabz]

Hey, thanks for the feedback.

Can you help me with the steps to reproduce?

You used the hosted version or you use a different setup to host it?

[eabz]

Seems it was an issue with the code, just fixed it, can you try again?

[dappnodedev]

Hey @eabz ! It looks like this helped, but after that, the tx seems to be stuck as the app tries to perform it in the L2 network, instead of in Goerli

[dappnodedev]

Also, we are going to integrate this UI inside a Dappnode package, it would be awesome if you could create releases so that we can track versions :)

[dappnodedev]

Any updates on this @eabz ?

[eabz]

Hey @dappnodedev I am really sorry for the delay.
The app should automatically ask you to change the network. Make sure you are using the custom RPC servers provided by the frontend.
If the app is not asking you to change the chain endpoint, take a look at the dev tools on your browser to see what is probably the issue.

[Marketen]

hey @eabz. How can I check that im using the custom RPC server provided by the frontend?. While using the app, I see a lot of post and options request to host http://mock-server-testnet.zkevm-tokens-withdrawal.dappnode:3000. Im guessing that's it.

Logs from mock-server-testnet seem okay:

Relaying request to zkEVM node: https://rpc.public.zkevm-test.net
Received POST request.

I can swap networks correctly by clicking on the "use testnet" button etc, but I have the same problem as @dappnodedev when doing the transaction

Thanks for your help!

[eabz]

Ok. Let me give it a check.

[dappnodedev]

We have seen that the deployed app in https://forced-batches.kindynos.mx/ works fine, but if we deploy it locally the network is not switched to Goerli at the moment of performing the tx

[Marketen]

Hey! Any updates, @eabz?

[eabz]

Hey @Marketen and @dappnodedev sorry for the delay.
I will give it a check. But if you say the deployed version works correctly, then there must be something regarding your build environment.

Can you please give me more information about the environment you are using? Or some instructions to replicate the issue?