Wallet connect v2 adapter error while connecting Error: Proposal expired

[ezekaemmanuel1710]

Hi Team,

Please why do I get the error in the screenshot after a few minutes of connecting to web3auth?

• SDK Version: Web3Auth PnP Web Modal SDK “^7.0.5”
• Platform: Google Chrome on windows 10
• Framework: Next.js version “13.2.4”
• Browser Console Screenshots:
  
  

I will be looking forward to a solution. Thanks

[vjgee]

@ezekaemmanuel1710 Thanks for your recent post.

Can you upgrade your SDK to the latest 7.2.0 https://www.npmjs.com/package/@web3auth/modal

If you still face the issue, please share your package.json to check the pacakage versions.

[afarley]

@vjgee I have updated to 7.2.0 but confirm the problem still persists. We are using web3Auth “cyan” network and Polygon Mumbai.

Edit: Deleted initially because I wanted to do further testing.

[martinus_staghouwer]

Hi @vjgee I am getting the same error.
Means, getting “Error: Proposal expired”
I am sharing my package.json file please assist me.
Thanks.

[vjgee]

Ok, I have forwarded your issue to our Dev team and we will get back with further updates.

[maharshi]

hi @afarley
Once you log in, are you able to use all the functions properly, before you get this error? And also could you please use https://jam.dev/ to share a video recording and console logs when you receive this error?

[martinus_staghouwer]

Hi @maharshi I can explain @afarley 's issue because I am getting the same one using 7.2.0.
The issue causes 5 mins after you click ‘Connect with Wallet’ and connect to Metamask after the wallet connect qr code opened. It shows wallet connect model again.
I am pretty sure the opened wallet connect qr code(proposal) causes the issue, hope your team could fix this issue or fixed already.
At this moment, if you try to connect wallet again, it says ‘Already connected’.

Please assist me to fix this issue.
Thanks.

[martinus_staghouwer]

Hi @vjgee do you have any update for me regarding this issue?
I’ve tried many approaches mentioned in other Topics, but still does not work, even thought we use the latest version of Web3Auth SDK.
Furthermore, even web3Auth’s demo app shows the same error.

We’re looking forward a solution asap.
Thanks.

[vjgee]

@martinus_staghouwer Thanks for sharing the console logs.

I have already reported to this issue to our Dev team and we will get back with further updates.

[maharshi]

Thanks a ton, @martinus_staghouwer, I have replied to your other thread. I have re-created this behaviour and it certainly seems like an issue with the qr-code modal. I am taking this up to our product team and I’ll let you know once I have something.

[martinus_staghouwer]

Thank you @maharshi
I hope we could have some solution asap.

[kakaf10]

Hi Team,

We’re experiencing the same issue with the Web3Auth modal as well.

We’re looking forward to a solution, as it’s causing quite a lot of trouble for our end users. Thank you!

[ezekaemmanuel1710]

Hi @vjgee, I would like to know if there are updates yet.

[kakaf10]

Any news regarding the issue?

[maharshi]

@here Please note that the fix for this is in the works. I will make sure to update this thread once it’s out in the next minor update. Thank you all for your continued patience.

[deivis]

Hello, it’s been a while and there seems to be no news… Any estimate on the fix?

[maharshi]

@here Quick update: The fix is now live. Thanks everyone for your patience! I’ve just finished testing it on my local setup. To resolve the issue, please upgrade your packages to the latest version. This should take care of it. Let me know if you run into any more hiccups.