You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How are you deploying your application? (if relevant)
telegram webapp
Describe the Bug
When I connect metamask in my telegram webapp, switch chains, and then reload the page, the chainId is different from the one in the wallet.
I noticed that you store a .MMSDK_cached_chainId in the cache to persist the login. After switching chains, this field retains the old chainId. When the page is reloaded, the retrieved chainId becomes the old value, even though the wallet has already switched to the new chain.
Expected Behavior
The chainId retrieved after reloading the page should match the one in the wallet.
Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster
SDK
Web
Provide environment information
telegram desktop version 5.6.3 x64
MetaMask SDK Version
0.30.1
MetaMask Mobile app Version
7.33.0
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
telegram webapp
Describe the Bug
When I connect metamask in my telegram webapp, switch chains, and then reload the page, the chainId is different from the one in the wallet.
I noticed that you store a .MMSDK_cached_chainId in the cache to persist the login. After switching chains, this field retains the old chainId. When the page is reloaded, the retrieved chainId becomes the old value, even though the wallet has already switched to the new chain.
Expected Behavior
The chainId retrieved after reloading the page should match the one in the wallet.
Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster
https://metamask-cache-chain-id.vercel.app/
To Reproduce
I deployed a reproduction in my test bot. You can enter the bot and type /metamask.
The text was updated successfully, but these errors were encountered: